The Replication Log (RL) maintains a record of data being replicated to the object store.
Issue
The replication log can become invalid in the following scenarios:
- Failback After Planned Failover (PFO)
- Resuming Continuous Rehydration
After failover is complete and the DRVA on the failover site has taken ownership of the protected domain, the replication log of the protected site is no longer used and will become invalid.
This example illustrates an invalid replication log section:
Solution
Considerations
Scenario 1: Failback After Planned Failover (PFO)
- The original replication log can no longer be used because it contains no free space leaving it in an invalid state.
- The section used by PFO can be deleted to release disk space on the replication log which can then be reused.
Scenario 2: Resuming Continuous Rehydration
- The original replication log can continue to be used, or it can be deleted allowing the freed space to be repurposed.
Delete Replication Log Section
- Use the Delete Section option to remove an invalid section from the replication log.
