See also Hyper-V Backup.

http://blogs.technet.com/b/storageserver/archive/2012/09/14/windows-storage-server-2012-is-available-to-microsoft-s-hardware-partners.aspx

http://blogs.technet.com/b/storageserver/archive/2011/02/25/microsoft-oem-engineering-services-help-storage-partners-bring-embedded-solutions-to-market-and-support-them-throughout-the-product-lifecycle.aspx

http://download.microsoft.com/download/A/B/E/ABE02B78-BEC7-42B0-8504-C880A1144EE1/WS%202012%20White%20Paper_Storage.pdf

http://technet.microsoft.com/en-us/library/jj643303.aspx

http://technet.microsoft.com/en-us/library/jj643306.aspx

The precise method of deploying any given shared storage scheme will vary depending on the hardware and software you are using.

The basic process is to:

1. Implement the shared storage first
2. Connect the Hyper-V hosts to it
3. Add the hosts into a Failover Cluster.

http://technet.microsoft.com/en-us/library/gg610692.aspx

http://blogs.msdn.com/b/clustering/archive/2012/04/06/10291490.aspx

http://technet.microsoft.com/pt-br/library/cc732181%28v=ws.10%29.aspx

• This feature enables multiple nodes to concurrently access a single shared volume
• CSV is supported on WS2008R2 and newer
• Failover Cluster Manager
  • CluAdmin.msc
• CSVs are created from Physical Disk Resources (PDR)
• Must pass all tests in the Validate a Configuration Wizard
  • Included in the Failover Cluster Manager MMC snap-in
• Use matching computers that contain either the same or similar features
• You cannot use teamed network adapters with iSCSI

• For a two-node failover cluster, the storage should contain at least two separate volumes (LUNs) configured at the hardware level
  • Do not expose the clustered volumes to servers that are not in the cluster
  • One volume will function as the witness disk
  • One volume will contain the files that are being shared between the cluster nodes
    • This volume serves as the shared storage on which you will create the virtual machine and the virtual hard disk