Zerto Virtual Replication Installation Guide ZVR-INV-3.1U4-01-20-02-14
Copyright 2014, Zerto Ltd. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of Zerto Ltd. Zerto Ltd. does not assume responsibility for any printing errors that may appear in this document. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser's personal use, without the prior written permission of Zerto Ltd. All other marks and names mentioned herein may be trademarks of their respective companies. ZVR-INV-3.1U4-01-20-02-14
Table of Contents Chapter 1: Installing Zerto Virtual Replication........................... 4 Zerto Virtual Replication Architecture................................................ 5 Zerto Virtual Replication Interoperability Matrix....................................... 8 Requirements and Pre-installation................................................. 11 Zerto Virtual Manager Firewall Considerations.................................... 13 Installation..................................................................... 14 Troubleshooting the Installation................................................... 21 Uninstalling Zerto Virtual Replication............................................... 21 Installing Zerto Virtual Replication Cmdlets......................................... 22 Installing Zerto Virtual Replication VSS Agent....................................... 23 Chapter 2: Accessing the Zerto Virtual Manager User Interface (Zerto GUI).. 25 Accessing the Zerto GUI.......................................................... 25 Using the Zerto DR Management UI............................................. 25 Using the vsphere Client Console............................................... 26 Using the vsphere Web Client.................................................. 26 Adding a Security Certificate to Enable Access to the Zerto User Interface................. 29 Chapter 3: Initial Configuration...................................... 31 Register Zerto Virtual Replication.................................................. 31 Install Virtual Replication Appliances............................................... 33 Pair Sites to Enable Replicating From One Site to Another Site.......................... 38 Set Up a Remote Site............................................................. 41 Chapter 4: Upgrading Zerto Virtual Replication......................... 42 Upgrading Zerto Virtual Replication................................................ 42 Upgrading VRAs................................................................ 47 Upgrading or Reinstalling VMware Components...................................... 49 3
Chapter 1: Installing Zerto Virtual Replication Zerto Virtual Replication provides a business continuity (BC) and disaster recovery (DR) solution in a virtual environment, enabling the replication of mission-critical applications and data as quickly as possible, the recovery time objective (RTO), and with minimal data loss, the recovery point objective (RPO). Zerto Virtual Replication enables recovery with low values for both the RTO and RPO. Zerto Virtual Replication is installed in every site with virtual machines to be protected and recovered. The installation includes the following: Zerto Virtual Manager (ZVM) A Windows service, which manages everything required for the replication between the protection and recovery sites, except for the actual replication of data. The ZVM interacts with the vcenter Server to get the inventory of VMs, disks, networks, hosts, etc. and then service the Zerto GUI as a standalone browser-based UI or from within vsphere Client console or vsphere Web Client, for the user to create and manage protected virtual machines. The ZVM also monitors changes in the VMware environment and responds accordingly. For example, a VMotion operation of a protected VM from one host to another is intercepted by the ZVM so the Zerto GUI is updated accordingly. OVF to enable installing Virtual Replication Appliances (VRAs) A VRA is a virtual machine installed on each ESX/ESXi hosting virtual machines to be protected or recovered, to manage the replication of data from protected virtual machines to the recovery site. Zerto vsphere Client console plug-in A plug-in in the vsphere Client console that enables managing recovery using Zerto Virtual Replication from the vsphere Client console. Zerto GUI Recovery using Zerto Virtual Replication is managed in a browser using the Zerto DR Management UI, or via the vsphere Client console or vsphere Web Client. The following topics are described in this chapter: Zerto Virtual Replication Architecture, below Zerto Virtual Replication Interoperability Matrix, on page 8 Requirements and Pre-installation, on page 11 Installation, on page 14 Troubleshooting the Installation, on page 21 Uninstalling Zerto Virtual Replication, on page 21 Installing Zerto Virtual Replication Cmdlets, on page 22 Installing Zerto Virtual Replication VSS Agent, on page 23 4
Zerto Virtual Replication Architecture Zerto Virtual Replication Architecture The following diagram shows how the main Zerto Virtual Replication are deployed across sites to provide disaster recovery across these sites. 1 1. For cloud-based architecture diagrams, see Zerto Virtual Replication Zerto Cloud Manager Installation. Installing Zerto Virtual Replication 5
Zerto Virtual Replication Architecture The following diagram shows how the components deployed on one site and the ports and communication protocols used between the components. Zerto Virtual Replication can be installed at multiple sites and each of these sites can be paired to any of the other sites enabling enterprises to protect multiple datacenters as well as remote branch offices. Zerto Virtual Replication supports both the protected and recovery sites being managed by a single vcenter Server. For example, in the following scenario: From one datacenter, a branch office, to another datacenter, the main office, both managed by the same vcenter Server. From one host to a second host, both managed by the same vcenter Server. To the same host but using a different datastore for recovery. When a single vcenter Server is used, port 9081 shown in the above diagram is not used. Also, it is recommended to install Zerto Virtual Replication in the main office site where protected machines will be recovered. Installing Zerto Virtual Replication 6
Zerto Virtual Replication Architecture The following table provides information about the ports opened by Zerto Virtual Replication: Ref. # Port Purpose 1 9080 a Communication between the ZVM and a Zerto VSS Agent. 2 443 Required between the Zerto Virtual Manager (ZVM) and the vcenter Server. 3 9669 a Communication between a machine running the vsphere Web Client and the ZVM for the relevant vcenter Server. 4 9669 a Communication between a machine running the vsphere Client console and the ZVM for the relevant vcenter Server. 5 9669 Communication between a machine running the Zerto DR Management UI and the ZVM for the relevant vcenter Server. 6 443 Required between an ESXi 4.x host and the Zerto Virtual Manager (ZVM) during installation of a Virtual Replication Appliance (VRA). 7 9081 a Communication between the site ZVMs b. 8 443 Required between an ESXi 5.x host and the Zerto Virtual Manager (ZVM) during installation of a Virtual Replication Appliance (VRA). 9 22 Required between an ESXi host and the Zerto Virtual Manager (ZVM) during installation of a Virtual Replication Appliance (VRA). 10 4005 Log collection between the ZVM and site VRAs. 11 4006 Communication between the ZVM and site VRAs. 12 4009 Communication between the ZVM and site VRAs to handle checkpoints. 13 9080 a Internal communication between the ZVM and Zerto internal APIs. 14 9669 a Communication between the ZVM and Zerto REST APIs. 15 9080 a Communication between the ZVM and Zerto cmdlets. 16 4007 Control communication between protecting and recovering VRAs. 17 4008 Communication between VRAs to pass data from protected virtual machines to a VRA on a recovery site. a. The default port provided during the Zerto Virtual Replication installation which can be changed during the installation. b. When the same vcenter Server is used for both the protected and recovery sites, Zerto Virtual Replication is installed on one site only and this port can be ignored. Note: For details of the architecture and ports used in a cloud-based architecture environment, see Zerto Virtual Replication Zerto Cloud Manager Installation. Installing Zerto Virtual Replication 7
Zerto Virtual Replication Interoperability Matrix Zerto Virtual Replication Interoperability Matrix The following tables list the supported environments and VMware features as of the release date for this document. For an up-to-date list of supported ESX/ESXi hosts, see the Compatibility Matrix dialog, under the site configuration Advanced Settings dialog in the Zerto GUI. Environments Supported by Zerto Virtual Replication Environment Zerto Virtual Replication version 3.1U4 (Granite) Zerto Virtual Manager Supported Servers Windows Server 2003 and SP2 (32 and 64 Bit) Windows Server 2008 (32 Bit) Windows Server 2008 and SP2 (64 Bit), R2 and R2 SP1 (64Bit) Windows Server 2012 and SP1 and R2 Zerto VSS Agent Windows Server 2003 No Windows Server 2003 SP2 (32 and 64 Bit) Windows Server 2008 all versions (32Bit) No Windows Server 2008 and SP2 (64Bit), R2 and R2 SP1 (64Bit) Windows Server 2012 and SP1 and R2 Operating Systems Supported for Re-IP: Windows Windows Server 2003, 2008 and 2012 all versions Operating Systems Supported for Re-IP: Linux Red Hat Enterprise Linux versions 5-6 SUSE Linux Enterprise versions 10-11 CentOS versions 5-6 Microsoft.NET Microsoft.NET Framework 4.0 Microsoft.NET Framework 4.5 VMware vcenter Server vcenter Server 4.0 and lower No vcenter Server 4.0U1-5.5 Installing Zerto Virtual Replication 8
Zerto Virtual Replication Interoperability Matrix Environment ESX/ESXi 4.0 ESX/ESXi 4.0U1-4.0U4 a ESX/ESXi 4.1-4.1U3 ESXi 5.0-5.0U3 ESXi 5.1-5.1U2 ESXi 5.5 vcloud Director 1.0-1.0.1 vcloud Director 1.5-1.5.2 vcloud Director 5.1-5.5 AMQP b vsphere Client console 4.0-5.5 vsphere Web Client 5.0-5.0U2 vsphere Web Client 5.1-5.5 Adobe Flash Player 11.1-11.8 Storage: SAN, NAS, FC, iscsi, DAS Storage: IDE VMware Hosts VMware vcloud Director and AMQP vsphere Clients and Adobe Flash Storage Volumes: All vdisks (including VMFS, Independent Persistent disks, Virtual RDM and dedupe stores) and Physical RDM Volumes: Non-default disk geometry Zerto Virtual Replication version 3.1U4 (Granite) No No No No Use preseed a. Known issues affect user experience: If a protected VM disk is resized, the recovery disk is not automatically resized when it is RDM, the recovery vcenter is 4.0 or there is a disconnection between the sites when resizing: The VPG state changes to Needs Configuration. Host affinity rules are not set on the VRA or test VMs. Lack of support for some advanced queries, resulting in more queries against the vcenter Server, slowing response time. The VRA needs manual intervention when installed on a shared datastore and one of the hosts sharing the datastore is powered off. b. Zerto Virtual Replication is tested with Rabbit MQ with Erlang/OTP. Installing Zerto Virtual Replication 9
Zerto Virtual Replication Interoperability Matrix VMware Features Supported by Zerto Virtual Replication Feature 16Gb FC HBAs Datastore clusters Distributed Switch QoS Fault Tolerance vcenter High availability (HA) with/without admission control (recovery site) b Host Affinity Rules and CPU Pinning Linked Clones Protect VMs using thin-provisioning Protected VM DRS and sdrs Stateless ESX over FCoE Storage IO control Storage Profiles d Storage vmotion of protected VMs Storage vmotion of protected VRAs vapp support vcenter Roles and permissions VMotion of protected VMs (with/without shared disks for VMs) VMware Host maintenance mode vcloud Director (vcd) 1.5, 5.1-5.5 AMQP Extended vcloud Networking and Security (vcns) Services f : Fivetuple firewall and IPSec VPN services Third-party distributed switch support vapp Networks vcd Public Addresses vcloud Director (vcd) 5.1-5.5 Elastic Virtual Datacenter Storage Profiles Zerto Virtual Replication version 3.1U4 (Granite) a No c N/A e Required Installing Zerto Virtual Replication 10
Requirements and Pre-installation Feature Storage Profiles with storage clusters as replicated targets Fast provisioning using linked clones Metadata (Custom guest Properties) GUI g Org vdc Networks h Snapshots of protected VMs i Single Sign-On j Zerto Virtual Replication version 3.1U4 (Granite) c a. When specifying the recovery storage for a virtual machine with a storage cluster, you have to specify a datastore in the cluster. b. Test failover, failover and move will fail if admission control does not enable starting recovered VMs. c. Collapsed on reverse protection. d. Not involved in replication. e. Cannot perform any recovery operations to the VRA during the storage vmotion. f. With vcd 1.5, settings not replicated with the virtual machines. g. Metadata is replicated. Metadata on every vcd entity is supported as it does not interfere with replication. h. Treat all Org vdc networks as if they were part of the entire Organization. i. Only vcd VM and vapp metadata. j. vcenter Server must be connected to Active Directory. Requirements and Pre-installation Zerto Virtual Manager is installed on each site managed by a vcenter Server on a machine running a Windows operating system with the following requirements: Windows Server 2003 SP2 or higher, or Windows Server 2008, 2008R2, 2012 or 2012R2. Reserve at least 2 CPUs and 4GB RAM for the machine. The clocks on servers where Zerto Virtual Replication is installed must be synchronized with each other so that the UTC values match (the timezones can be different). Zerto recommends that the clocks are synchronized using NTP. Note: Installing Zerto Virtual Replication on a 32-bit Windows operating system limits the memory to 2GB. This limits the number of virtual machines that can be protected. At least 2GB of free disk space. Microsoft.NET Framework 4 or 4.5. The 4.0 installation executable is included as part of the Zerto Virtual Replication installation kit and it needs an additional 1.8GB of free disk space. 1 Installing Zerto Virtual Replication 11
Requirements and Pre-installation You must have VMware vcenter Server version 4.0U1 or higher with at least one ESX/ESXi host installed on each site where Zerto Virtual Manager is to be used. When recovery is managed by the same vcenter Server as the protection, Zerto Virtual Manager is required to be installed once only. When the protected and recovery sites are managed by different vcenter Servers Zerto Virtual Manager is installed once per vcenter Server. Note: When the vcenter Server is installed on a Linux machine via the vcenter Server Linux Virtual Appliance (vcsa), the Zerto Virtual Manager must still be installed on a Windows machine. It is recommended to install the Zerto Virtual Manager with the following profile: On a dedicated virtual machine. With a dedicated administrator account. No other applications installed on this machine. If additional applications are installed, the Zerto Virtual Manager service must receive enough resources and HA remain enabled. With VMware vsphere High Availability (HA) enabled. With the VM Restart Policy set to High. Note: If a proxy server is used at the site, specify the IP address of the Zerto Virtual Manager in the exception list in the Proxy Server settings. Routable Networks Zerto Virtual Manager supports the following network configurations: Flat LAN networks VLAN networks, including Private VLANs and stretched VLANs WAN emulation VPN IPsec Zerto Virtual Manager does not support NAT (Network Address Translation) firewalls. Minimum Bandwidth The connectivity between sites must have the bandwidth capacity to handle the data to be replicated between the sites. The minimum bandwidth must be at least 5 Mb/sec. 1. You should ensure that you have the latest.net and Windows updates, unless Zerto support warns against a specific update. For example, installing update 2661254 and running vsphere client 4.x causes a problem to connect to the vcenter Server during the Zerto Virtual Replication installation. Also, from Microsoft MSDN: Ensure that your computer has the latest Windows service pack and critical updates. To find security updates, visit Windows Update. If you re installing on XP 64 bit or Windows 2003 you might need the Windows Imaging Component. Download the 32 bit component from http://www.microsoft.com/downloads/details.aspx?familyid=8e011506-6307-445b-b950-215def45ddd8 and the 64 bit component from http://www.microsoft.com/downloads/details.aspx?familyid=f64654ac-6e26-41d9-a90a-0e7783b864ee. Installing Zerto Virtual Replication 12
Requirements and Pre-installation Zerto User Interface Requirements On the machine running the Zerto user interface to manage the disaster recovery you need Adobe Flash Player 11.8 ActiveX or higher. If Adobe Flash Player is not installed, it is included with the Zerto Virtual Replication installation and you are prompted to install it when you first attempt to access the Zerto user interface. 1 The minimum recommended screen resolution is 1024*768. Zerto Virtual Manager Firewall Considerations Zerto Virtual Manager requires the following ports to be open in the protected and recovery site firewalls: Port Description 22 a During Virtual Replication Appliance (VRA) installation on ESXi 4.x and 5.x hosts for communication between the Zerto Virtual Manager (ZVM) and the ESXi hosts IPs and for ongoing communication between the ZVM and a Zerto Cloud Connector. 443 During VRA installation on ESX/ESXi hosts for communication between the ZVM and the ESX/ESXi hosts IPs and for ongoing communication between the ZVM and vcenter Server and vcloud Director. 4005 Log collection between the ZVM and VRAs on the same site. 4006 TCP communication between the ZVM and VRAs on the same site. 4007 TCP control communication between protecting and recovering VRAs and between a Zerto Cloud Connector and VRAs. 4008 TCP communication between VRAs to pass data from protected virtual machines to a VRA on a recovery site and between a Zerto Cloud Connector and VRAs. 4009 TCP communication between the ZVM and site VRAs to handle checkpoints. 5672 TCP communication between the ZVM and vcloud Director for access to AMQP messaging. 9080 HTTP communication between the ZVM and Zerto internal APIs, a Zerto Cloud Manager (ZCM), cmdlets, and a VSS Agent. 9081 b TCP communication between the ZVMs c and between a ZVM and a Zerto Cloud Connector. 1. The GUI is displayed within a Microsoft Internet Explorer browser window. Thus, access to the Zerto Virtual Manager must be enabled as a trusted site in Internet Explorer: In Internet Explorer, select Tools > Internet Options and in the Internet Options dialog that is displayed, select the Security tab. Select the Trusted Sites zone, click Sites and enter the IP address of the machine where the Zerto Virtual Manager will be installed. Installing Zerto Virtual Replication 13
Installation Port 9082 and up Description A cloud service provider supplies disaster recovery services Two TCP ports for each VRA (one for port 4007 and one for port 4008) accessed via the Zerto Cloud Connector installed by the cloud service provider. There is directionality to these ports. It is recommended to use a port range starting with port 9082. For example, Customer A network has 3 VRAs and customer B network has 2 VRAs and the cloud service provider network has 4 VRAs, then the following ports must be open in the firewall for each cloud: The cloud service provider s VRAs need to use 6 ports to reach customer A s VRAs, while customer A s VRAs need 8 ports to reach the cloud s VRAs. The cloud service provider s VRAs need to use 4 ports to reach customer B s VRAs, while customer B s VRAs need 8 ports to reach the cloud s VRAs. 9669 HTTPS communication between the machine running the Zerto GUI, the Zerto DR Management UI, vsphere Web Client or vsphere Client console, and a ZVM, and for invoking Zerto REST APIs. 9779 HTTPS communication between the Zerto Self-Service Portal for in-cloud (ICDR) customers and a ZVM. 9989 HTTPS communication between a browser and the Zerto Cloud Manager. a. If the ESX/ESXi hosts are given names, make sure that the Zerto Virtual Manager can resolve these names. b. The default port set during the Zerto Virtual Replication installation. When pairing the ZVM to a Zerto Cloud Connector, this value must not be changed. c. When the same vcenter Server is used for protection and recovery, Zerto Virtual Replication is installed on one site only and this port is ignored. Installation The Zerto Virtual Replication installation deploys the Zerto Virtual Manager (ZVM) and sets up the plug-in to manage the replication from the vsphere Client console and also copies the installation for the Virtual Replication Appliance (VRA). A complete installation includes installing Zerto Virtual Replication on the protected and peer, recovery, sites. When both these sites use a single vcenter Server, Zerto Virtual Replication is installed on only one site. In this case, it is recommended to install Zerto Virtual Replication in the main office site where protected machines will be recovered. You can install Zerto Virtual Replication using the defaults provided by Zerto or perform a custom install, whereby you can determine the ports that will be used by Zerto Virtual Replication. In addition, when performing a custom install, site information and information to connect to vcloud Director can be provided, which, with an express install can only be provided, if required, after Installing Zerto Virtual Replication 14
Installation the installation in the Zerto GUI; the Zerto DR Management UI, vsphere Client console or Web Client. To perform an express install of Zerto Virtual Replication: 1. Run Zerto Virtual Replication Installer.exe. Note: If the Microsoft.NET Framework 4 or 4.5 is not installed, it is installed as part of the Zerto Virtual Replication installation. In this case, after it is installed, reboot the vcenter Server machine, and when it comes up rerun Zerto Virtual Replication Installer.exe. 2. Follow the wizard through the installation until the dialog for the Installation Type and select the Express Installation option. 3. Click Next. The vcenter Server Connectivity and Site Name dialog is displayed. Specify the following: IP / Host Name The IP address or host name of the machine where the vcenter Server runs. User Name The user name for a user with administrator level privileges to the vcenter Server. The name can be entered using either of the following formats: username domain\username Password A valid password for the given user name. Site Name The name used to identify the site. 4. Click Next. The installation performs a series of checks to make sure that the installation can proceed successfully. 5. After the checks complete successfully, click Next and continue to the end of the installation. 6. Set any antivirus software running on the machine not to scan the folder where Zerto Virtual Replication is installed. Installing Zerto Virtual Replication 15
Installation 7. Repeat the procedure to install Zerto Virtual Replication on peer sites. To perform a custom install of Zerto Virtual Replication: 1. Run Zerto Virtual Replication Installer.exe. Note: If the Microsoft.NET Framework 4 or 4.5 is not installed, it is installed as part of the Zerto Virtual Replication installation. In this case, after it is installed, reboot the vcenter Server machine, and when it comes up rerun Zerto Virtual Replication Installer.exe. 2. Follow the wizard through the installation until the dialog for the Installation Type and select the Custom Installation option. 3. Click Next. The Zerto Virtual Manager Setup dialog is displayed. IP for use by vsphere Client The IP to access the Zerto Virtual Manager from the Zerto DR Management UI, vsphere Client console or Web Client. If the machine has more than one NIC, select the appropriate IP from the list, otherwise the IP that is displayed is the only option. HTTP Port (ZVMApi) The port used for inbound communication between the Zerto Virtual Manager and Zerto internal APIs, Cmdlets and a VSS Agent. HTTPS Port (vsphere client<->zvm) The port used for inbound communication between the Zerto DR Management UI, vsphere Client console or Web Client and the Zerto Virtual Manager. TCP Port (ZVM<->ZVM) The port used for communication between Zerto Virtual Managers. Both the protected and recovery sites belong to the same enterprise If you change the value, when pairing sites, use the TCP port value specified here. Pairing the sites is described in Pair Sites to Enable Replicating From One Site to Another Site, on page 38. An enterprise using a cloud service provider to supply disaster recovery services You must not change this value. 4. Click Next. Installing Zerto Virtual Replication 16
Installation The Service User dialog is displayed. Select either the Local System account or This account: Local System account Use the Local System account to run the Zerto Virtual Manager service installed as part of the installation. The Local System account has complete unrestricted access to local resources. This account Use a specific account as the user account to run the Zerto Virtual Manager service installed as part of the installation. Password The password to use to run the service under the specified account. Confirm Password Confirmation of the password. 5. Click Next. The Database Selection dialog is displayed. Information required by Zerto Virtual Replication is stored in a database embedded in the Zerto Virtual Manager. This information includes details of the site where the Zerto Virtual Manager is installed, details of the Virtual Replication Appliances and the volumes they use, and points-in-time recorded for recovery purposes. By default an embedded SQL-based database is used but the option is available to use an externally managed database, either Microsoft SQL Server or SQL Server Express. Note: During protection and if recovery is required, the database must be running. Thus, if an external database is used and it is down for any reason, protection ceases. Installing Zerto Virtual Replication 17
Installation Leave the default, to use the embedded database or select the option to connect to an external Microsoft SQL Server or SQL Server Express database. Note: It is recommended to use the embedded database, unless you specifically want to manage all data for you applications within a single database. If the external database option is selected: Server Name The domain name and server instance to connect to, with the format domain\instance. Specify either of the following authentication options: Windows Authentication Use Windows authentication. This option is only enabled if a specific service user account was specified in the previous Service User dialog, in which case the service account name and password are used. SQL Server Aut hen ica ti on Use SQL Server authentication. User Name The user name for SQL Server database. Password A valid password for the given user name. 6. Click Next. The Zerto Virtual Manager Site Details dialog is displayed to define general information about the site. Installing Zerto Virtual Replication 18
Installation Site Name The name used to identify the site. This name is displayed in the Zerto GUI. Location Information such as the address of the site or a significant name to identify it. Contact Info Information about who to contact if a need arises, such as a phone number or email address. The Site Name added here is used to identify the site in the Zerto GUI. 7. Click Next. The vcenter Server Connectivity dialog is displayed. IP / Host Name The IP address or host name of the machine where the vcenter Server runs. User Name The user name for a user with administrator level privileges to the vcenter Server. The name can be entered using either of the following formats: username domain\username Password A valid password for the given user name. 8. Click Next. The vcloud Director Connectivity dialog is displayed. Installing Zerto Virtual Replication 19
Installation When using vcloud Director and you have installed an AMQP server, click the Enable VMware vcloud BC/DR checkbox and enter the VMware vcloud Director access details: IP / Host Name The IP address or host name of the machine where vcd runs. When connecting to vcd with multiple cells, enter the virtual IP for the network load balancing used by the cells. User name The user name for an administrator to vcd. Password A valid password for the given user name. AMQP User name The user name for the AMQP server. AMQP Password A valid password for the given AMQP user name. If the vcd connection settings are not specified, for example, when you do not have an AMQP server installed, they can be set in the Advanced Settings dialog in the Site Configuration panel, in the Zerto GUI after the installation completes, as described in the Zerto Virtual Replication Zerto Cloud Manager Installation, Configuration and Management. Zerto provides an AMQP installation kit if you do not have one installed for vcd. Run ZertoAMQPInstallWizard.exe as described in the Zerto Virtual Replication Zerto Cloud Manager Installation, Configuration and Management, with the following credentials: Username: guest Password: guest 9. Click Next. The installation performs a series of checks to make sure that the installation can proceed successfully. 10. After the checks complete successfully, click Next and continue to the end of the installation. If you intend managing your disaster recovery from this machine, you can select to open the Zerto DR Management UI at the end of the installation. 11. Set any antivirus software running on the machine not to scan the folder where Zerto Virtual Replication is installed. 12. Repeat the procedure to install Zerto Virtual Replication on peer sites. Note: If the vsphere Client console was open during the installation, close it and reopen it to ensure you have the Zerto Virtual Replication UI loaded. Installing Zerto Virtual Replication 20
Troubleshooting the Installation After installing Zerto Virtual Replication, add the machine to the relevant host boot configuration, so that on starting up a host this machine running the Zerto Virtual Manager is also powered on automatically. Troubleshooting the Installation If you have problems with accessing the Zerto GUI, check under Windows Services, on the machine where the Zerto Virtual Manager is installed that the Zerto Virtual Manager service is started. Uninstalling Zerto Virtual Replication You uninstall Zerto Virtual Replication, in one of the following ways: Via Start > Programs > Zerto Virtual Replication > Uninstaller. Rerun the installation and select the Uninstall option. Via the Add or Remove Programs in the Windows Control Panel. Note: The Zerto tab continues to be displayed in the vsphere Client console until the console is closed and then reopened. When you uninstall Zerto Virtual Replication, the Virtual Replication Appliances and all the virtual protection groups defined to protect virtual machines are also removed, including all the target disks managed by the VRA for the virtual machines that were being protected. If, for any reason, a Virtual Replication Appliance cannot be removed, for example, when the vcenter Server is down or when the Virtual Replication Appliance was installed on an ESXi host and the password to the host was changed, you can continue with the uninstall and later remove the Virtual Replication Appliance manually from within the vsphere Client console. If this does not work, contact Zerto support. Installing Zerto Virtual Replication 21
Installing Zerto Virtual Replication Cmdlets Installing Zerto Virtual Replication Cmdlets Windows PowerShell is a command-line shell running under Windows operating systems for system administrators. The Windows PowerShell includes both an interactive command line prompt and a scripting environment that can be used independently or in combination. Windows PowerShell is built on top of the.net Framework common language runtime (CLR), enabling it to accept and return.net Framework objects. To run the Zerto Virtual Replication cmdlets you must first run the installation package supplied by Zerto. Note: You must have both Microsoft.NET Framework 4 and Windows PowerShell installed. To install the Zerto Virtual Replication cmdlets: Run the installation file. After installing the Zerto Virtual Replication cmdlets, either add the cmdlets each time you open the Windows PowerShell, or create a Windows PowerShell profile. The following procedure describes how to add the Zerto Virtual Replication cmdlets for every Windows PowerShell session. To add the Zerto Virtual Replication cmdlets to the current session: Open Windows PowerShell with the following arguments: -NoExit -Command Add-PSSnapIn Zerto.PS.Commands The Add-PSSnapin cmdlet adds registered Windows PowerShell snap-ins to the current session. To add the Zerto Virtual Replication cmdlets to every session, in the Properties dialog for a PowerShell shortcut specify a Target value similar to the following: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -NoExit -Command Add-PSSnapIn Zerto.PS.Commands Note: You can create a Windows PowerShell profile, as described in the Windows PowerShell Help, to add the snap-in to all future Windows PowerShell sessions. For more details, see the Zerto Virtual Replication Cmdlets guide. Installing Zerto Virtual Replication 22
Installing Zerto Virtual Replication VSS Agent Installing Zerto Virtual Replication VSS Agent The Microsoft Volume Shadow Copy Service (VSS) enables taking manual or automatic backup copies or snapshots of data, even if it has a lock, on a specific volume at a specific point-in-time over regular intervals. This ensures not just that the data is crash consistent but also application consistency if recovery is needed. Zerto Virtual Replication enables adding checkpoints to the journal that are synchronized with VSS snapshots. To use Zerto Virtual Replication with VSS to ensure application consistency you must install the ZertoVssAgent on every virtual machine that uses VSS and that you want to protect with Zerto Virtual Replication. The ZertoVssAgent is available from Zerto Ltd. in both 32-bit and 64-bit versions. You can install the ZertoVssAgent on the following supported Windows operating systems: 32-Bit Operating Systems Windows Server 2003 SP2 64-Bit Operating Systems Windows Server 2003 SP2 Windows Server 2008, all versions (SPs and R2) Windows Server 2012, all versions (SPs) To install the ZertoVssAgent: 1. Run either ZertoVss32Agent.msi or ZertoVss64Agent.msi on every virtual machine that uses VSS and that you want to protect with Zerto Virtual Replication, where ZertoVss32Agent.msi is for 32-bit Windows operating systems and ZertoVss64Agent.ms is for 64-bit Windows operating systems. 2. Follow the wizard through the installation. The Zerto Virtual Manager Connections Settings dialog is displayed. 3. Specify the IP address and HTTP port number for the Zerto Virtual Managers managing the protection of the virtual machines, both for the local site and optionally, for the paired, remote site. If the same vcenter Server is used both for protecting and recovering virtual machines, specify the IP address and HTTP port number for the single Zerto Virtual Manager installed. Note: The default HTTP port number when Zerto Virtual Replication is installed is 9080. Installing Zerto Virtual Replication 23
Installing Zerto Virtual Replication VSS Agent If you enter a wrong IP address or port you can correct the address or port after the installation completes by editing the ZertoVssAgentGUI.exe.conf file in the ZertoVssAgent folder under the folder where the ZertoVssAgent is installed, for example, C:\Program Files (x86)\zerto. 4. Click OK. The ZertoVssAgent is installed and the Add VSS Checkpoint is placed on the desktop. For more details about the ZertoVssAgent, see the Zerto Virtual Manager Administration Guide. Installing Zerto Virtual Replication 24
Chapter 2: Accessing the Zerto Virtual Manager User Interface (Zerto GUI) You manage your vcenter site, including the protection and replication of virtual machines between the protected and recovery sites, using the Zerto GUI. The following topics are described in this chapter: Accessing the Zerto GUI, below Adding a Security Certificate to Enable Access to the Zerto User Interface, on page 29 Zerto also provides a set of PowerShell cmdlets and REST APIs to enable incorporating some of the disaster recovery functionality within scrips or programs. On first access to the user interface, you might have to add a security certificate to set up secure communication, as described in Adding a Security Certificate to Enable Access to the Zerto User Interface, on page 29. Accessing the Zerto GUI You manage your vcenter site, including the protection and replication of virtual machines between the protected and recovery sites, using one of the following ways: The Zerto DR Management UI. The vsphere Client console. The vsphere Web Client. Using the Zerto DR Management UI To use the Zerto DR Management UI: 1. In a browser, enter the following URL: https://zvm_ip:9669 where zvm_ip is the IP address of the Zerto Virtual Manager for the site you want to manage. 25
2. Login using the user name and password for the vcenter Server connected to the Zerto Virtual Manager. Note: You cannot protect a vapp, as a vapp, using the Zerto DR Management UI. Using the vsphere Client Console To use the vsphere Client console: 1. Login using the user name and password for the vcenter Server connected to the Zerto Virtual Manager. 2. Access the Zerto tab, displayed for the root node. Note: The Zerto tab is also displayed for a datacenter node showing the same information as for the root node. For a virtual machine or vapp node the Zerto tab displays information specific to the virtual machine or vapp. Using the vsphere Web Client You can use the VMware Web Client to manage Zerto Virtual Replication. The vsphere Web Client is a browser-based interface for configuring and administering virtual machines enabling you to connect to a vcenter Server system to manage an ESXi host through a browser. The following procedure describes how to configure the vsphere Web Client to display Zerto Virtual Replication dialogs. This procedure is valid for vsphere Web Client version 5.1 communicating with vcenter Server from version 5.0 and higher. Note: The following procedure assumes that the vsphere Web Client version 5.1 has been installed. Although you can run the vsphere Web Client version 5.1 with vsphere Server 5.0 and 5.1, when installing the vsphere Web Client you need access to a vsphere Server version 5.1 which includes an option for single sign on, required by the vsphere Web Client installation. Note: Setting up Zerto Virtual Replication to be used via the vsphere Web Client disables the use of other VMware plug-ins, such as VDP and VSA, causing them to disappear from the web client. This is a known VMware problem, see http://kb.vmware.com/selfservice/microsites/ search.do?language=en_us&cmd=displaykc&externalid=2042455. To resolve this issue, set up two web clients, on different servers. On one run Zerto Virtual Replication and on the other run the VMware plug-ins. 26
Accessing the Zerto GUI To set up the vsphere Web Client to work with To work with Zerto Virtual Replication: 1. When running the vsphere Web Client on a Microsoft Windows platform: Copy and run VsphereWebClientPluginEnabler.exe to the machine where you run the web client. This file is located in the Zerto Virtual Replication folder under the folder where Zerto Virtual Replication was installed. You can copy VsphereWebClientPluginEnabler.exe to any folder on the relevant machine. Run VsphereWebClientPluginEnabler.exe as an administrator. When running the vsphere Web Client on a Linux platform, via the vcenter Server Linux Virtual Appliance (vcsa): In the directory /var/lib/vmware/vsphere-client, open the webclient.properties file in a text editor and add the following to the file:. scriptplugin.enabled = true 2. Restart the vsphere Web Client. Note: After the service has started you might have to wait a few minutes before you can open the vsphere Web Client in your browser. To use the vsphere Web Client: 1. Login using the user name and password for the vcenter Server connected to the Zerto Virtual Manager. 2. In the browser, navigate to a vsphere node supported by Zerto Virtual Replication, such as the root node or a virtual machine, and choose the Classic Solutions tab, which is now displayed after the Related Objects tab. Note: With Chrome and Firefox browsers, you must load the script plug-in page in an external tab at least once before it appears inside the vsphere Web Client. 3. If prompted, allow blocked content to be displayed. The Classic Solutions tab is displayed when there is a plug-in installed, in this case the Zerto Virtual Replication user interface plug-in. Accessing the Zerto Virtual Manager User Interface (Zerto GUI) 27
Accessing the Zerto GUI 4. If more than one plug-in is installed, click Zerto to display the Zerto Virtual Replication UI. Accessing the Zerto Virtual Manager User Interface (Zerto GUI) 28
Adding a Security Certificate to Enable Access to the Zerto User Interface Adding a Security Certificate to Enable Access to the Zerto User Interface The communication between the Zerto Virtual Manager and the user interface uses HTTPS. On the first login to user interface, via the Zerto DR Management UI, vsphere Client console, or vsphere Web Client, you have to install a security certificate in order to be able to continue working without each login requiring acceptance of the security. To install a security certificate for Zerto Virtual Manager: Note: The following procedure is based on Microsoft Internet Explorer. The procedure is similar for Google Chrome and for Mozilla Firefox. On first access to the Zerto GUI, if you haven t installed the security certificate, the Security Alert dialog is displayed. 1. Click View Certificate. The Certificate dialog is displayed. 2. Click Install Certificate. The Certificate Import Wizard dialog is displayed. 3. Follow the wizard: Place all the certificates in the Trusted Root Certification Authorities store: Select the Place all certificates in the following store option and browse to select the Trusted Root Certification Authorities store. Accessing the Zerto Virtual Manager User Interface (Zerto GUI) 29
Adding a Security Certificate to Enable Access to the Zerto User Interface 4. Continue to the end of the wizard. Click when the Security Warning is displayed. 5. Click OK that the installation was successful. 6. Click OK when prompted and then in the Security Alert dialog to continue. Accessing the Zerto Virtual Manager User Interface (Zerto GUI) 30
Chapter 3: Initial Configuration After installing Zerto Virtual Replication, you configure the site. Zerto Virtual Replication is configured and managed from within the Zerto GUI. This chapter describes the initial configuration required after installing Zerto Virtual Replication. The following topics are described in this chapter: Register Zerto Virtual Replication, below Install Virtual Replication Appliances, on page 33 Pair Sites to Enable Replicating From One Site to Another Site, on page 38. Set Up a Remote Site, on page 41. Cloud service providers must configure both Zerto Virtual Manager and a Zerto Cloud Manager as described in Zerto Virtual Replication Zerto Cloud Manager Installation and Configuration. Register Zerto Virtual Replication On the very first access to Zerto GUI, you have to either register your use of Zerto Virtual Replication, by entering the license key supplied by Zerto or pair to a site where a license has already been entered. Note: A customer using a Cloud Service Provider (CSP) to manage the disaster recovery, pairs to the CSP using the IP address supplied by the CSP and does not enter a license key. A CSP with more than one cloud site must enter a license for each cloud site and not pair to a licensed cloud site. The license can be the same license used in another cloud site. 31
Register Zerto Virtual Replication After entering a valid license, the How-To-Guide is displayed. Use this to learn a little about Zerto Virtual Replication and the initial configuration that is required. If you do not want to see the guide again, uncheck the Show on startup checkbox in the bottom left of the window. After closing the guide details of the local site are displayed on the left and the remote site on the right in the Summary tab. The local site name, specified during the installation, is displayed in the header at the top with the location displayed on the right. If an express installation was performed, the location is the machine domain name where the Zerto Virtual Manager is installed. In the top left of the header an indicator show the Zerto Virtual Manager status. The alert status indicators are green when there are no problems, yellow for warnings and red for errors. Hovering the mouse over the red or yellow indicator, when it is showing, displays the reason for the error or warning and a link to the Alerts tab (More Alerts), under the Alerts & Events tab, where all the alerts are displayed in the Alerts tab. Initial Configuration 32
Install Virtual Replication Appliances The number of unacknowledged alerts is displayed inside the indicator and by clicking on the indicator you can see more information about the alert. Install Virtual Replication Appliances The Zerto Virtual Replication installation includes the OVF template for Virtual Replication Appliances (VRAs). A VRA is a Zerto Virtual Replication virtual machine that manages the replication of virtual machines across sites. A VRA must be installed on every ESX/ESXi which hosts virtual machines that require protecting in the protected site and on every ESX/ESXi that will host the replicated virtual machines in the recovery site. A VRA can manage a maximum of 500 volumes, whether these are volumes being protected or recovered. It is recommended to install a VRA on every ESX/ESXi host so that if protected virtual machines are moved from one host in the cluster to another host in the cluster there is always a VRA to protect the moved virtual machines. If you are protecting a vapp, you must install a VRA on every ESX/ESXi host in the cluster on both the protected and recovery sites and ensure that DRS is enabled for these clusters. VRA Installation Requirements To install a VRA you require the following: 12.5GB datastore space At least 1GB of reserved memory. ESX/ESXi host version 4.0U1 and higher. Ports 22 and 443 are enabled on the host during the installation. For the duration of the installation of the VRA, the Zerto Virtual Manager enables SSH in the vcenter Server. You must also know the following information to install a VRA: The datastore the VRA will use and the local network used by the host. The network settings to access the peer site; either the default gateway or the IP address, subnet mask and gateway. Initial Configuration 33
Install Virtual Replication Appliances If a static IP is used, which is the Zerto recommendation 1, instead of DHCP, the IP address, subnet mask and default gateway to be used by the VRA. To install Zerto Virtual Replication Appliances (VRAs) on ESX/ESXi hosts: 1. In the Zerto GUI, click the Manage VRAs button or VRAs tab to display the VRAs tab content. 2. If the access to the peer site VRAs is not via the network default gateway, check the Paired Site Routing checkbox and click the link. The Configure Paired Site Routing dialog is displayed. 1. In a non-production environment it is often convenient to use DHCP to allocate an IP to the VRA. In a production environment this is not recommended. For example, if the DHCP server changes the IP allocation on a reboot, the VRA does not handle the change. Initial Configuration 34
Install Virtual Replication Appliances Specify the IP address, subnet mask and gateway to access the network for the peer site VRAs and click Save. These access details then apply to every VRA defined on this site to access the peer site. 3. Select a host which require a VRA and click Actions and then click Install. The Configure & Install VRA dialog is displayed. Note: If you selected a cluster or multiple hosts, only the first host in the displayed list is installed. Specify the following Target Host Details: Host The target ESX/ESXi host for the VRA. The drop-down displays the hosts managed by the vcenter Server which do not have a VRA installed, with the selected host displayed by default. Host Root Password The password used to access the host for the root user. This field is required for ESXi 4.x and 5.x hosts. This field is disabled for ESX 4.x hosts. When the checkbox at the side is checked the password is displayed as asterisks. The password is used by the Zerto Virtual Manager when deploying and upgrading the VRA on this host. Also, root access is required in case the Zerto host component is down and needs an automatic restart. The Zerto Virtual Manager checks the password is valid once a day. If the password was changed, an alert is triggered, requesting the user enter the new password. Datastore The datastore that the VRA will use for mirror virtual machines and for its journal. You can install more than one VRA on the same datastore. Network The network used to access the VRA. Amount of VRA RAM The amount of memory to allocate to the VRA. The amount determines the maximum buffer size for buffering IOs written by the protected virtual machines by the Initial Configuration 35
Install Virtual Replication Appliances protecting VRA, before they are sent over the network to the recovery VRA. The recovery VRA also buffers the incoming IOs until they are written to the journal. Amount of VRA RAM VRA Buffer Pool Size 1GB 2GB 3GB 461MB 1485MB 2509MB The protecting VRA can use 90% of the buffer for IOs to send over the network and the recovery VRA can use 75% of the buffer. That is, for example, a protecting VRA defined with 2GB of RAM can buffer approximately 1337MB before the buffer is full and a Bitmap Sync is required. VRA Group Specify the VRA Group as free text to identify the group or select from a previously specified group. You group VRAs together when VRAs use different networks so they can be grouped by network, for example when the same vcenter Server supports two datacenters with separate networks and you are replicating from one datacenter to the second datacenter. The group name is free text you use to identify the group. Note: The priority assigned to a VPG dictates the bandwidth used. The Zerto Virtual Manager distributes bandwidth among the VRAs based on this priority and the VPGs with higher priorities are handled before writes from VPGs with lower priorities. Specify the following VRA Network Details: Configuration Either have the IP address allocated via a static IP address or a DHCP server. If you select the Static option, which is the recommended option, enter the following: Address The IP address for the VRA. Subnet Mask The subnet mask for the network. The default value is 255.255.255.0. Default Gateway The default mask for the network. 4. Click Install. The installation starts and the status is displayed in the VRA Status field in the VRAs tab. Initial Configuration 36
Install Virtual Replication Appliances This process includes a number of tasks, which you can see in the recent tasks list in the Zerto GUI. 5. Repeat steps 3 and 4 to add a VRA to every ESX/ESXi host that hosts virtual machines for which you want replication. Note: It is recommended to install a VRA on every listed ESX/ESXi host. In the above diagram an alert is issued after the first VRA is installed because it is recommended to install a VRA on every host in the cluster. The alert is automatically removed when all the hosts have VRAs installed. You can display a list of hosts with VRAs installed along with the hosts still requiring a VRA to be installed by toggling Show hosts without a VRA installed at the bottom left of the tab to On. After a VRA has been installed on the site the left panel in the Summary tab displays the name and IP address of the site and information about what is protected on the site. Initial Configuration 37
Pair Sites to Enable Replicating From One Site to Another Site Pair Sites to Enable Replicating From One Site to Another Site Note: When a customer is using a Cloud Service Provider to manage the disaster recovery, the pairing is done during the registration of Zerto Virtual Replication, described in Register Zerto Virtual Replication, on page 31. Zerto Virtual Replication can be installed at multiple sites and each of these sites can be paired to any of the other sites enabling enterprises to protect virtual machines across multiple vcenters. In this case the sites must be paired as described in the following procedure. When a single vcenter is used, for example with remote branch offices, when replicating from one datacenter to another datacenter, both managed by the same vcenter Server, you have to enable replication to the same vcenter Server and pairing is not required. In this case, replication to the same vcenter must be set in the Advanced Settings dialog. To pair the sites for the first time: 1. In the Zerto GUI, in the Summary tab click the Pair button in the right panel. The Manage Sites dialog is displayed. 1 2. Click the Add New Site button. The Add Site dialog is displayed. 1. The Manage Sites dialog enables pairing to multiple sites. The number of sites you can pair with is determined by the license agreement. Initial Configuration 38
Pair Sites to Enable Replicating From One Site to Another Site 3. Specify the following: Remote Site ZVM IP Address IP address or host name of the remote site to pair to. The remote site is the site where the remote Zerto Virtual Manager is installed. Port The TCP port communication between the sites. Enter the port that was specified during the installation. The default port during the installation was 9081. 4. Click the Pair button. The sites are paired, the process being reflected in the Status column. Once paired the status changes to Paired meaning that the Zerto Virtual Manager for the local vcenter Server is connected to the Zerto Virtual Manager on the remote server. 5. Click the Close button. After the pairing completes the content of the Zerto tab for the vcenter node changes to present summary information about the paired site. Initial Configuration 39
Pair Sites to Enable Replicating From One Site to Another Site Note: When the local site is paired with multiple sites, the remote site area, on the right, specifies multiple sites and a site name and IP address is not displayed. After pairing, each Zerto Virtual Manager can manage up to 5000 virtual machines, either being protected by, or recovered to, the Zerto Virtual Manager. To enable replication to the same vcenter Server: 1. In the Zerto GUI, click the configuration (cog) button in the top right of the header. The Site Settings dialog is displayed. 2. Click Advanced Settings. The Advanced Settings dialog is displayed. 3. Check the Enable Replication to Self checkbox. 4. Click Save. 5. Close the Site Settings dialog. The Zerto Virtual Manager when used to protect to itself can manage the protection of up to 5000 virtual machines. Initial Configuration 40
Set Up a Remote Site Set Up a Remote Site When you are recovering to a remote site, and not the same site, you set up a remote site by pairing to the site as described in Pair Sites to Enable Replicating From One Site to Another Site, on page 38 and then installing VRAs in the site. To install VRAs on ESX/ESXi hosts in the remote site: Repeat the procedure, Install Virtual Replication Appliances, on page 33, via the Zerto GUI for the remote site vcenter Server. If you install a VRA on a remote site before pairing the site, you have to enter the license to use Zerto Virtual Replication, as described in Register Zerto Virtual Replication, on page 31. Note: A cloud service provider, using Zerto Cloud Manager can install VRAs on all the cloud sites from within the Zerto Cloud Manager. Initial Configuration 41
Chapter 4: Upgrading Zerto Virtual Replication Zerto Virtual Replication release regular updates. In addition, VMware also releases new versions of their products which can impact on Zerto Virtual Replication. This chapter describes the different options for different upgrade scenarios. You can only upgrade to the next version of Zerto Virtual Replication or any update within the version. All releases prior to version 3.0 are considered versions and not updates: 2.0, 2.0U1, 2.0U2, etc. As of version 3.0, update versions, 3.0U1, 3.0U2, etc., are considered, for upgrade purposes, as the same version. Thus, Zerto Virtual Replication 2.0U4 and 2.0U5 are different versions while Zerto Virtual Replication update versions 3.0U3, 3.0U4 are considered one version. For example, upgrading directly from 2.0U5 to 3.1 is not possible, since 2.0U5 can only be directly upgraded to 3.0Ux, but upgrading directly from 3.1 to 3.1U2 is possible. The following topics are described in this chapter: Upgrading Zerto Virtual Replication, below. Upgrading VRAs, on page 47 Upgrading or Reinstalling VMware Components, on page 49. A Zerto Virtual Manager can be used with a different version on another site, either one version higher or lower than the version installed on this site. Thus, for example, version 3.0U5 of Zerto Virtual Replication can be used with Zerto Virtual Replication versions 2.0U5, 3.0 (including all the upgrades, 3.0U1, etc.) and 3.1 (including all the upgrades, 3.1U1, etc.). Upgrading Zerto Virtual Replication Note: Zerto Virtual Replication features aimed at cloud service providers, such as Zerto Cloud Connectors and masking, were moved to the Zerto Cloud Manager as of Zerto Virtual Replication version 3.0. If Zerto Cloud Connectors and masking were not implemented at the site, you can upgrade, as described below. If a Zerto Cloud Connector or masking was implemented, refer to Zerto Virtual Replication Zerto Cloud Manager Installation for upgrade details after upgrading Zerto Virtual Replication, described below. 42
Upgrading Zerto Virtual Replication Before Upgrading Zerto Virtual Replication Before upgrading to a new version, either by installing the new version over the existing version or by uninstalling the existing version and then installing the new version, it is recommended to do the following: Clear the Microsoft Internet Explorer cache of temporary internet files. Not clearing the cache of temporary files can result in problems when accessing the Zerto Virtual Manager via the vsphere Client console. Make sure that all VPGs are in Protecting state and not in a sync state, such as Delta Sync, or an error state, such as Missing Configuration. The installation checks for an existing installation and if an existing installation is identified, that is one version lower than the new version or the same version, you can upgrade, reinstall or uninstall the existing version. Upgrading the Current Installation The defined Virtual Replication Appliances and protected virtual machines, along with all other information, such as checkpoints, journals, site and pairing information, are kept. The upgrade is performed without disrupting the protection, but no new checkpoints are written to the journal, resulting in alerts, even if only one of the sites was affected. Zerto Virtual Replication alerts might be issued stating that the journal history and RPO do not meet the specified targets. When the upgrade has completed, the VPG definitions are upgraded to the new version. Also, any customization of Zerto Virtual Replication alarms is maintained during an upgrade except for the Send a notification email action which is removed. Email notifications for alarms configured in the Zerto GUI, in the Advanced Settings dialog, are maintained during an upgrade. When upgrading Zerto Virtual Replication, the VRAs that were installed in the previous version are not upgraded. Zerto Virtual Replication enables VRAs installed with the previous version of Zerto Virtual Replication to work with VRAs installed with the current version of Zerto Virtual Upgrading Zerto Virtual Replication 43
Upgrading Zerto Virtual Replication Replication in any combination of VRAs (all from one version or a mix of VRA versions) as long as the VRAs are only one version higher or lower than the version of Zerto Virtual Replication installed on this site. It is recommended to upgrade the VRAs to be consistent with the latest version and this can be done in the Manage VRAs dialog as described in Upgrading VRAs, on page 47. If the vsphere Client console was open during the upgrade, close it and reopen it to ensure you have the upgraded Zerto GUI. Note: When using the Zerto Cloud Manager, it is recommended to upgrade the Zerto Cloud Manager to be consistent with the latest version as described in the Zerto Cloud Manager Installation Guide. Re-installing the Current Installation If the version is the same as the installed version, you can reinstall or uninstall the version. When reinstalling the version, all pairing, VRAs and VPGs defined for the site are removed. Use the Zerto Diagnostics utility export and import options, as described in Upgrading To More Than One Version Higher, below to save the settings. If the vsphere Client console was open during the reinstallation, close it and reopen it to ensure you have the upgraded Zerto GUI. Upgrading To More Than One Version Higher If you need to upgrade more than one version higher: Either upgrade to the next version, as described above, and repeat this until you upgrade to the required version, Or, use the Zerto Diagnostics utility import option to save the VPG definitions that have been defined, before uninstalling the old version of Zerto Virtual Replication. After the upgrade of Upgrading Zerto Virtual Replication 44
Upgrading Zerto Virtual Replication Zerto Virtual Replication, use the Zerto Diagnostics utility import option to re-implement these VPGs. Note: Make sure that all VPGs are in Protecting state and not in a sync state, such as Delta Sync, or an error state, such as Missing Configuration. To upgrade Zerto Virtual Replication using the Zerto Diagnostics utility: 1. Click Start > Programs > Zerto Virtual Replication > Zerto Diagnostics. The Zerto Virtual Replication Diagnostics menu dialog is displayed. 2. Select the Export Protection Group Settings option and click Next. Note: Zerto Virtual Replication regularly exports settings to the Zerto_Installation_Folder\Zerto Virtual Replication\ExportedSettings folder. You can use the last exported file. The default Zerto_Installation_Folder is C:\Program Files\Zerto. 3. Select the destination for the file to contain exported settings and specify the Zerto Virtual Manager IP address and port where the VPGs are protecting virtual machines. 4. Click Next. The list of exported VPGs is displayed. 5. Click Done. 6. In the Zerto GUI delete the VPGs, keeping their target disks. Upgrading Zerto Virtual Replication 45
Upgrading Zerto Virtual Replication Note: If you did not export the settings, Zerto Virtual Replication regularly exports settings to the Zerto_Installation_Folder\Zerto Virtual Replication\ExportedSettings folder. You can use the last exported file as input to recreate the VPGs to this point in time. The default Zerto_Installation_Folder is C:\Program Files\Zerto. 7. Uninstall the existing Zerto Virtual Replication version. 8. Install the new Zerto Virtual Replication version. 9. Click Start > Programs > Zerto Virtual Replication > Zerto Diagnostics. The Zerto Virtual Replication Diagnostics menu dialog is displayed. 10. Select the Import Protection Group Settings option. 11. Click Next. 12. Select the file previously exported and enter the Zerto Virtual Manager IP address and port specified when exporting the VPGs. 13. Click Next. The list of exported VPGs is displayed. 14. Select the VPGs to import. Only VPGs with names that are not already defined can be imported. VPGs in the import files with the same name as an existing VPG are displayed in the list disabled. Upgrading Zerto Virtual Replication 46
Upgrading VRAs 15. Click Next. The list of imported VPGs is displayed. If the VPG could not be imported the reason for the failure is specified. 16. Click Done. Upgrading VRAs When upgrading Zerto Virtual Replication, the VRAs that were installed in the previous version are not upgraded automatically. If a newer version of the installed VRAs exists, you can continue to use the current VRAs with the new version of Zerto Virtual Replication or upgrade these VRAs from within the Zerto GUI. VRAs installed with the previous version of Zerto Virtual Replication can work with VRAs installed with the current version of Zerto Virtual Replication in any combination of VRAs (all from one version or a mix of VRA versions) as long as the VRAs are only one update higher or lower than the version of Zerto Virtual Replication installed on this site. Zerto recommends that you always upgrade the VRAs to be consistent with the latest version. Not all new installations of Zerto Virtual Replication requires upgrading VRAs. You can see if an upgrade is available in the VRAs tab, in the VRA Version column. An alert is also issued both on the site with the old VRA installed and on any paired site with this site. Move the mouse over the Outdated value to display the VRA version as a tooltip. Considerations when upgrading VRAs: VRAs managing protected virtual machines: Either vmotion the protected virtual machines and datastores managed by the VRA to another host with a VRA, or upgrade the VRA without vmotioning the virtual machines and a Delta Sync is performed following the upgrade. Upgrading a VRA that manages the recovery of virtual machines results in a Bitmap Sync being performed after the upgrade. Note that the time to upgrade a VRA is short so the Bitmap Sync should also be quick. Upgrading Zerto Virtual Replication 47
Upgrading VRAs To upgrade VRAs: 1. For a VRA protecting virtual machines and vmotioning the protected virtual machines: Remove affinity rules for protected virtual machines on the host with the VRA to be upgraded and vmotion these protected machines from the host to another host with a VRA. 2. In the Zerto GUI, either select the VRAs to upgrade in the VRAs tab or for a single VRA display the VRA details by clicking the VRA Name link in the VRAs tab, and click Actions and then click Upgrade. The Upgrade VRAs dialog is displayed, listing the selected VRAs and whether an upgrade is available. 3. Review the list and deselect any VRAs that you decide not to upgrade. 4. Click Upgrade Selected VRAs. The upgrade progress is displayed in the VRAs tab. A Delta Sync, for VRAs protecting virtual machines, or a Bitmap Sync, for VRAs managing recovery, is performed following the upgrade. Note: The VRA name does not change, even if the naming convention in the latest version is different. Upgrading Zerto Virtual Replication 48
Upgrading or Reinstalling VMware Components Upgrading or Reinstalling VMware Components When changing the version of the vcenter Server, you can either upgrade the vcenter Server or reinstall it. Upgrading a vcenter Server When you upgrade a vcenter Server, preserving the vcenter database, the Zerto Virtual Replication components are not affected and protection continues without you needing to perform any additional procedures. Zerto recommends upgrading a vcenter Server in preference to reinstalling it. Reinstalling a vcenter Server If, for whatever reason, you need to reinstall the vcenter Server, including rebuilding the database, contact Zerto for help throughout the reinstallation. Upgrading or Reinstalling a Host When upgrading or reinstalling a host with an active VRA, change the recovery host of every virtual machine in every VPG that is recovering to this host, to avoid a Delta Sync after the host has been upgraded and the VRA started up. You can change the host within the Zerto GUI, described below or by using cmdlets as described in Zerto Virtual Replication PowerShell Cmdlets Guide. Upgrading Zerto Virtual Replication 49
Upgrading or Reinstalling VMware Components To change a host VRA: 1. In the Zerto GUI, either select the VRA to change in the VRAs tab or display the VRA details by clicking the VRA Name link in the VRAs tab, and click Actions and then click Change VM Recovery VRA. The Change Target Host dialog is displayed, listing all the virtual machines that require a change to the recovery host. 2. Review the list and select the virtual machines to change the target host to another specified target host. Upgrading Zerto Virtual Replication 50
Upgrading or Reinstalling VMware Components 3. Select the target host for these virtual machines in the Select the replacement host drop-down list. You can move some virtual machines to one replacement target host and by repeating the operation, move other virtual machines to a different target host. Validation is performed to make sure the selected target host can be used, for example the datastores used by both the VRAs are accessible from both hosts. Any implications of the change, such as whether synchronization might be required after the change is also displayed. 4. Click OK. 5. Repeat this procedure from step 2 for all the virtual machines. The VPG target host definitions are changed and the affected target data transferred to the changed VRAs. During the change procedure you cannot edit the affected VPGs nor attempt a failover, move, failover test or clone operation. VRAs installed on ESXi 4.x and 5.x hosts require a password to access the host. If the host password changes, for example when he host is upgraded, the VRA has to be updated with the new password, as described in Zerto Virtual Manager Administration Guide. To change the host password required by a VRA: 1. In the Zerto GUI, either select the VRA to edit in the VRAs tab or display the VRA details by clicking the VRA Name link in the VRAs tab, and click Actions and then click Edit. The Edit VRA dialog is displayed. 2. Edit the host root password: Host Root Password Specify the new password. 3. Click Save. There is also a procedure to change the passwords for more than one host at one time, described in the Zerto Virtual Manager Administration Guide. Upgrading Zerto Virtual Replication 51