During a test failover using ActiveDR, what content will be presented to the target pod?

ActiveDR's test failover feature is designed to be non-disruptive to ongoing replication. When a test is initiated, Purity creates a temporary, writable copy of the target pod, known as an "undo pod." This undo pod is what is presented to the test hosts. All I/O operations during the test are directed to the undo pod, which isolates the testing activity. The original target pod remains untouched and continues to receive replication data from the source array, ensuring the test does not impact the recovery point objective (RPO).

A. The content from the last periodic refresh: ActiveDR is near-synchronous, not based on periodic refreshes. The test uses a point-in-time copy from when the test was initiated.

B. The content from the last real fail-over: A test failover is independent of any prior real failovers and uses the current replicated data, not data from a past disaster recovery event.

1. Pure Storage. (2021). Purity ActiveDR Best Practices. p. 11, Section "Test Failover". [This document states, "When a test failover is performed... an 'undo pod' is created on the target array... This undo pod is what is connected to the host(s) for testing purposes."]

2. Pure Storage Support. (n.d.). ActiveDR: Test Failover. Pure Storage Knowledge Base. [This article details the procedure and explains the creation and role of the undo pod during a non-disruptive test failover.]