FreeNAS & Vmware exsi migration bypassing ESXi (VAAI not work?)

[as43031]

Good day!
I have two FreeNAS servers of the same hardware and software configuration (FreeNAS-11.3-U3.1)
There is a LUN on each FreeNAS, it is shared by isсsi in the ESHi 6.7 cluster.
I start the migration from one LUN to another LUN, and the migration traffic goes through the ESXi server, however, it is stated that FreeNas supports VAAI and migration traffic seems to go directly between storages, tell me why this may not happen?
The Enable TPK checkbox in the properties of both LUNs is worth it.
The fact that traffic goes through the ESHi server I see from the graphs of the network interfaces (I run into gigabits (network cards for the ESXi are gigabit)), and the network cards for the storages are 10 gigabits.
vCenter admin panel shows hardware acceleration is supported in the both storages.
Thanks for help.

 

[as43031]

If no one can help, maybe I got the wrong section?

 

[as43031]

I am saddened

 

[HoneyBadger]

From VMware's "Big List of Excuses" - https://kb.vmware.com/s/article/1021976

VAAI hardware offload cannot be used when:

• The source and destination VMFS volumes have different block sizes
• The source file type is RDM and the destination file type is non-RDM (regular file)
• The source VMDK type is eagerzeroedthick and the destination VMDK type is thin
• The source or destination VMDK is any kind of sparse or hosted format
• Cloning a virtual machine that has snapshots because this process involves consolidating the snapshots into the virtual disks of the target virtual machine.
• The logical address and/or transfer length in the requested operation is not aligned to the minimum alignment required by the storage device (all datastores created with the vSphere Client are aligned automatically)
• The VMFS datastore has multiple LUNs/extents spread across different arrays

Do any of these apply? Snapshots and changing VMDK type are the most common.

 

[kspare]

If you want to do storage vmotion and let the freenas boxes do the actual moves, do the disks have to be eager zero?

 

[HoneyBadger]

If you want to do storage vmotion and let the freenas boxes do the actual moves, do the disks have to be eager zero?

Thin XCOPY is supported but IIRC it's still slower as you can't move the data in large chunks like you can with thick.

 

[as43031]

From VMware's "Big List of Excuses" - https://kb.vmware.com/s/article/1021976

Применимо ли что-нибудь из этого? Снимки и изменение типа VMDK являются наиболее распространенными.

Thanks for responding!
It seems that the bottom of this list does not apply to me.
maybe i can turn on some kind of debug?

 

[as43031]

all disks vm - Thick Provision Lazy Zeroed, its wrong?
I do not change the disk type during the vmotion

 

[HoneyBadger]

Hold on:

I have two FreeNAS servers of the same hardware and software configuration (FreeNAS-11.3-U3.1)
There is a LUN on each FreeNAS, it is shared by isсsi in the ESHi 6.7 cluster.
I start the migration from one LUN to another LUN, and the migration traffic goes through the ESXi server, however, it is stated that FreeNas supports VAAI and migration traffic seems to go directly between storages, tell me why this may not happen?

Are you copying/migrating from one FreeNAS unit to another?

 

[as43031]

yes

 

[HoneyBadger]

yes

That will never work, the VMware VAAI XCOPY primitive (CLONE_WR) is only for copies within the same array. It is by design unable to copy SAN to SAN.

 

[as43031]

but I'm not doing cloning, but migration (

 

[as43031]

tell me, where is this limitation described?

 

[as43031]

any comment?

 

[HoneyBadger]

From the previous link posted, emphasis added in bold

VAAI uses these fundamental operations:

• Clone Blocks/Full Copy/XCOPY, which is used to copy or migrate data within the same physical array

If it's not the same physical array, VAAI is a no-go.

 

[as43031]

Thanks, but I asked for a link to the documentation where this limitation is described

 

[HoneyBadger]

Again:

VMware Knowledge Base

kb.vmware.com

Please look under the question titled

What are the fundamental operations used by VAAI and what are their corresponding Advanced Settings?

This describes the available VAAI operations (or "primitives") and under the XCOPY description it is described as

copy or migrate data within the same physical array

If you are not copying or migrating data within the same physical array (eg: two ZVOLs on the same FreeNAS) you cannot use VAAI XCOPY/CLONE_WR.

 

[as43031]

оk, sadness