18.08.2013 Views

vSphere Storage - ESXi 5.1 - Documentation - VMware

vSphere Storage - ESXi 5.1 - Documentation - VMware

vSphere Storage - ESXi 5.1 - Documentation - VMware

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>vSphere</strong> <strong>Storage</strong><br />

Verify Hardware Acceleration Status for NAS<br />

In addition to the client, you can use the esxcli command to verify the hardware acceleration status of the<br />

NAS device.<br />

In the procedure, --server=server_name specifies the target server. The specified target server prompts you<br />

for a user name and password. Other connection options, such as a configuration file or session file, are<br />

supported. For a list of connection options, see Getting Started with <strong>vSphere</strong> Command-Line Interfaces.<br />

Prerequisites<br />

Install vCLI or deploy the <strong>vSphere</strong> Management Assistant (vMA) virtual machine. See Getting Started with<br />

<strong>vSphere</strong> Command-Line Interfaces. For troubleshooting , run esxcli commands in the <strong>ESXi</strong> Shell.<br />

Procedure<br />

u Run the esxcli --server=server_name storage nfs list command.<br />

The Hardware Acceleration column in the output shows the status.<br />

Hardware Acceleration Considerations<br />

When you use the hardware acceleration functionality, certain considerations apply.<br />

Several reasons might cause a hardware-accelerated operation to fail.<br />

For any primitive that the array does not implement, the array returns an error. The error triggers the <strong>ESXi</strong><br />

host to attempt the operation using its native methods.<br />

The VMFS data mover does not leverage hardware offloads and instead uses software data movement when<br />

one of the following occurs:<br />

n The source and destination VMFS datastores have different block sizes.<br />

n The source file type is RDM and the destination file type is non-RDM (regular file).<br />

n The source VMDK type is eagerzeroedthick and the destination VMDK type is thin.<br />

n The source or destination VMDK is in sparse or hosted format.<br />

n The source virtual machine has a snapshot.<br />

n The logical address and transfer length in the requested operation are not aligned to the minimum<br />

alignment required by the storage device. All datastores created with the <strong>vSphere</strong> Client or the<br />

<strong>vSphere</strong> Web Client are aligned automatically.<br />

n The VMFS has multiple LUNs or extents, and they are on different arrays.<br />

Hardware cloning between arrays, even within the same VMFS datastore, does not work.<br />

224 <strong>VMware</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!