VMware Cloud Community
INSPSC
Contributor
Contributor
Jump to solution

VAAI & ATS Datastores

Hi

just a quick Question. If i have created and formatted a VMFS5 Datastore before the SAN Array was VAAI capable will the Datastore after a Firmware Upgrade, now with VAAI support, use ATS?

If i create a Datastore on a VAAI enable SAN Array the Datasore is ATS-Only... so something to do here?

Greetz,

Peter

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

Yes if you upgraded the firmware and VAAI is supported it should be automatically enabled after a storage 'refresh' operation, you can check using the instructions in the following link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102197...  ATS-Only means it won't use SCSI-2 reservations, this isn't an error and is expected on new VMFS-5 volumes. (see the link for more info).  You can disable the individual VAAI fundamental operations using the advanced settings if you need to.

View solution in original post

0 Kudos
4 Replies
admin
Immortal
Immortal
Jump to solution

Yes if you upgraded the firmware and VAAI is supported it should be automatically enabled after a storage 'refresh' operation, you can check using the instructions in the following link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102197...  ATS-Only means it won't use SCSI-2 reservations, this isn't an error and is expected on new VMFS-5 volumes. (see the link for more info).  You can disable the individual VAAI fundamental operations using the advanced settings if you need to.

0 Kudos
INSPSC
Contributor
Contributor
Jump to solution

Hi

thanks for the Quick Answer.

So the Datastore shows:

naa.600508b400105c1e0001100000380000
   VAAI Plugin Name:
   ATS Status: supported
   Clone Status: supported
   Zero Status: supported
   Delete Status: unsupported

so everything ok or?

Greetz,

Peter


0 Kudos
admin
Immortal
Immortal
Jump to solution

Yep looks like you're good to go!  Please award correct/helpful points if you found my answer useful. 🙂

admin
Immortal
Immortal
Jump to solution

For delete status: unsupported means that you're not using a thin-provisioned LUN or your array does no support the UNMAP opperation (T10 compatibility required). It's not a problem though, just means you can't tell your array to reclaim blocks on a thin-provisioned LUN when you delete VMs.  Check this KB for more info and to see i your array is T10 compliant: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200742...