How many CSVs per cluster (4 node and 8 node). A CSV per node of cluster, or a single CSV for the entire cluster (Hyper-V)
This is a specific question regarding setting up a 4 and a separate 8 node Hyper-V cluster. Specifically, both of these clusters were setup with a single CSV. In speaking to a vendor who is helping us setup a new backup appliance, trying to troubleshoot why when the backups of the VMs were running, we had missed polls on VMs in the cluster, as well as sometimes having a node of the cluster crash. This has happened on both of these clusters (again, with a single CSV; which according to the backup people is incorrect, they were very specific when they said we need to have "A CSV PER NODE of the cluster)."
So when setting up a 4 or 8 node Hyper-V cluster, does each node of the cluster require a CSV ("a CSV PER NODE"), or should there be a single CSV shared by the nodes of the clusters?
I could not find specific information on MS's technet that says exactly that, but a couple of diagrams they showed me from MS (the backup people), it looked like each node of a cluster should have their own CSV, as well as their own documentation which stated very specifically that each node must have it's own CSV to accommodate backing up the VMs through the cluster (rather than the workaround we are using now, backing each VM up as if it were a Physical Machine).
Any advice on architect the cluster correctly would be greatly appreciated.
The 8 node is Windows 2012 R2, and the 4 node is Windows 2008R2.
So when setting up a 4 or 8 node Hyper-V cluster, does each node of the cluster require a CSV ("a CSV PER NODE"), or should there be a single CSV shared by the nodes of the clusters?
I could not find specific information on MS's technet that says exactly that, but a couple of diagrams they showed me from MS (the backup people), it looked like each node of a cluster should have their own CSV, as well as their own documentation which stated very specifically that each node must have it's own CSV to accommodate backing up the VMs through the cluster (rather than the workaround we are using now, backing each VM up as if it were a Physical Machine).
Any advice on architect the cluster correctly would be greatly appreciated.
The 8 node is Windows 2012 R2, and the 4 node is Windows 2008R2.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have spent some time reading over the articles, thank you very much. My question was a fairly strightforward one, and you gave me much more, thanks again. What it really set us straight on was how to calculate the number of CSVs, etc. The main problem is trying to rearchitect, on the same hardware, a cluster like that. We may have to use a workaround backup for the time being, until we reach a time at which the hardware will be replaced (sooner for one than the other), and pay closer attention to the role of CSVs when architecting the cluster. Thank you again.
ASKER
Answered the main question, and went further in providing the articles that will help not only answer the question, but allow us to properly tune that answer to our specific situation, equipment, and needs.
ASKER