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?
If exchange was running as a VM would you even need a second node given the redundancy built into the hyper-visor. Added to that you have a replicated backup of the server, I fail to see why you do not
HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct. It's a good idea to compare checksums, because many installat…
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version
Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
This video shows you how to use a vSphere client to connect to your ESX host as the root user.
Demonstrates the basic connection of bypassing certification set up.
Demonstrates how to access the traditional view to begin managing your virtual mac…