{"id":11491,"date":"2011-08-14T21:08:30","date_gmt":"2011-08-14T21:08:30","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=11491"},"modified":"2011-08-14T21:08:30","modified_gmt":"2011-08-14T21:08:30","slug":"whitepaper-csv-and-backup","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=11491","title":{"rendered":"Whitepaper – Planning Hyper-V CSV and Backup"},"content":{"rendered":"

I have just published<\/a> a guide or document to discus the subject(s) of Hyper-V Cluster Shared Volume (CSV) and backup.<\/p>\n

Windows Server 2008 R2 introduced many new features for those of us who use Hyper-V. One of the big ones was something called Cluster Shared Volume (CSV). This allowed us to do something that VMware users take for granted and that we could not do before this release of Windows Server: store many virtual machines, which are running on many hosts in a cluster, on a single storage volume. The benefit of CSV is that it simplifies administration, reduces the possibility of human engineering error, and even makes the private cloud a possibility.<\/em><\/p>\n

A structure depends on the foundation that it is built upon. The same is true of a virtualisation infrastructure. The foundation of Hyper-V (or XenServer or vSphere) is the storage design and implementation. What appears to be not very well understood is that backup design is intrinsically linked to your storage architecture. One must be considered hand-in-hand with the other in the Hyper-V world. Get that wrong and you\u2019ll have unhappy users, an unhappy boss, and maybe even an unhappy bank manager when you are no longer employed. When you get to grips with the basics you\u2019ll be empowered to implement that ideal virtualisation platform with optimised backup.<\/em><\/p>\n

This document will cover:<\/em><\/p>\n