| Previous | Next |
| ERROR_VHD_SHARED | ERROR_VHDSET_BACKING_STORAGE_NOT_FOUND |
ERROR_SVHDX_NO_INITIATOR
One feature introduced in Windows Server 2012 R2 that is receiving a lot of attention is the shared virtual hard disk (VHDX). Shared VHDX allows a guest cluster to share a virtual hard disk. This makes deployment of cluster configuration simpler and allows for the use of storage from SMB shares as opposed to Fibre Channel or iSCSI.
Why is this cool? Because it makes administration of the virtual environment easier. Most organizations want to authorize users to create their own virtual machines, particularly when developing and testing new applications. Often a guest cluster is desirable, but many admins do not want to give users access to storage networks to create cluster shared volumes. Now, with shared VHDX, all a user need do is create a virtual disk and share it between guests when configuring a virtual machine failover cluster.
Instructions on how to deploy a guest cluster using a shared virtual hard disk can be found here.
You can see a demonstration using shared VHDX at six minute mark if this video.
As mentioned many times on this site, Unitrends provides an easy to use, unified backup solution for virtual and physical systems.
System Requirements and Limitations of Shared VHDX Technology
The Shared VHDX feature will work on Hyper-V version of Windows Server 2012 R2. The same goes for a file cluster node when sharing shared VHDX disks on a Scale-Out File Server.
As a guest OS, you can use Windows Server 2012 R2 or Windows Server 2012 with the latest available version of the Hyper-V integration components. The shared disk must be in VHDX format (VHD format is not supported in this configuration). At the same time, the guest OS itself can be adopted on both VHD and VHDX disks.
Both the first (Generation 1) and the second generation (Generation 2) virtual machines are supported.