A customer has a pair of HPE Alletra MP B10000 storage arrays with Peer Persistence configured between them. The customer will be adding Veeam to the solution for data protection. Which statement is correct regarding Peer Persistence orchestration and the snapshots taken by Veeam?
HPE Peer Persistence is a high-availability solution that provides synchronous replication with transparent failover between two storage arrays. When integrating Veeam Backup & Replication with an HPE Alletra MP B10000 (Block) environment using Peer Persistence, the software must account for the synchronous nature of the volumes.
To maintain the integrity of the synchronous replication state and ensure that a crash-consistent or application-consistent recovery point exists at both locations, Veeam utilizes the HPE Storage Snapshot Provider. When a backup job or a snapshot-only job is triggered for a volume in a Peer Persistence relationship, the orchestration logic ensures that the snapshot is created on both the primary and the secondary array. This 'dual-snapshot' approach is critical; if a site failover occurs shortly after the snapshot is taken, the backup software can still perform a recovery from the secondary array because the corresponding snapshot exists there.
Furthermore, this integration allows for Backup from Storage Snapshots (BfSS), which reduces the impact on the production virtual environment by offloading the I/O processing to the storage layer. While Option A suggests the primary array is always the source, Veeam can actually be configured to back up from the secondary array to save primary site bandwidth (though the snapshot itself must exist on both). Option B is incorrect as snapshot retention is defined by the Veeam backup policy, not a hardcoded 30-minute limit. Option D is incorrect because the synchronous link handles the data flow naturally; the snapshot is a pointer-based operation within each array's metadata layer once the synchronous write is acknowledged.
Currently there are no comments in this discussion, be the first to comment!