Some Highly Available Virtual Machines in a Windows 2008 R2 Hyper-V cluster are not visible under the Microsoft Hyper-V HA Virtual Machine backup selections
|Article:TECH145913|||||Created: 2010-12-09|||||Updated: 2013-05-29|||||Article URL http://www.symantec.com/docs/TECH145913|
When selecting Hyper-V clustered virtual machines under the Hyper-V cluster node name some Virtual Machines may be missing from the backup selection list (Microsoft Hyper-V HS Virtual Machines) (FIGURE 1).
In this Example the Hyper-V cluster consist of two physical Hyper-V cluster Nodes (NODE1 and NODE2). The Hyper-V virtual cluster resource name is BE-VS.LAB. There are 6 Virtual machines in the Hyper-V cluster. Currently 3 Virtual machines (AC, DC, EXCH10) are owned by NODE1 and the Hyper-V cluster resource (BE-VS.LAB) is owned by NODE1 of the Hyper-V Cluster.
(FIGURE 1) NOTE: Only 3 out of 6 Clustered Virtual Machines are showing up for selection in Backup Exec.
In the Example above the 3 virtual machines missing are owned by NODE1 of the Hyper-V cluster. The 3 Virtual machines available for selection are owned by NODE1 and this is the same node the Hyper-V Cluster resource is currently owned by. Live Migrating a missing Virtual Machine to the Hyper-V node where the Virtual Machine are showing up in the Backup Exec selection list will allow the Virtual machine to appear in the selection list although not desired for Load balancing and fault tolerance of the Hyper-V cluster and Virtual machine.
Backup Exec 2010 and 2010 R2
WIndows 2008 R2 Hyper-V
Clustered or Highly Available Virtual Machines on CSV (Clustered Shared Volumes)
Two, Three, Four Node Hyper-V Clusters
Solution 1 :
Add the Backup Exec Service Account (BESA) to the Hyper-V Cluster and Cluster Nodes.
Open Hyper V Cluster Manager. Go to properties of Cluster Name (FIGURE 2) :
Add the Backup Exec Service Account (BESA) account with full rights in the Cluster manager for the Hyper-V Cluster Resource/Name (FIGURE 3).
NOTE: Additionally add the BESA account to the Local Administrator group on all nodes of the Hyper-V cluster.
Restart the Backup Exec remote agent service on all Hyper-V cluster nodes.
Solution 2 :
Another cause is if there is an issue with the WMI namespace in the Hyper-V hosts. In this case , a reboot the Hyper V host(s) may be necessary. Virual Machines will need to be moved to other cluster nodes to reboot each Hyper-V cluster node one at a time.
[ Note : This is taken in consideration that Hyper V Cluster and its configurations are configured properly. ]
AHV Hyper-V HA Guests that don't reside on active Hyper-V cluster node do not show up in the Hyper-V HA Selections in a 3 Node Windows 2008 R2 HA cluster
Article URL http://www.symantec.com/docs/TECH145913