short follow-up on peer persistence. One of the "features" of peer persistence is protecting volumes in case of a failure by using a failsafe condition. Volumes in a peer persistence configuration are protected based on remote copy groups, where you have a primary volume on the source storage and a backup volume on the target storage where the primary volume is being replicated to the backup volume over FC or IP. When communication between the source storage with "a tie-breaker" and the target storage system is broken, the remote copy group will end in a failsafe condition, where IO to the primary volume is stopped, and wil continue on the backup volume. Replication will be stopped in this scenario.
I must admit, you should monitor your storage and recover from such a big failure condition adequate. However we would like to know how Veeam reacts on such a big failure condition in the remote copy group. Quite scary tot think of, if it turns out that Veeam is using the primary volume for performing a backup, resulting in data loss while changed data is handled by the backup volume.
So in short : Is Veeam aware of a failsafe condition, and how will this impact the backups that use storage integration with the 3PAR ?