Skip to main content
NetApp Knowledge Base

Is there a work around so SC can enforce retention when MAV is configured?

  1. Last updated
  2. Save as PDF
Views:
640
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • ONATAP 9.11.1 and higher
  • Multi-Administrator Verification (MAV)
  • SnapCenter Server (SC) 4.5 and higher
  • SnapCenter Plug-in for VMware vSphere (SCV) 4.5 and higher

Answer

Unfortunately, there is no work around so SC can bypass MAV and enforce retention, since it requires more than one set of credentials to do so.
 
That MAV is unsupported by SnapCenter Server is documented in the SnapCenter Server README PDF (Version 5.0 reference, Page 4).
That MAV is unsupported by the VMware Plug-in is documented in its own README PDF (Version 5.0 reference, Page 8).

Additional Information

RFE 1514982 was submitted to integrate SC Server retention policies with MAV, so it could enforce retention when MAV is configured on a volume with snapshot deletion restriction. An enhancement request for SCV has not been filed at this time.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.