garyttu
asked on
Veeam Exchange Backup DAG
We're converting a 2 node physical Exchange 2010 DAG into a new config where at least one of the nodes is a VM (ESXi) so it can be backed up with Veeam.
Is there any reason to make both of the nodes VMs (from a backup perspective)?
I am assuming the best plan is to make the VM node the passive copy and just back up that in Veeam, thus capturing all necessary backup data to restore Exchange data.
The active copy would not be backed up.
Keeping the active node physical saves on the licensing and small VM overhead and deduplication store space (of not backing it up). I also understand backing up both can lead to occasional failovers due to snapshot processing. However, are there any advantages to making both virtual and backing up both with Veeam worth noting?
Is there any reason to make both of the nodes VMs (from a backup perspective)?
I am assuming the best plan is to make the VM node the passive copy and just back up that in Veeam, thus capturing all necessary backup data to restore Exchange data.
The active copy would not be backed up.
Keeping the active node physical saves on the licensing and small VM overhead and deduplication store space (of not backing it up). I also understand backing up both can lead to occasional failovers due to snapshot processing. However, are there any advantages to making both virtual and backing up both with Veeam worth noting?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.