Skip to main content
NetApp Knowledge Base

Queries regarding SVM DR testing

Last Updated:

Applies to

  • ONTAP 9.8
  • System Manager
  • SVM Disaster Recovery (SVM-DR) with identity preserve.


  • You should not start the production and the DR vservers at the same time without breaking the relationship in case of identity-preserve true, as it would cause duplicate IP addresses in the environment.
    • Creating a new LIF is not permitted on a Vserver that is configured as the destination for identity preserve Vserver DR either.
    • Starting a destination SVM of a SVM-DR identity-preserve relationship would throw an error - Error: command failed: Failed to start Vserver "DR_SVM" as the partner Vserver is operationally up.
  • However, if the SVMDR is identity-preserved false relationship then you could start the destination SVM, which would bring the destination data interface up and you’d be able to access the vserver via CIFS/NFS.
    • If you wish to use the SVMDR secondary site for Development and testing purposes you must use relationships with identity preserve set to FALSE.
    • With identity preserve set to false, you could start the destination SVM while the source SVM is still up.
    • This is because, accessing data on destination of an identity discard Vserver DR relationship requires separate LIFs, CIFS server, export policy etc. to be created manually.
  • You cannot directly clone the DP volume involved in an SVM-DR relationship.
    • On GUI you’d see an error – “This operation is not permitted on a Vserver that is configured as the destination for Vserver DR”.
  • However, you may mount these DP volumes directly. Example:

cluster2 ::*> vol mount -volume vol1 -junction-path /vol1 -vserver DR_SVM

  • Another workaround to test individual volumes is to fan-out the volumes to another SVM (on same cluster). Volumes that are contained in an SVM DR source SVM can be the source for other SnapMirror relationships. You may create another (default) SVM at destination cluster and setup a fanout relationship.
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.