Snapshot Primary and Secondary Array

[mkaaden]

Hi,

A customer wants to snapshot a datastore on a hourly basis and use that as quickrecovers.
Regualar backups and copys to repositories will run every 24 hour.

This site is configured with VMware Metro Storage cluster with 2 Array's with synchronise replication.

When configuring a snapshot job, default the datastore LUN on the primairy array get's a snapshot.
To get a snapshot on the secondairy array one needs to configure a secondary destination in the job.
But the a popup that says:
"Instructs the job to create array snapshots on the HPE Alletra/Primera Peer Persistence target storage instead of the source one."

However, the custom would like to have a synchronized snapshot on both array's

We could define 2 jobs, one with and one without secondary destination, say 10 minutes apart, but then the snapshots are not each others exact mirror.

Is there a way to tell Veeam Backup to snapshot both array's at the same time ?
HPE Alletra MP now runs default in Active PP, thus a datastore is writeable on both primairy and secondairy.
So a pre-snapshot stun on LUN will be performed on both array's, no matter on which array the snapshot is made.

Running Veeam 12.2 with VMware 8

Regards,
Martijn

[CLDonohoe]

When you are configuring this in the Veeam UI, it sounds like Veeam Backup & Replication recognizes that the array is in a Peer Persistence configuration. When choosing the secondary target, you will see a few choices there:
- HPE Alletra/Primera Snapshot
- HPE Alletra/Primera Remote Copy
- HPE Alletra/Primera Peer Persistence

When you choose the "Peer Persistence" option, you're getting the pop up with more information to clarify the behavior of the software. VBR will indeed create the snapshot on the target array. If you want a snapshot schedule on the primary array as well, you would need to configure another snapshot orchestration job. This job will have an independent schedule, so the snapshots on each array will not be in sync.

So you may have three jobs potentially? Two snapshot orchestration jobs with independent schedules on each array and a backup from storage snapshot job with snapshot retention.