iSCSI Target Server stores each SCSI Logical Unit (LU) as a file in the Windows native file system – either NTFS or ReFS. The iSCSI stack uses the VHD (virtual hard disk) format for these files, which is why we call them ‘iSCSI Virtual Disks’. The VHD format provides good portability across target servers, and across the Hyper-V and iSCSI stacks. In Windows Server 2012, the iSCSI stack was
well
aware of the VHD file formats as it directly creates and manipulates the VHD files. Although this worked out well in some scenarios, this situation was not ideal for iSCSI stack as we really wanted to take immediate advantage of significant improvements in Hyper-V stack’s VHD capabilities – especially
the VHDX format
, which was newly introduced in Windows Server 2012.
Therefore, in Windows Server 2012 R2, the iSCSI stack switched to using the native Hyper-V VHD APIs. This update instantly gave the iSCSI stack the ability to support iSCSI Virtual Disks based on VHDX format and dynamic VHDX/VHD formats. In this release, the iSCSI stack also switched to VHDX as the default file format for Virtual Disks, so VHDX is the only format that you can use to create new iSCSI Virtual Disks. The iSCSI stack also takes advantage of the new online shrink/expand functionality in the Hyper-V stack, although you should note that the online shrink is new only for VHDX in Windows Server 2012 R2. Finally, we have made a number of corresponding improvements in the File and Storage Services UI in Server Manager to support these core functional changes.
The following tables summarize all of the Virtual Disk compatibility information for Windows Server 2012 and Windows Server 2012 R2. Although the tables may look daunting on a first glance, they are fairly easy to understand with this background information.
iSCSI Virtual Disks & Compatibility in Windows Server 2012
Create? |
Import? |
Expand? |
Shrink? |
|
Fixed VHD |
Yes |
Yes |
Yes |
No |
Fixed VHDX |
No |
No |
No |
No |
Diff VHD |
Yes |
Yes |
Yes |
No |
Diff VHDX |
No |
No |
No |
No |
Dynamic VHD |
No |
No |
No |
No |
Dynamic VHDX |
No |
No |
No |
No |
iSCSI Virtual Disks & Compatibility in Windows Server 2012 R2
Create? |
Import? |
Expand? |
Shrink? |
|
Fixed VHD |
No |
Yes |
Offline |
No |
Fixed VHDX |
Yes |
Yes |
Yes |
Yes |
Diff VHD |
No |
Yes |
Offline |
No |
Diff VHDX |
Yes |
Yes |
Yes |
Yes |
Dynamic VHD |
No |
Yes |
Offline |
No |
Dynamic VHDX |
Yes |
Yes |
Yes |
Yes |
This is a frequent question that I get – “Does iSCSI Target Server support thin provisioning?” Yes we do support thin provisioning, but not in the precise T10 sense because we do not support the UNMAP SCSI command . Dynamic VHDX-based iSCSI Virtual Disks now supported in Windows Server 2012 R2 are in reality thin-provisioned – which is why Dynamic is the default disk type iSCSI target cmdlets use to provision.
Wrap-upSo here is the short summary:
I hope this blog post serves as a useful reference for you. If you have feedback, drop me a comment on this blog post. Let me also know how the new VHDX-based iSCSI Virtual Disks are working for you so far on Windows Server 2012 R2!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.