Will using the option "Shut down Cluster" in 2008 R2 Failover Cluster Manager cause any disruption to Hyper-V VMs not in the cluster?

I previously had several VMs in a failover cluster in hyper-v utilizing a large Cluster Shared Volume.  I need to take that CSV offline/away from Hyper-V failover cluster manager so that it can be accessed from another machine via iSCSI target.  there are two nodes in this cluster but i'm not using the CSV or failover cluster to run any of the virtual machines right now.  Those VMs are currently on another LUN that is simply seen by the operating system as an iSCSI disk.  I don't want to cause any issues/outage within Hyper-V (again, 2 nodes right now that have the CSV I need to remove from the cluster) by shutting down the cluster service or removing the CSV from failover cluster manager.  

     So from within one of the two nodes in this cluster can I safely shutdown the failover cluster service or use the "take this resource offline" option without disrupting the Hyper-V service itself and the VMs that are currently running on one of those two nodes?  Again, currently the VMs that are running on one of those two nodes aren't actually using a CSV or setup as a cluster.  they are simply running in Hyper-V Manager and are stored on a non clustered iSCSI volume.  I simply don't want to disrupt them or Hyper-V by removing the previously used CSV from Failover Cluster Manager.

Can I do this safely?

Thanks.
linuxroxAsked:
Who is Participating?
 
Shabarinath RamadasanConnect With a Mentor Infrastructure ArchitectCommented:
If the VM is not dependent on the cluster resources, It shouldn't harm anything.

Verify the following before you start.

1) Location of VHD files
2) Location of Snapshot/Checkpoint files
3) Location of smart paging file (not sure if HyperV on 2008 has this.. Still)
4) Configuration File - Its an XML file with the GUID of the VM

And finally, Instead of Shutting down the cluster first - Try taking the CSV Disk offline. That will give you a quicker option if in case you need to make it on. And Shutting down the cluster is just turning off. You need to evict the nodes and destroy the cluster to fully move out of the cluster configuration. You may need to reboot the nodes while evicting the nodes or destroying the cluster - which needs more planning.

Good luck !

Shaba
0
 
linuxroxAuthor Commented:
hello Shabarinath!
     
     yes all of the VHD files running in hyper-v right now (not in the cluster service) are on a different LUN so removing that CSV from the cluster service "shouldn't" in theory affect anything I would think.  That was my hope actually.  All of the VMs currently running in Hyper-V were created independently from scratch using the source folder on the new LUN that is not in the cluster so i'm thinking that it should be ok!  Probably going to try this in 2 days.

thanks Shabarinath!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.