nfs vmware datastores and fabricpool | NetApp | Page 1

cold scarab Apr 12, 2024, 10:59 AM

#

Hi all, we have a few cases where we need to extend or add more vmdk's for an vm appliance; and the appliance does not support adding any external storage like nfs, cifs, s3 or iscsi. Only option is to add or extend vmks. Now this will likely be 99% cold data.
And this can be up to a few 100 TBs in sizes.

What is the general opinion about creating a dedicated tiered datastores for cold data vmdks?
The OS disks would not be tiered only the attached vmdks.

Our storagegrid is on-prem close to the AFF and are in the same "pod" so to speak.

radiant kite Apr 12, 2024, 11:18 AM

#

technically its supported to tier vmware workloads with fabricpool. if you are sure that most of this data is cold, i would go for it. There are some points that you have to check/aware of (e.g. Backup, Metadata, Performance) and i would recommend to use separate datastores for the tiered VMDKs (to tier hat volumes only). Starting with ONTAP 9.14.1 there is also an "onPrem Mode" for FabricPool available which improves read and write Performance to a local Tier like SGW. This as info for later, thats no recommendation to upgrade prod systems to 9.14.1 right now 😉

cold scarab Apr 12, 2024, 12:46 PM

#

Thanks for the input frechna, appreciate it

modern nova Apr 25, 2024, 6:30 PM

#

I need to understand how deletion works with fabricpool as the unreferenced capacity of the fabricpool keeps on increasing

lyric slate Apr 25, 2024, 8:03 PM

#

does this help?

#

FabricPool does not delete blocks from attached object stores. Instead, FabricPool deletes entire objects
after a certain percentage of the blocks in the object are no longer referenced by ONTAP.

#

page 21

#nfs vmware datastores and fabricpool