Windows  Offloaded  Data  Transfer  ODX      Steve  Olsson  Principal  Program  Manager  Lead  Windows  Core  OS,  Storage  and  File  Systems  Microsoft  Corporation  

Local  Area  Network  

Storage  Network  

Server  1   Server  2  

Data  Center  1   Data  Center  2  

ODX Vision

2

Local  Area  Network  

Storage  Network  

Server  1   Server  2  

Data  Center  1   Data  Center  2  

Storage Technology behind ODX

3

SAS   SAS   SAS   SAS   SAS   SAS  

SAS   SAS   SAS   SAS   SAS  

SAS   SAS   SAS   SAS   SAS  

SAS   SAS   SAS   SAS   SAS  

SAS   SAS   SAS   SAS   SAS  

SAS  FC  

FCoE  iSCSI  

SAS  FC  FCoE  iSCSI  

§  Enable greater productivity with existing capital hardware

§  Providing a more agile datacenter, more capable of dealing with rapidly changing workloads

§  Windows has the capability “baked in” so no changes to the operational scripts or software is required

Business Goals

ODX Goals §  Technical Goals:

§  Achieve offloaded data transfer initiated from application level

§  Reduce the network and CPU workload from the server §  Utilize an advanced storage array’s bandwidth or

intelligent data management to move data between processes or servers

§  Industry Goals: §  Ensure all applications can leverage this capability with

VMs, physical machines and network connections §  Complete application compatibility with no code change §  Provide a standard framework across industry

Approach §  Look at the problem from an application

centric point of view §  Microsoft and its partners took a system

level approach to solve the problem §  Constructed a model for ODX

implementation §  Work with T10 Standard Committee to

adopt SCSI interface part of the solution §  T10 SPC4 (SCSI Primary Command) §  T10 SBC3 (SCSI Block Command)

6

Local  Area  Network  

Storage  Network  

Hyper-­‐V  Host  Server  1   Hyper-­‐V  Host  Server  2  

•  2xN  Virtual  Machines  hosted  by  two  Hyper-­‐V  servers    •  One  ODX  capable  storage  array  •  Connected  through  local  area  network  and  storage  network  

Storage  Array   Storage  Array  

ODX Hardware Concept

 VM1-­‐1  

 VM1-­‐2  

 VM1-­‐N    

VM2-­‐N  

 VM2-­‐1  

 VM2-­‐2  

Server1  or  

Hyper-­‐V  VM1  

Physical  Disk,  VHD  or  SMB  Shared  Disk  

Server2  or  

Hyper-­‐V  VM2  

Client-­‐Server  Network  

Data  Movement  

Offload  Read  

Return  Token  

Offload  Write  

Return  Result  

Physical  Disk,  VHD  or  SMB  Shared  Disk  

Copy  Offload  Application  

   Token  

Storage  Array   Storage  Array  

Storage  Network  

How  does  Windows  Offloaded  Data  Transfer  work?  

§  Token is a point-in-time representation of the data up and down the storage stack

§  The token facilitates logical block mapping

§  Application is not aware of the physical layout within the storage array

§  Token is opaque, secured and not guessable

The Token

10

Hyper-­‐V  Host  Server  

VM  

VM  

Note:  Corporate  Network  Speed  is  1  Gb/sec  

Hyper-­‐V  Host  Server  

Offloaded  Copy    takes  ~  2  min  

Traditional  Copy    needs    40+  min  

~  0%  Network  Utilization    ~  0%  CPU  Usage  

30  ~  99%  Network  Utilization  1  ~  5%  CPU  Usage  

Deploy  a  VM  with  30  GB  VHD  Image  Files    

Example  Scenario  

§  High  performance  data  transfer  rate    §  Low  server  CPU  usage  and  network  bandwidth  

consumption  §  Intelligent  data  movement  options  

§  Virtual  machine  deployment  §  Massive  data  transfer  between  physical  and  virtual  

systems    §  Host  controlled  data  movement  inside  tiered  storage  

devices  

Benefits  and  Implementation  

Thanks to our Partners