Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

General Discussion

VMware DRS and NetApp snaps

storageguy

Good Morning,

 

Looking for some inputs. When DRS (Auto) is enabled on datastore cluster , vmdks moved between datastores I guess. Hence I assume for NetApp it is data change and snaps will be bigger. I ask this question because we noticed and aggregate utilization went above 98% and soon as DRS disabled and snaps delete, it started to come down. I couldn't see aggr utilization going down while DRS was enabled and snaps got deleted.  So enabling DRS good or bad?

 

Thanks in advance

1 ACCEPTED SOLUTION

jeras

Our recommendation is to use the default storage DRS setting of "manual".  This is discussed towards the bottom of this section of TR-4597, the VMware vSphere for ONTAP Best Practices Technical Report: https://docs.netapp.com/us-en/netapp-solutions/hybrid-cloud/vsphere_ontap_other_capabilities_for_vsphere.html#ontap-qos-and-vmware-sioc  

 

When you have SDRS set to "auto" and VMDKs files are copied to a new datastore by vSphere, the VMDK files in the original location are deleted by SDRS which can cause your ONTAP snapshot space to dramatically increase as you have seen.  When SDRS deletes the files related to the VM that was moved, those data blocks are no longer part of the active file system on the original datastore and the space associated with those data blocks is now being accounted for in the ONTAP Snapshot space in the original datastore volume.  

 

Among the considerations for keeping the default "manual" setting for SDRS are:

  • When SDRS moves VMDKs between datastores, any space savings from ONTAP cloning or deduplication are lost. You can rerun deduplication to regain these savings.  
  • Moving VMDKs between datastores on the same aggregate has little benefit and SDRS does not have visibility into other workloads that might share the aggregate.  
  • SDRS is reacting to a measurement crossing a specific threshold and does not understand whether the event trigger is an temporary anomaly/performance spike in the ONTAP system.   By using the "manual" SDRS setting,  you can further investigate whether the event trigger was just a performance spike in the ONTAP system or is an situation that would warrant moving the VM to a different datastore.  

You can use "auto" for SDRS, but you'll need to keep an eye on ONTAP Snapshot space consumption as you experienced.  You can consider using Active IQ Unified Manager to set an alert trigger for Snapshot space growth to provide you an alert on the sudden spike in Snapshot space growth.

View solution in original post

1 REPLY 1

jeras

Our recommendation is to use the default storage DRS setting of "manual".  This is discussed towards the bottom of this section of TR-4597, the VMware vSphere for ONTAP Best Practices Technical Report: https://docs.netapp.com/us-en/netapp-solutions/hybrid-cloud/vsphere_ontap_other_capabilities_for_vsphere.html#ontap-qos-and-vmware-sioc  

 

When you have SDRS set to "auto" and VMDKs files are copied to a new datastore by vSphere, the VMDK files in the original location are deleted by SDRS which can cause your ONTAP snapshot space to dramatically increase as you have seen.  When SDRS deletes the files related to the VM that was moved, those data blocks are no longer part of the active file system on the original datastore and the space associated with those data blocks is now being accounted for in the ONTAP Snapshot space in the original datastore volume.  

 

Among the considerations for keeping the default "manual" setting for SDRS are:

  • When SDRS moves VMDKs between datastores, any space savings from ONTAP cloning or deduplication are lost. You can rerun deduplication to regain these savings.  
  • Moving VMDKs between datastores on the same aggregate has little benefit and SDRS does not have visibility into other workloads that might share the aggregate.  
  • SDRS is reacting to a measurement crossing a specific threshold and does not understand whether the event trigger is an temporary anomaly/performance spike in the ONTAP system.   By using the "manual" SDRS setting,  you can further investigate whether the event trigger was just a performance spike in the ONTAP system or is an situation that would warrant moving the VM to a different datastore.  

You can use "auto" for SDRS, but you'll need to keep an eye on ONTAP Snapshot space consumption as you experienced.  You can consider using Active IQ Unified Manager to set an alert trigger for Snapshot space growth to provide you an alert on the sudden spike in Snapshot space growth.

View solution in original post

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public