Hi all,
This is my first post so please go easy on me. 🙂
We currently in the process of migrating physical servers to Hyper-V cluster running on NetApp 7 mode filers. We will be utilizing 10G connections over iSCSI but unfortunately we don't we don't have a switch to connect between the virtual hosts and the controllers.
We have two virtual host nodes in the cluster, and a FAS2240 7 mode dual controller unit. Because the lack of storage we are running acitve-passive HA mode. LUNs and vFilers are all running on the active controller. Each virtual host has two links, one goes to the active controller and the other goes into the passive controller to ensure that all nodes have access to the LUNs in case of failover.
This works fine if I use the Windows built-in iSCSI initiator, I don't have to specify the initiating IP address. So when controller failover occurs all running VMs are not affected, because Windows would use the second IP/link to connect to the passive controller.
Issue surfaces when I implemented SnapManager and SnapDrive. In SnapDrive it seems that I have to specify initiating IP address, but this IP address won't have access to the passive controller when failover occurs.
My question is is there anyway around this? If I don't use SnapManager what other backup/restore solutions I would have for VMs?