Best Practice to build Physical Veeam backup proxy ?

[albertwt]

Hi All,

I've got my main Veeam Backup server (as VM) in my head office server room.

In my two remote Data Center (PROD & DR) I have ESXi servers running and all of the VMs on top of iSCSI SAN (Lefthand and 3PAR) while the Veeam Backup Repository is on QNAP NAS presented as iSCSI LUN.

So what's the best practice to utilize Storage Array Snapshot since I'm about to deploy physical box into each Data Center to make sure VM backup going to this physical box iSCSI LUNs on the QNAP on each site ?

[foggy]

Please follow these prerequisites for the backup from storage snapshots. Thanks.

[albertwt]

Hi Alex,

I assume the VM backup when using Storage array snapshot will be much quicker and doesn't have the problem/risk with open VMware snapshot ?

[foggy]

Correct, backup from storage snapshots allows to eliminate VMware snapshot commit issues, since the time VM runs on the snapshot is significantly shorter.

[albertwt]

Great, in that case, I can now be sure to backup all of my big Tier-1 VMs like Exchange Server, SQL Server, File Server, SharePoint Server which is larger than 2.6 TB up to 12 TB.

I guess Storage Array snapshot is the best way to move forward to backup those VMs even during the business hours

[dellock6]

At least for VMFS based datastore, yes. Otherwise you may look at different solutions that have different snapshot technologies, VVOLS and VSAN specifically. Those two do not use redolog snapshots, so commit times are really really shorter (many minutes vs a few seconds).

[albertwt]

Thanks, Luca for the explanation,
Since I do not have VVOL and vSAN license, I can only continue with Storage Array Snapshot.