Offloaded Data Transfers (ODX) support with NetApp
Microsoft Offloaded Data Transfer (ODX), also known as copy offload, enables direct data transfers within or between compatible storage devices without transferring the data through the host computer.
While standard reads and writes work well in most scenarios, but what if the data intending to be copied is located on virtual disks managed by the 'same Storage Array' in the backend. This means that the data is moved out of the array, onto a server, across a network transport, onto another server, and back into the same array once again. The act of moving data within a server and across a network transport can significantly impact the availability of those systems; not to mention the fact that the throughput of the data movement is limited by the throughput and availability of the network.
Support for ODX starts with Windows 2012 Server and Windows 8. Applications can now take advantage of these capabilities to help offload the process of data movement to the storage subsystem. Two new FSCTLs (FSCTL_OFFLOAD_READ & FSCTL_OFFLOAD_WRITE) are introduced starting with Windows 2012 Server and Windows 8 that facilitate a method of offloading the data transfer.
This shifts the burden of bit movement away from servers to bit movement that occurs intelligently within the storage subsystems. The best way to visualize the command semantics is to think of them as analogous to an unbuffered read and an unbuffered write.
Requirements for using ODX with NetApp Storage Array:
Data ONTAP version requirements
Clustered Data ONTAP 8.2 and later releases support ODX for copy offloads.
Related article on 'How to trace ODX transfer':
http://www.slideshare.net/AshwinPawar/odx-42682251
IMPORTANT:
For CIFS environment, SMB 3.0 support is only available in clustered Data ONTAP 8.2. Data ONTAP 8.2 running 7-mode does not support SMB 3.0.
Please note Data ONTAP supports ODX for both the CIFS and SAN protocols. The source can be either a CIFS server or LUNs, and the destination can be either a CIFS server or LUNs.
Requirements for using ODX with Windows server and client requirements
Starting with Windows 2012 Server and Windows 8.
Use cases for ODX
https://library.netapp.com/ecmdocs/ECMP1196784/html/GUID-BAD66DF1-2AB5-4CB2-BF53-068E4B4D94A3.html
Courtesy:
http://msdn.microsoft.com/en-us/library/windows/hardware/dn265282(v=vs.85).aspx#feedback
Microsoft Offloaded Data Transfer (ODX), also known as copy offload, enables direct data transfers within or between compatible storage devices without transferring the data through the host computer.
While standard reads and writes work well in most scenarios, but what if the data intending to be copied is located on virtual disks managed by the 'same Storage Array' in the backend. This means that the data is moved out of the array, onto a server, across a network transport, onto another server, and back into the same array once again. The act of moving data within a server and across a network transport can significantly impact the availability of those systems; not to mention the fact that the throughput of the data movement is limited by the throughput and availability of the network.
Support for ODX starts with Windows 2012 Server and Windows 8. Applications can now take advantage of these capabilities to help offload the process of data movement to the storage subsystem. Two new FSCTLs (FSCTL_OFFLOAD_READ & FSCTL_OFFLOAD_WRITE) are introduced starting with Windows 2012 Server and Windows 8 that facilitate a method of offloading the data transfer.
This shifts the burden of bit movement away from servers to bit movement that occurs intelligently within the storage subsystems. The best way to visualize the command semantics is to think of them as analogous to an unbuffered read and an unbuffered write.
Requirements for using ODX with NetApp Storage Array:
Data ONTAP version requirements
Clustered Data ONTAP 8.2 and later releases support ODX for copy offloads.
Related article on 'How to trace ODX transfer':
http://www.slideshare.net/AshwinPawar/odx-42682251
IMPORTANT:
For CIFS environment, SMB 3.0 support is only available in clustered Data ONTAP 8.2. Data ONTAP 8.2 running 7-mode does not support SMB 3.0.
Please note Data ONTAP supports ODX for both the CIFS and SAN protocols. The source can be either a CIFS server or LUNs, and the destination can be either a CIFS server or LUNs.
Requirements for using ODX with Windows server and client requirements
Starting with Windows 2012 Server and Windows 8.
Use cases for ODX
https://library.netapp.com/ecmdocs/ECMP1196784/html/GUID-BAD66DF1-2AB5-4CB2-BF53-068E4B4D94A3.html
Courtesy:
http://msdn.microsoft.com/en-us/library/windows/hardware/dn265282(v=vs.85).aspx#feedback
No comments:
Post a Comment