Known troubleshooting information can help you diagnose and correct problems with vSphere Replication. What to read next OVF Package Is Invalid and Cannot Be DeployedWhen you attempt to deploy OVF for the vSphere Replication appliance, an OVF package error might occur. vSphere Replication Service Fails with Unresolved Host ErrorIf the address of vCenter Server is not set to a fully qualified domain name (FQDN) or to a literal address, the vSphere Replication service can stop unexpectedly or fail to start after a reboot. Error Recovering Virtual Machine in a Single vCenter Server InstanceYou might receive an error message when you are recovering a virtual machine with the same name in a single vCenter Server instance. vSphere Replication RPO ViolationsYou might encounter RPO violations even if vSphere Replication is running successfully at the recovery site. vSphere Replication Appliance Extension Cannot Be DeletedIf you delete the vSphere Replication appliance virtual machine, the VRMS Appliance Management Interface is not available to delete the appliance extension that still exists in vCenter Server. vSphere Replication Does Not Start After Moving the HostIf you move the ESXi Server on which the vSphere Replication appliance runs to the inventory of another vCenter Server instance, vSphere Replication operations are not available. If you reinstall vCenter Server, vSphere Replication operations are also unavailable. Unexpected vSphere Replication Failure Results in a Generic ErrorvSphere Replication includes a generic error message in the logs when certain unexpected failures occur. Reconnecting Sites Fails If One of the vCenter Server Instances Has Changed Its IP Address When the vCenter Server address of one site changes, the connection status between two sites is displayed as Not connected and you cannot reconnect the sites. vSphere Replication Server Registration Takes Several MinutesvSphere Replication server registration might take a long time depending on the number of hosts in the vCenter Server inventory. Generating Support Bundles Disrupts vSphere Replication RecoveryIf you generate a vSphere Replication log bundle and at the same time attempt to run a recovery, the recovery might fail. vSphere Replication Operations Take a Long Time to CompleteSome vSphere Replication operations might take a long time to complete during a heavy load. vSphere Replication Operations Fail with Authentication ErrorAn error message appears when you try to configure a replication between two sites, though the sites are paired. vSphere Replication Does Not Display Incoming Replications When the Source Site Is InaccessibleThe list of incoming replications between two remote sites fails to populate when the connection to the local site is refused. vSphere Replication Is Inaccessible After Changing vCenter Server CertificateIf you change the SSL certificate of vCenter Server, you cannot access vSphere Replication. vSphere Replication Cannot Establish a Connection to the HostsReplications fail because vSphere Replication cannot connect to the hosts. Anti-Virus Agent in Firewall Stops Virtual Machine Replication If a virtual machine contains virus information, an anti-virus agent in the firewall might detect the virus data and stop the connection during replication. Initial Full Synchronization of Virtual Machine Files to VMware vSAN Storage Is SlowWhen using VMware vSAN storage and configuring vSphere Replication on multiple virtual machines, the initial full synchronization takes a long time to complete. Update the Child Replica Disks When Changing the Storage Policy for a vSAN Target DatastoreWhen you change a target storage policy and the target datastore is vSAN, the base disk storage policy is updated, but the child disk storage policy still refers to the previous storage policy. Configuring Replication Fails Because Another Virtual Machine Has the Same Instance UUIDYou cannot configure a replication because another virtual machine already exists at the target site. vSphere Replication Operations Run Slowly as the Number of Replications IncreasesAs you increase the number of virtual machines that you replicate, vSphere Replication operations can run more slowly. Unable to Establish an SSH Connection to the vSphere Replication ApplianceSSH connections to the vSphere Replication appliance are deactivated. The Replication Pauses When You Add a New Disk to the Source VMThe replication pauses when you add a new disk to the source virtual machine. The vSphere Replication Appliance Root File System Switches to Read-Only Mode and Login FailsThe vSphere Replication appliance root file system switches to read-only mode, and you cannot log in. Configuration of an Encrypted VM Fails with an ErrorWhen you try to configure a replication for an encrypted virtual machine, the process fails with an error. Reprotect Failures on Overloaded Datastores Reversing replications at large scale during the reprotect operation might fail due to issues caused by an overloaded datastore. Reconfigure replication process fails with an error after a long timeReconfiguring a replication with a target ESXi host that has a disallowed tag, fails with an error. Configuring a replication for a VM with physical mode RDM disk fails with an errorYou cannot configure a replication for a virtual machine with physical mode RDM disk even if the disk is excluded from replication . You cannot use custom defined users and roles with vSphere ReplicationYou cannot configure a replication with a custom user, even if the custom user is assigned all required VRM privileges on both sites. VMs that are located in the target folder are overwritten during recovery with vSphere ReplicationIf the target folder contains a registered virtual machine with the same name as the replicated virtual machine, the registered virtual machine is overwritten during the recovery. Generating a support bundle failsIf you try to generate a vSphere Replication support bundle, the process fails. You cannot configure new replications with network encryptionWhen you try to configure new replications with network encryption, the network encryption option is not active. Replications with network encryption appear in Not Active stateExisting replications that were configured with network encryption enter Not Active state. You cannot use network encryption for vSphere ReplicationWhen you try to configure network encryption for a replication, the option in the Configure replication wizard is inactive. vSphere Replication issues for VMware Live Site Recovery degraded and suspended modes remain after returning to operational modeYou entered VMware Live Site Recovery degraded or suspended mode, returned to operational mode and the vSphere Replication issues remain. Configure and reconfigure replication processes fail with an errorWhen you try to configure or reconfigure a replication with seed disks, a vSAN target datastore and a VM Encryption Policy storage policy, the process fails. You cannot encrypt an unencrypted source VM in an active replicationIf you try to encrypt an unencrypted virtual machine in an active replication configuration, the encryption fails. A recovered VM with activated MPIT loses the attached disks to the latest snapshotWhen you recover a VM for which you enabled MPIT instances and attach a disk for unresolved disks, if any, the disks attach to the latest snapshot. Failover or planned migration fails due to storage errorsAt 4000 scale on the target datastore, the test failover or planned migration might fail with an error. Recovering a VM with vSphere Replication 9.0 fails to power on the recovered VMThe issue is observed when a replicated VM is attached to a distributed virtual switch and you attempt to perform a recovery in an automated DRS cluster. Planned migration fails with an errorIf you trigger a replication sync, the replication might fail with an error due to connectivity issues. Moving seed replica disks from different datastores into one datastore failsWhen you try to move seed replica disks with identical names from different datastores into one datastore, the process fails. Replication reconfiguration attempts fail with a TaskInProgress faultIf a reconfiguration attempt is made, it internally invokes the vim.HbrManager API. An unexpected error appears in the Summary tab if you have a second NICIf you have a second NIC and you configured a static route set for it, the VRMS Appliance Management Interface cannot obtain an IP address from the second NIC. After reconfiguring a replication to assign a new storage policy, the policy is not appliedThe storage policy is applied to the replica disks at the target site when you first configure or recover a replication. A replicated VM becomes unresponsive or cannot serve network requestsDuring a vSphere Replication sync operation, the VM disk I/O blocks for the duration of the sync. The replication enters Error state when you remove and add disks to the source VMThe issue occurs when automatic inclusion of new disks is activated. Reprotect operation fails with an errorWhen you are replicating virtual machines at a large scale, reprotect might fail with an error. Automatic replication does not start when a disk is replaced on the same SCSI deviceThe issue occurs when automatic replication of new disks is activated. Newly added virtual disk is not replicated upon reprotect operationIf you perform a recovery and add a new disk to the recovered VM, the new disk is not replicated upon reprotect operation. VRMS might leak a partially recovered virtual machine in the target vCenter Server after a failed recoveryThe vSphere Replication management server might stop during recovery after registering the recovered virtual machine in the target vCenter Server. A recovered VM does not power on in vCenter ServerWhen you try to recover a VM, the process fails. Parent topic: Troubleshooting vSphere Replication
