If you encounter problems with creating protection groups and recovery plans, failover, recovery, or guest customization, you can troubleshoot the problem.
Site Recovery Manager Doubles the Number of Backslashes in the Command Line When Running Callouts Site Recovery Manager doubles all backslashes.Powering on Many Virtual Machines Simultaneously on the Recovery Site Can Lead to Errors LVM.enableResignature=1 Remains Set After a Site Recovery Manager Test Failover Site Recovery Manager does not support ESXi environments in which the LVM.enableResignature flag is set to 0.Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error Configuring Protection fails with Placeholder Creation Error Planned Migration Fails Because Host is in an Incorrect State ESXi host on the recovery site into maintenance mode during a planned migration, the planned migration fails. Recovery Fails with a Timeout Error During Network Customization for Some Virtual Machines Recovery Fails with Unavailable Host and Datastore Error vCenter Server inventory. Reprotect Fails with a vSphere Replication Timeout Error vSphere Replication protection groups, the operation times out with an error. Recovery Plan Times Out While Waiting for VMware Tools Reprotect Fails After Restarting vCenter Server vCenter Server , when you use vSphere Replication , reprotect operations sometimes fail. Rescanning Datastores Fails Because Storage Devices are Not Ready Site Recovery Manager before a promoted storage device on the recovery site is available to the ESXi hosts. Site Recovery Manager rescans the storage devices and the rescan fails. Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0 Application Quiescing Changes to File System Quiescing During vMotion to an Older Host vSphere Replication can create an application quiesced replica for virtual machines with Windows Server 2008 and Windows 8 guest operating systems running on an ESXi 5.1 or newer host. Reconfigure Replication on Virtual Machines with No Datastore Mapping vSphere Replication on multiple virtual machines, the replication configuration fails.Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores vSphere Replication on a virtual machine that includes two disks that are contained in different datastores, the configuration fails.vSphere Replication RPO Violations vSphere Replication is running successfully at the recovery site. vSphere Replication Does Not Start After Moving the Host ESXi Server on which the vSphere Replication appliance runs to the inventory of another vCenter Server instance, vSphere Replication operations are not available. vSphere Replication operations are also unavailable if you reinstall vCenter Server . Unexpected vSphere Replication Failure Results in a Generic Error vSphere Replication includes a generic error message in the logs when certain unexpected failures occur. Generating Support Bundles Disrupts vSphere Replication Recovery vSphere Replication log bundle and at the same time attempt to run a recovery, the recovery might fail. Initial Full Synchronization of Virtual Machine Files to VMware Virtual SAN Storage Is Slow vSphere Replication on multiple virtual machines, the initial full synchronization takes a long time to complete. vSphere Replication Operations Run Slowly as the Number of Replications Increases vSphere Replication operations can run more slowly.
