vSphere Replication behavior after recovery
search cancel

vSphere Replication behavior after recovery

book

Article ID: 428575

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

In an environment using vSphere Replication (VR) without Site Recovery Manager (SRM), a virtual machine is replicated from the Production site to the DR site.

After executing a RECOVER operation at the DR site for testing purposes, the replication task remains visible in the VR interface, but its status changes from OK to Recovered. Replication no longer continues automatically.

Environment

 

  • vSphere Replication

  • No Site Recovery Manager (SRM)

  • Separate Production and DR vCenter Server instances

 

Cause

This behavior is by design.

When a RECOVER operation is executed:

  • The replicated disks are used to register and power on a virtual machine at the DR site.

  • The replication status changes from OK to Recovered.

  • Ongoing synchronization stops.

  • The replication configuration is not automatically removed.

To resume protection, the existing replication must be manually removed and reconfigured.

vSphere Replication does not support non-disruptive test recovery. Non-disruptive testing is available only when using Site Recovery Manager (SRM).

Resolution

If a recovery test is performed and continued protection is required, the following steps must be completed:

  1. On the DR site vCenter, power off the recovered virtual machine and delete it from inventory (and disk if no longer required).

  2. In the vSphere Replication interface, record the configuration parameters of the existing replication task (RPO, target datastore, network settings, etc.).

  3. Remove the existing replication task. This step is required because the replication is in a Recovered state and will not resume automatically.

  4. From the Production site, configure a new replication task using the original parameters.

Additional Information

 

  • Before a RECOVER operation, no virtual machine object exists at the DR site — only replicated disk data is present.

  • After RECOVER, the DR virtual machine becomes independent.

  • Protection is not automatically resumed.

  • Manual removal and reconfiguration of replication is required to restore protection.

 

Powered by Wolken Software