ODX – Why to wait ? Make use of it…

I heard about ODX in Windows Server 2012 Boot Camp which happened in Sep 2012 @ Dubai. Though I was impressed and a bit excited on these new technology, I realized that our existing storage don’t support ODX. And in late 2013, I got a chance to work with a storage which supports ODX. I searched a bit in Google to see how we can implement ODX.

All the documents says ODX is enabled by default. What next ? I need to enable and feel it. And at last I did it. 😀

Lets me brief those steps. My experiments was using Windows Server 2012 R2 Hyper-V and Windows Server 2012 R2 with SCVMM 2012 R2 both having SAN Disks from ODX capable SAN. I am planning few more tests which I will update on the following posts.

1) Verify that storage supports ODX

The best place to check this is Windows Server Catalog .

Navigate to Hardware Testing Status and search for the specific storage mode which needs to be checked.

Confirm that ODX is supported. Windows Server Catalog is a site hosted by Microsoft. If Microsoft has tested and certified, it should work well.

If your storage is not listed here, the next step is to contact the Storage vendor directly to confirm on ODX. I forsee a chance where a specific device may be supporting ODX, how ever if Microsoft has not yet tested – it will not be listed in the server catalog.

ODX - Compatibility


2) Storage Firmware is the second item to be checked. In my case, this particular storage will support ODX only if the Storage Firmware is above a certain level. Double check with the storage vendor. Its also recommended to make the server firmware and drivers updated.

3) On the Hyper-V Server and SCVMM Server, Verify the status of ODX

fltmc instances

Now, we need to check the supported features for the filter.

Registry Value - SupportFeatures

SupportedFeatures 3 means ODX is supported.

This is by default enabled. However, Just to confirm that no one has disabled it by mistake – check this too.

Get-ItemProperty hklm:\system\currentcontrolset\control\filesystem -Name “FilterSupportedFeaturesMode”

ODX Enabled

FilterSupportedFeaturesMode 0 Means ODX is enabled.

4) What next ? Nothing other than testing ODX. 😀

The first test is by copying a 33 GB folder from a CSV Volume to another ODX enabled SAN volume on a remote server.

As ODX is enabled, we should not see the traffic passing over network. To montor the network traffic, I am using the simple performance monitor inside Task Manager.

odx test 2


As I am connected over RDP, a slight traffic is expected on the management interface. However, the current data transfer speed on on the Copying job is 266 MB/s. And the traffic (Send) currently over the management network interface is 312 Kbps. The graph for the network interface traffic will give you an idea on the data transfer in the last 60 seconds. The maximum on the graph is 11 MB/s.

The next test is to know the behavior while copying the same file from the ODX enabled CSV Volume to a non ODX enabled remote share. We should see the traffic over network here.

ODX Test - Copying to ODX Disabled remote share

The data transfer on management interface is now 943 Mbps which is approximately 117 MBps. The speed on the copying job is 113 MBps which is almost matching. Thus we conclude that the data-transfer is happening over network.

To double check if the traffic we are seeing on the network is from the copying job, I just paused the copying job. See the difference on the traffic.

odx test - Pausing copy

Just after the copying job is paused, see the network traffic dipping to almost null.

And finally, I resumed the copying job which made the traffic to shoot up and hit the maximum.

odx test 6

# Reference – http://technet.microsoft.com/en-us/library/jj200627.aspx