An administrator setup replicated snapshots for a protection group last week. They left the local snapshot schedule disabled.
How many snapshots are stored locally on the source array?
Replication Fundamentals: On a Pure Storage FlashArray, replication is a snapshot-based process. To replicate a Protection Group (pgroup) to a target array, the system must first create a point-in-time snapshot of the volumes within that group on the source array.
The 'Immutable' Rule: Even if the Local Snapshot Schedule is disabled, the act of replicating requires the existence of a local snapshot to serve as the 'base' or 'source' for the data transfer. Purity does not stream data directly from the active volume to the wire; it creates a snapshot and then replicates the unique blocks contained in that snapshot.
Accounting for Local Copies: When a Protection Group is configured for replication, every snapshot generated by the Replication Schedule is stored locally on the source array. These snapshots will remain on the source array until they are aged out according to the Local Retention policy (even if the local schedule itself is off, the retention policy still applies to those replicated snapshots).
Visibility: If you navigate to the Protection Group in the Purity GUI, you will see these snapshots listed under the 'Snapshots' tab. They are functionally identical to local snapshots, meaning they can be used for local clones or restores without needing to pull data back from the target array.
Why Option A and C are incorrect: * Option A: If 0 snapshots were stored, there would be nothing to replicate.
Option C: While Purity uses the most recent snapshot as a reference for delta-tracking, it keeps the entire history of snapshots defined by your retention policy, not just a single one.
Leah
12 hours ago