Choosing backup source for VMs on Hyper-V: Cluster or Node?
Greetings, all! Our site has a new 2-node Hyper-V cluster that will replace our well-aged VMware ESXi 5.5 cluster. So, I'll be using Backup Exec (v.20.5) on Hyper-V for the first time as we build new servers on and move existing servers (?) to the new system. Having pushed the Agent for Windows successfully to the two nodes, I noticed that the cluster appeared in the list as well and can be backed up along with its VMs. The VMs can be backed up by choosing the nodes, too, which makes me ask which method is the better one. I don't recall seeing a mention of the two possibilities or a recommendation in the Administrator's Guide. What can those of you with experience in such a situation recommend as a backup strategy? Thank you for sharing your collective wisdom!
Backup Exec 15 - FP5 - 2012 R2 Hyper-V Cluster - GRT Backups Stuck in Snapshot Processing
Hello all. We have a 2012 R2 Hyper-V Cluster, all patched to date. This cluster has 6 nodes, each one connected via FC to a 3PAR 7400c All-Flash array. Each cluster node hosts about 20 VMs and 2 or 3 CSV (so each VM role has direct access to their storage via FC as it is its own Coordinator Node). With that in mind, we installed BEX 15 FP5 in each cluster node so that we could backup the VMs directly through FC and not via Ethernet (it's way faster and we do have a lot of data). Since implementation, eveything is going smooth (with some issues sometimes) with all cluster nodes except one. Every cluster node has either a FC Tape Library or a SAS Drive (all LTO6/LTO5, all firmwares up-to-date). This cluster node, VHT06, shows erratic behavior. It starts the granular job, but hangs in a random VM in "Snapshot Processing". We can't cancel the job unless we stop the "vmms.exe" service or reboot the cluster node. If we manage to cancel the job, the VM gets stuck in "Backing up..." within Hyper-V manager and can't reboot. We thought it could be the tape library, so we changed it. Still the same issue. We even evicted and reprovisioned the cluster node two times. Backup through RAWSworks fine. Marco