VMware vSphere Replication Administration vSphere Replication 5.
VMware vSphere Replication Administration You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation, submit your feedback to docfeedback@vmware.com VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com Copyright © 2012–2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc.
Contents vSphere Replication Administration Updated Information 6 7 1 Overview of VMware vSphere Replication 8 Contents of the vSphere Replication Appliance vSphere Replication Client Plug-In Source and Target Sites 9 10 10 How vSphere Replication Works 11 2 vSphere Replication Roles and Permissions 14 Assign vSphere Replication Roles to Users Assign VRM Replication Viewer Role 14 14 Assign VRM Virtual Machine Replication User Role Assign VRM Virtual Machine Recovery User Role 15 15 Clone Exis
VMware vSphere Replication Administration 6 Upgrading vSphere Replication 35 Upgrade vSphere Replication by Using the Downloadable ISO Image 36 Update vCenter Server IP Address in vSphere Replication Management Server Update vSphere Replication By Using vSphere Update Manager Update vSphere Replication by Using the VAMI 37 37 39 7 Reconfigure the vSphere Replication Appliance 42 Reconfigure General vSphere Replication Settings 43 Change the SSL Certificate of the vSphere Replication Appliance Chang
VMware vSphere Replication Administration vSphere Replication Events and Alarms 77 Solutions for Common vSphere Replication Problems VMware, Inc.
vSphere Replication Administration vSphere Replication Administration provides information about installing, configuring, and using VMware vSphere Replication. Intended Audience This information is intended for anyone who wants to protect the virtual machines in their virtual infrastructure by using vSphere Replication. The information is written for experienced Windows or Linux system administrators who are familiar with virtual machine technology and datacenter operations. VMware, Inc.
Updated Information vSphere Replication Administration is updated with each release of the product or when necessary. This table provides the update history of vSphere Replication Administration. Revision Description 7 NOV 2017 Updated the information about vSphere High Availability in topic Compatibility of vSphere Replication with Other vSphere Features.
Overview of VMware vSphere Replication 1 VMware vSphere Replication is an extension to VMware vCenter Server that provides hypervisor-based virtual machine replication and recovery. vSphere Replication is an alternative to storage-based replication.
VMware vSphere Replication Administration You can use VMware Virtual SAN datastores as target datastores and choose destination storage profiles for the replica virtual machine and its disks when configuring replications. Note VMware Virtual SAN is a fully supported feature of vSphere 5.5u1. n You can use Virtual SAN in production environments with vSphere Replication 5.5.1 and vSphere 5.5u1. n Virtual SAN is an experimental feature in vSphere 5.5.
VMware vSphere Replication Administration You can use vSphere Replication immediately after you deploy the appliance. The vSphere Replication appliance provides a virtual appliance management interface (VAMI) that you can use to reconfigure the appliance after deployment, if necessary. For example, you can use the VAMI to change the appliance security settings, change the network settings, or configure an external database. You can deploy additional vSphere Replication Servers using a separate .
VMware vSphere Replication Administration Connecting Source and Target Sites Before you replicate virtual machines between two sites, you must connect the sites. If the sites use different SSO, you must provide authentication details for the target site, including IP or FQDN , user and password information. When connecting sites, users at both sites must have VRM remote.Manage VRM privilege.
VMware vSphere Replication Administration Figure 1‑1.
VMware vSphere Replication Administration Figure 1‑3. Replication to a Shared Target Site Source Site Replication vCenter Server VR Appliance VM ESXi ESXi VR Agent VR Agent Target Site ESXi VR Agent vSphere Web Client Source Site Replication vCenter Server VR Appliance Replicate changed blocks vCenter Server VR Appliance VM VM ESXi ESXi ESXi ESXi VR Agent VR Agent Network File Copy Network File Copy VM ESXi VR Agent VMware, Inc.
vSphere Replication Roles and Permissions 2 You can use any predefined roles or clone an existing role, and add or remove privileges from it based on your needs.
VMware vSphere Replication Administration 4 Log in as the user with the assigned VRM replication viewer role. The user cannot perform modifications on the configured replication, nor on the replication sites. Running operations result in Permission to perform this operation was denied. Assign VRM Virtual Machine Replication User Role In this example, you create a vSphere Replication user who can only configure replication between sites and use a specific datastore on the target site.
VMware vSphere Replication Administration Procedure 1 Log in as the Administrator user on the target site. 2 Select vCenter > Manage > Permissions and assign to this user the VRM virtual machine recovery user role with the propagate option. 3 Log in as that user on the target site. 4 Select Monitor > vSphere Replication > Incoming Replications, select the replication, and start recovery. 5 Select Recover with latest available data and follow the prompts to finish the recovery.
VMware vSphere Replication Administration Table 2‑1. vSphere Replication Roles Role Actions that this Role Permits Privileges that this Role Includes VRM replication viewer n View replications. VRM remote.View VR n Cannot change replication parameters. VRM remote.View VRM VRM datastore mapper.View Host.vSphere Replication.Manage replication Virtual machine.vSphere Replication.Monitor replication VRM virtual machine replication user n View replications. Datastore.
VMware vSphere Replication Administration Table 2‑1. vSphere Replication Roles (Continued) Role Actions that this Role Permits Privileges that this Role Includes VRM administrator Incorporates all vSphere Replication privileges. VRM remote.Manage VR VRM remote.View VR VRM remote.Manage VRM VRM remote.View VRM VRM datastore mapper.Manage VRM datastore mapper.View VRM diagnostics .Manage VRM session .Terminate Datastore.Browse datastore Datastore.
VMware vSphere Replication Administration Table 2‑1. vSphere Replication Roles (Continued) Role Actions that this Role Permits Privileges that this Role Includes VRM target datastore user Configure and reconfigure replications. Datastore.Browse datastore Datastore.Low level file operations Used on target site in combination with the VRM virtual machine replication user role on both sites. VRM virtual machine recovery user Recover virtual machines. Datastore.Browse datastore Datastore.
vSphere Replication System Requirements 3 The environment in which you run the vSphere Replication virtual appliance must meet certain hardware requirements. vSphere Replication is distributed as a 64-bit virtual appliance packaged in the .ovf format. It has a dual core CPU, a 10GB and a 2GB hard disk, and 4GB of RAM. Additional vSphere Replication Servers require 512MB of RAM. You must deploy the virtual appliance in a vCenter Server environment by using the OVF deployment wizard on an ESXi host.
VMware vSphere Replication Administration If you have the correct vSphere license, there is no limit on the number of virtual machines that you can replicate by using vSphere Replication. You cannot use vSphere Replication to replicate virtual machines on ESXi hosts that do not have the correct vSphere license.
VMware vSphere Replication Administration Table 3‑1. Compatibility of vSphere Replication with Other vSphere Features vSphere Feature Compatible with vSphere Replication vSphere vMotion Yes You can migrate replicated virtual machines by using vMotion. Replication continues at the defined recovery point objective (RPO) after the migration is finished.
VMware vSphere Replication Administration vSphere Replication Compatibility with Other Software vSphere Replication is compatible with versions of ESXi Server, vCenter Server, Site Recovery Manager, databases, and Web browsers. vSphere Replication is compatible with the same versions as vCenter Server, except for ESXi: vSphere Replication requires ESXi 5.0 or greater. See: n VMware Product Interoperability Matrixes at http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.
VMware vSphere Replication Administration Dataset Size vSphere Replication might not replicate every virtual machine nor every VMDK file in the replicated virtual machines. To evaluate the dataset size that vSphere Replication replicates, calculate the percentage of the total storage used for virtual machines, then calculate the number of VMDKs within that subset that you have configured for replication.
VMware vSphere Replication Administration You can assume that only about 70% of a link is available for traffic replication. This means that on a 10Mb link you obtain a link speed of about 3GB per hour. On a 100Mb link you obtain a speed of about 30GB per hour. To calculate the bandwidth, see Calculate Bandwidth for vSphere Replication.
Installing vSphere Replication 4 vSphere Replication uses the replication technologies included in ESXi with the assistance of virtual appliances to replicate virtual machines between source and target sites. To use vSphere Replication, you must deploy the vSphere Replication appliance on an ESXi host using the vSphere Web Client. The vSphere Replication appliance registers with the corresponding vCenter Server instance.
VMware vSphere Replication Administration n Download and install the Client Integration Plug-in from the login page of the vSphere Web Client. If the plug-in is already installed, the link does not appear. n In the vSphere Web Client, select the vCenter Server instance on which you are deploying vSphere Replication and click Manage > Settings > Advanced Settings. Verify that the VirtualCenter.FQDN value is set to a fully-qualified domain name or a literal address.
VMware vSphere Replication Administration vSphere Replication is ready for use immediately after you deploy the appliance. No manual configuration or registration is required. What to do next Perform optional reconfiguration of the vSphere Replication appliance by using the virtual appliance management interface (VAMI). You can install a certificate, change the appliance root password, change the trust policy, or configure vSphere Replication to use an external database.
VMware vSphere Replication Administration n Stop all existing outgoing or incoming replications to the site. n Disconnect any connections to other vSphere Replication sites. Procedure 1 Connect to the VAMI of the vSphere Replication appliance in a Web browser. The URL for the VAMI is https://vr-appliance-address:5480. 2 Select the Configuration tab. 3 Click Unregister from vCenter Server. 4 In the vSphere Web Client, power off and delete the vSphere Replication appliance.
VMware vSphere Replication Administration What to do next Deploy a new vSphere Replication appliance and perform any optional configuration. VMware, Inc.
Deploying Additional vSphere Replication Servers 5 Depending on replication traffic, you might need to deploy one or more additional vSphere Replication servers.
VMware vSphere Replication Administration 3 Review the virtual appliance details and click Next. 4 Follow the prompts to select a destination host, datastore, and disk format for the virtual appliance. 5 Enter a password for the appliance that is at least eight characters long. 6 Set the network properties. Select DHCP or set a static IP address. You can change network settings after deployment in the VAMI.
VMware vSphere Replication Administration Prerequisites You deployed an optional vSphere Replication server in addition to the vSphere Replication appliance, and the server is powered on. Procedure 1 Log into the VAMI of the vSphere Replication server in a Web browser. A sample address might be https://:5480. 2 Log in to the vSphere Replication server configuration interface as root. Use the root password you set when you deployed the vSphere Replication server.
VMware vSphere Replication Administration Procedure 1 In Manage > vSphere Replication, click the Replication Servers tab and find the vSphere Replication server in the list. 2 Select the server and click Unregister the selected vSphere Replication Server. 3 In the Hosts and Clusters view, power off and delete the vSphere Replication server virtual machine. Disable the Embedded vSphere Replication Server vSphere Replication includes an embedded vSphere Replication Server by default.
Upgrading vSphere Replication 6 You upgrade the vSphere Replication appliance and any additional vSphere Replication servers by using a downloaded ISO image. The downloadable ISO image is the only means of upgrading from vSphere Replication 5.1.x to vSphere Replication 5.5.x. You cannot upgrade vSphere Replication from version 5.1.x to to version 5.5.x by using vSphere Update Manager or the virtual appliance management interface (VAMI) of the vSphere Replication appliance.
VMware vSphere Replication Administration Upgrade vSphere Replication by Using the Downloadable ISO Image You upgrade the vSphere Replication appliance and the vSphere Replication server by using a downloadable ISO image. Prerequisites n Upgrade the vCenter Server instance that vSphere Replication extends. n Download the VMware-vSphere_Replication-5.5.x.x-build_number.iso ISO image from the vSphere downloads page.
VMware vSphere Replication Administration Update vCenter Server IP Address in vSphere Replication Management Server After you upgrade vCenter Server and the vSphere Replication appliance, if the vCenter Server certificate or the IP address changed during the upgrade, you must perform additional steps. To update the vCenter Server certificate, see vSphere Replication is Inaccessible After Changing vCenter Server Certificate.
VMware vSphere Replication Administration Procedure 1 In the Update Manager interface, click the Configuration tab, click Download Settings, and select the VMware VAs download source. You can deselect all other download sources. 2 Click Apply and click Download Now to download the latest updates. 3 Click the Baselines and Groups tab, select VMs/VAs, and click Create to create an update baseline for virtual appliances.
VMware vSphere Replication Administration Update vSphere Replication by Using the VAMI You can update vSphere Replication from version 5.5.x to a later 5.5.x update release by using the virtual appliance management interface (VAMI) of the vSphere Replication management server. Important Do not select the option in Update > Settings in the VAMI to automatically update vSphere Replication.
VMware vSphere Replication Administration 7 Repeat the process on the target site. What to do next If you configured vSphere Replication to accept only certificates that are signed by a trusted certificate authority, after an update you must reconnect the vSphere Replication appliances. If your infrastructure uses more than one vSphere Replication server, update the vSphere Replication server appliances.
VMware vSphere Replication Administration 6 When the update finishes, select the System tab, and click Reboot. 7 Repeat the procedure to update any other vSphere Replication server instances. VMware, Inc.
Reconfigure the vSphere Replication Appliance 7 If necessary, you can reconfigure the vSphere Replication appliance settings by using the virtual appliance management interface (VAMI). You provide the settings for the vSphere Replication appliance in the Deploy OVF wizard when you deploy the appliance. If you selected automatic configuration of the appliance using an embedded database, you can use the vSphere Replication appliance immediately after deployment.
VMware vSphere Replication Administration n Reconfigure vSphere Replication to Use an External Database The vSphere Replication appliance contains an embedded vPostgreSQL database that you can use immediately after you deploy the appliance, without any additional database configuration. If necessary, you can reconfigure vSphere Replication to use an external database.
VMware vSphere Replication Administration 6 Type the address of the vCenter Server instance to use with this installation. You must use the same address format that you used when you installed vCenter Server. For example, if you used a fully qualified domain name during installation, you must use that FQDN. If you used an IP address, you must use that IP address. 7 Type an administrator email address. 8 Click Save and Restart Service to apply the changes.
VMware vSphere Replication Administration 5 (Optional) To enforce verification of certificate validity, select the Accept only SSL certificates signed by a trusted Certificate Authority check box. See vSphere Replication Certificate Verification for details of how vSphere Replication handles certificates. 6 7 Generate or install a new SSL certificate. Option Action Generate a self-signed certificate Click Generate and Install.
VMware vSphere Replication Administration vSphere Replication can trust remote server certificates either by verifying the validity of the certificate and its thumbprint or by verifying the thumbprint only. The default is to verify by thumbprint only.
VMware vSphere Replication Administration n If you use your own certificate authority, for example one that you create and manage with the OpenSSL tools, you must add the fully qualified domain name or IP address to the OpenSSL configuration file. n If the fully qualified domain name of the appliance is VR1.example.com, add subjectAltName = DNS: VR1.example.com to the OpenSSL configuration file.
VMware vSphere Replication Administration 6 Click Apply to change the password. Change Keystore and Truststore Passwords of the vSphere Replication Appliance To increase security, you can change the default passwords of the vSphere Replication appliance keystore and truststore. If you copy the keystores from the appliance to another machine, VMware recommends that you change the passwords before the copy operation. The keystore and truststore passwords might be stored in an access restricted config file.
VMware vSphere Replication Administration 8 Obtain the current hms-truststore password. # /opt/vmware/hms/hms-configtool -cmd list | grep truststore Example of the output: hms-truststore-password = old_password 9 Change the hms-truststore password. # /usr/java/default/bin/keytool -storepasswd -storepass old_password -new new_password -keystore /opt/vmware/hms/security/hms-truststore.jks 10 Update the configuration with the new password.
VMware vSphere Replication Administration 5 6 Click Address to review or modify IPv4 and IPv6 address settings. IP Address Type Option Description IPv4 DHCP DHCP is not recommended if the IP address of the appliance might change if it reboots. IPv4 Static With a static IPv4 address, you can modify the IP settings, DNS settings, netmask, and host name information. IPv4 None Deactivates IPv4 addresses.
VMware vSphere Replication Administration 2 Type the root user name and password for the server. 3 Click the System tab. 4 Click Information. You can review information about vSphere Replication, and reboot or shutdown the appliance.
VMware vSphere Replication Administration If you reinitialize the database after you deploy vSphere Replication, you must go to the vSphere Replication virtual appliance management interface (VAMI) to reconfigure vSphere Replication to use the new database connection. Prerequisites n Verify that the vSphere Replication appliance is powered on. n You must have administrator privileges to configure the vSphere Replication appliance.
VMware vSphere Replication Administration Databases that vSphere Replication Supports The vSphere Replication virtual appliance includes the VMware standard embedded vPostgreSQL database. You can also configure vSphere Replication to use an external database. Automated migration between the embedded database and any external databases is not supported in any direction. If you must configure an external database, you must manually migrate the data or manually recreate all replications.
VMware vSphere Replication Administration 3 Enable TCP on the database instance. 4 Set a TCP port. Option Action Static TCP port Set the TCP port to the default of 1433. Dynamic TCP port a Use a named instance of SQL Server. You can only use dynamic ports with a named instance of SQL Server. b Select the Show DB URL check box in the virtual appliance management interface (VAMI) of the vSphere Replication appliance. c Modify the DB URL value.
VMware vSphere Replication Administration Use the Embedded vSphere Replication Database If you configured vSphere Replication to use an external database, you can reconfigure vSphere Replication to use the embedded database. The vSphere Replication appliance includes an embedded vPostgreSQL database.
Replicating Virtual Machines 8 With vSphere Replication you can replicate virtual machines from a source site to a target site. You can set a recovery point objective (RPO) to a certain time interval depending on your data protection needs. vSphere Replication applies all changes made to virtual machines configured for replication at the source site to their replicas at the target site. This process reoccurs at the RPO interval that you set.
VMware vSphere Replication Administration n Stop Replicating a Virtual Machine n Reconfiguring Replications How the Recovery Point Objective Affects Replication Scheduling The Recovery Point Objective (RPO) value you set during replication configuration affects replication scheduling. If you set an RPO of x minutes, the latest available replication instance can never reflect a state that is older than x minutes.
VMware vSphere Replication Administration You can also use the PIT instances to recover the last known good state of a database. Note vSphere Replication does not replicate virtual machine snapshots. Figure 8‑1.
VMware vSphere Replication Administration Configuring Replications by Using Replication Seeds When copying replication seed files to the target datastore, you can use the vSphere Web Client to create a new root folder on a Virtual SAN datastore, or place the files in an existing folder. When you configure replications that use replication seeds, you must select the folder by using its UUID name. Selecting the user-friendly folder names is not supported.
VMware vSphere Replication Administration See the VMware Virtual SAN Design and Sizing Guide at http://www.vmware.com/products/virtual-san/resources.html for explanations of objects, components, mirrors, witnesses, and Virtual SAN storage policies.
VMware vSphere Replication Administration Replicating a Virtual Machine in a Single vCenter Server Instance You can use vSphere Replication to replicate a virtual machine in a single vCenter Server even if the vCenter Server instance has only one host in its inventory. When you configure replication in a single vCenter Server instance, you can select the source site as the target site for replication. You then configure replication in the same way as for an infrastructure with a source and a target site.
VMware vSphere Replication Administration You can configure virtual machines to replicate to a Virtual SAN datastore on the target site. See Using vSphere Replication with Virtual SAN Storage for the limitations when using vSphere Replication with Virtual SAN. Note VMware Virtual SAN is a fully supported feature of vSphere 5.5u1. n You can use Virtual SAN in production environments with vSphere Replication 5.5.1 and vSphere 5.5u1. n Virtual SAN is an experimental feature in vSphere 5.5.
VMware vSphere Replication Administration 10 Review the settings and click Finish to establish replication. vSphere Replication starts an initial full synchronization of the virtual machine files to the designated datastore on the target site. Configure Replication for Multiple Virtual Machines You can configure replication for multiple virtual machines using the multi-VM configure replication wizard.
VMware vSphere Replication Administration Prerequisites To replicate virtual machines using vSphere Replication, you must deploy the vSphere Replication appliance at the source and target sites. You must power on the virtual machines to begin replication. Procedure 1 On the vSphere Web Client Home page, click VMs and Templates. 2 Select a datacenter, click the Related Objects tab, then click the Virtual Machines tab. A list of virtual machines appears in the right pane.
VMware vSphere Replication Administration Move a Virtual Machine to a New vSphere Replication Server After configuring vSphere Replication, you can move replications to other vSphere Replication servers. You might do this to complete maintenance tasks on existing servers or to balance the load on the servers if one server becomes overloaded with replications. Prerequisites Other than the embedded vSphere Replication server, you must have an additional vSphere Replication server deployed and registered.
VMware vSphere Replication Administration Reconfiguring Replications You can reconfigure a replication to modify its settings. For example, you can reconfigure the replication to enable or disable a virtual machine disk file for replication, modify replication options, such as RPO, MPIT retention policy, or quiescing method. You can also specify a different target datastore for replica configuration and disk files.
VMware vSphere Replication Administration Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds vSphere Replication prevents you from resizing the virtual machine disk file during replication. If you did not use replication seeds during configuration of the target disk, vSphere Replication deletes the target disk when you stop the replication.
Performing a Recovery with vSphere Replication 9 With vSphere Replication, you can recover successfully replicated virtual machines at the target site. vSphere Replication performs a sequence of steps to recover replicated virtual machines. n If you perform a synchronization of the latest changes, vSphere Replication checks that the source site is available and source virtual machine is powered off before recovering the virtual machine on the target site.
VMware vSphere Replication Administration 3 Select whether to recover the virtual machine with all the latest data, or to recover the virtual machine with the most recent data from the target site. Option Description Recover with recent changes Performs a full synchronization of the virtual machine from the source site to the target site before recovering the virtual machine. Selecting this option avoids data loss, but it is only available if the data of the source virtual machine is accessible.
VMware vSphere Replication Administration After a successful recovery, vSphere Replication disables the virtual machine for replication if the source site is still available. When the virtual machine is powered on again it does not send replication data to the recovery site. To unconfigure the replication, select Stop replication. When the source virtual machine is no longer in the vCenter Server inventory, the replication is unconfigured.
Monitoring and Managing Replications in vSphere Replication 10 vSphere Replication provides a management interface where you can monitor and manage virtual machine replication and connectivity states for local and remote sites. The Home tab in vSphere Replication lists all vCenter Servers that are joined in the same SSO server and the status of each vSphere Replication appliance with the total number of replications.
VMware vSphere Replication Administration 3 Click the Summary tab. Replication States for Virtual Machines vSphere Replication shows the replication states of virtual machines that you configured for replication.
VMware vSphere Replication Administration Identifying Replication Problems in the Issues Tab You can view and troubleshoot possible vSphere Replication problems that might occur during replication at the Issues tab of the corresponding vCenter Server. Table 10‑1. Possible Replication Problems Problem Cause Solution Not Active The replication is not active because the virtual machine is powered off and a warning icon appears. Replication is not running for that virtual machine.
VMware vSphere Replication Administration Manage Replication Servers You can register new vSphere Replication servers in addition to the embedded one that is included with the vSphere Replication appliance by default. Prerequisites Verify that vSphere Replication is running. Procedure 1 Log in to the vSphere Web Client. 2 Select the vCenter Server to which the vSphere Replication appliance is registered. 3 Click Manage and click the vSphere Replication tab.
Troubleshooting vSphere Replication 11 Known troubleshooting information can help you diagnose and correct problems that occur while replicating and recovering virtual machines with vSphere Replication. If you have problems with deploying vSphere Replication, replicating or recovering virtual machines, or connecting to databases, you can troubleshoot them. To help identify the problem, you might need to collect and review vSphere Replication logs and send them to VMware Support.
VMware vSphere Replication Administration Shared Disk Support vSphere Replication cannot replicate virtual machines that share vmdk files in this release. Raw Device Mapping (RDM) vSphere Replication supports replicating RDMs in Virtual Compatibility Mode. RDMs in Physical Compatibility Mode cannot be configured for replication. Snapshots vSphere Replication does not replicate virtual machine snapshot hierarchy at the target site.
VMware vSphere Replication Administration Manually Access the vSphere Replication Logs You can copy and use the vSphere Replication logs for system monitoring and troubleshooting. A VMware support engineer might request these logs during a support call. Use SCP or Win SCP to copy log folders and files from the vSphere Replication appliance and all Additional vSphere Replication Servers. n /opt/vmware/hms/logs/ n /opt/vmware/var/log/lighttpd/ n /var/log/vmware/ n /var/log/boot.
VMware vSphere Replication Administration Table 11‑1. vSphere Replication Events (Continued) Categ ory Event Target com.vmware.vcHms.h ostUnconfiguredForH brEvent Info Folder Virtual machine is experiencing problems with vSphere Replication and must be reconfigured com.vmware.vcHms.v mMissingReplication ConfigurationEvent Error Virtual Machine VM cleaned up from vSphere Replication Virtual machine cleaned up from vSphere Replication configuration com.vmware.vcHms.
VMware vSphere Replication Administration Table 11‑1. vSphere Replication Events (Continued) Categ ory Event Target com.vmware.vcHms.v mRecoveredEvent Info Virtual Machine Datastore is not accessible for vSphere Replication Server com.vmware.vcHms.d atastoreInaccessibleE vent Error Datastore vSphere Replication handled a disk addition on a virtual machine vSphere Replication detected and handled the addition of a disk to virtual machine . Disks added are com.vmware.vcHms.
VMware vSphere Replication Administration Table 11‑1. vSphere Replication Events (Continued) Categ ory Event Target hbr.primary.AppQuies cedDeltaCompletedE vent Info Virtual Machine File-system consistent sync completed hbr.primary.FSQuiesc edDeltaCompletedEv ent Warni ng Virtual Machine Unquiesced crash consistent sync completed Unquiesced crash consistent sync completed. Quiescing failed or virtual machine is powered off. hbr.primary.
VMware vSphere Replication Administration Solutions for Common vSphere Replication Problems Known troubleshooting information can help you diagnose and correct problems with vSphere Replication. Error at vService Bindings When Deploying the vSphere Replication Appliance When you deploy the vSphere Replication appliance, you get an error at vService bindings in the Deploy OVF Template wizard.
VMware vSphere Replication Administration Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved You cannot resolve a connection error between the vSphere Replication appliance and SQL Server. Problem vSphere Replication might not be able to connect to SQL Server, and you have insufficient information to solve this problem. Cause Several issues can cause this problem, and initially available information about the problem is insufficient to affect a resolution.
VMware vSphere Replication Administration Solution Make sure that all hosts in the cluster are running ESXi 5.1 or newer before you use vMotion to move a Windows Server 2008 and Windows 8 virtual machine with application quiescing. Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores If you try to configure vSphere Replication on a virtual machine that includes two disks that are contained in different datastores, the configuration fails.
VMware vSphere Replication Administration Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0 Performance might be slow if you replicate a large number of virtual machines with a short Recovery Point Objective (RPO) to a single virtual machine file store (VMFS) datastore that is accessible by multiple hosts on the recovery site. Problem This problem occurs when running ESXi Server 5.0 on the recovery site.
VMware vSphere Replication Administration 2 If you cannot upgrade ESXi Server to version 5.1 or later, redistribute the replicated virtual machines or adjust their RPO. n Reduce the number of virtual machines with a short RPO that replicate to a single VMFS volume, for example by using a larger number of smaller datastores. n Increase the RPO of the virtual machines replicating to a single VMFS volume to create a longer harmonic mean RPO.
VMware vSphere Replication Administration Cause You cannot recover virtual machines with the same name in the same source and destination folder in the vCenter inventory. Solution Recover the virtual machine in a different VMs and Templates folder in the same datacenter. Optionally, after successful recovery, you can remove the old virtual machine from the vCenter inventory and drag the recovered virtual machine to the required virtual machine folder.
VMware vSphere Replication Administration Solution 1 Use the Managed Object Browser (MOB) to delete the vSphere Replication extension manually. 2 Redeploy the appliance and reconfigure the replications.
VMware vSphere Replication Administration e Type the correct managed object id of the appliance VM in Appliance VM MO value. Use the vCenter Server MOB to obtain the appliance id. f Click Save and Restart Service. If you use the VAMI solution, you must repeat the steps each time that you change the vSphere Replication certificate. Unexpected vSphere Replication Failure Results in a Generic Error vSphere Replication includes a generic error message in the logs when certain unexpected failures occur.
VMware vSphere Replication Administration Increase the Memory of the vSphere Replication Server for Large Deployments If you deploy an additional vSphere Replication server, you might need to increase the memory of the vSphere Replication server if that server manages large numbers of virtual machines. Problem vSphere Replication supports a maximum of 100 virtual machines per vSphere Replication server.
VMware vSphere Replication Administration Uploading a Valid Certificate to vSphere Replication Results in a Warning When you upload a custom certificate to the vSphere Replication appliance, you see a warning even if the certificate is valid. Problem When you use the virtual appliance management interface (VAMI) in Internet Explorer to upload certificates to the vSphere Replication appliance, you see a certificate error: The certificate installed with warnings.
VMware vSphere Replication Administration Generating Support Bundles Disrupts vSphere Replication Recovery If you generate a vSphere Replication log bundle and at the same time attempt to run a recovery, the recovery might fail. Problem In heavily loaded environments, generating log bundles can cause vSphere Replication connection problems during recovery operations. Recovery fails with the error VRM Server generic error. Please check the documentation for any troubleshooting information.
VMware vSphere Replication Administration vSphere Replication Does Not Display Incoming Replications When the Source Site is Inaccessible The list of incoming replications between two remote sites fails to populate when the connection to the source site is refused. Problem When you refresh the incoming replications list on a remote site soon after the connection to the source site has become unavailable, the replications do not display due to a communication error between the two sites.
VMware vSphere Replication Administration Solution Make sure the vSphere Replication appliance has access to port 80 on the storage hosts. For a list of ports that must be open for vSphere Replication, see vSphere Replication Network Ports. Anti-virus Agent in Firewall Terminates Virtual Machine Replication If a virtual machine contains virus information, an anti-virus agent in the firewall might detect the virus data and terminate the connection during replication.
VMware vSphere Replication Administration vSphere Web Client 5.1.x Non-Functioning Option Binds vSphere Replication Traffic to a Specific vmknic vSphere Web Client 5.1.x contains an option that binds vSphere Replication traffic to a specific vmknic. Problem If you use this option in vSphere Replication version 5.1.x and then upgraded to version 5.5.x, replication configuration fails due to the underlying connectivity issue. Solution Manually edit the esx.
VMware vSphere Replication Administration vSphere Replication Operations Run Slowly as the Number of Replications Increases As you increase the number of virtual machines that you replicate, vSphere Replication operations can run more slowly. Problem Response times for vSphere Replication operations can increase as you replicate more virtual machines. You possibly experience recovery operation timeouts or failures for a few virtual machines, and RPO violations.
