Manual Cleanup of Replication Log Section After Failover

This article applies to all JSDR software versions.

Issue

The Replication Log section becomes invalid after the execution of a Forced Failover or Planned Failover. In the event of a disaster at the primary site, the replication log section is not automatically cleaned up and must be manually deleted.

Procedure

If the DRVA is still operational following a forced failover/planned failover, manually delete the replication log section:

1. Click the Appliances tab and navigate to Replication Log Volume details.

2. Click the Delete Section option to manually remove the section from the replication log.

3. In some situations, an error may occur during the deletion process preventing the section from being deleted. In such case, reboot the DRVA and then attempt to delete the replication log section again.

Planned failover (PFO) is a planned event and the DRVA will continue to remain operational throughout the entire process. The corresponding replication log section will not be deleted automatically. This is done to support the “Resume Continuous Rehydration” function where retention of the replication log section is necessary.

If planned failover if performed and then it is desired to failback without “Resume Continuous Rehydration” (RCR), the replication log section must first be deleted.

However, if the “Destroy protected domain’s VMs and section on the remote site” option is explicitly selected during execution of a planned failover, it will not be necessary to manually the section.