3PAR Storage Snapshot failed

[mkaaden]

I have a VMware MSC with 2 3PAR's with Peer Persistence.
I'm running back-ups in both DC's to even the load.
Now last weekend 1 of the 3PAR's had to be powered off for maintenance in that DC

I expected that back-ups in the offending DC were about to fail.
What I did not expect was all back-ups failing, including the DC where all luns en vm's were running.
Now I noticed that the storage snapshots failed because it tried to snap the replica disk, which wasn't there because that 3PAR was powered off.

Why doesn't it fall back to snap the source volume if the replica volume is not available ?

[foggy]

Could you please tell a few words about your jobs configuration in regard to storage snapshots? First of all, are you backing up from the storage snapshots or running snapshot only jobs?

[mkaaden]

I am running backup jobs per datastore on each site of the MSC
Each site has its own physical proxy and a StoreOnce appliance.
Each job is setup with "enable backup from storage snapshot" checked.
So jobs failed on the surviving site failed, because the storage snapshots failed, because it tried to snap the replica disk which wasn't there.

[JasonL]

For the backups from the datastore at the DC where the 3PAR did not have to be powered off, do you have the box checked for a secondary destination?

[foggy]

Seems your job is indeed configured to backup from secondary storage while failover to primary storage snapshot is not currently supported for Peer Persistence.