Skip to main content
NetApp Knowledge Base

What are the implications of renaming an SVM in ONTAP?

  1. Last updated
  2. Save as PDF
Views:
4,464
Visibility:
Public
Votes:
4
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • Rename SVM (Vserver)

Answer

  1. Renaming the SVM/Vserver does not change volume names. Thus, if you have the named intuitively, change them (for example, vs1_root).
  2. Volume names cannot contain special characters like '.', because your SVM/Vserver is named vs1.vcluster1, vs1.vcluster1_root cannot be a volume name.
    • As a corollary to this, if you use System Manager 3.0 to create a SnapMirror of a simple 'vol1' on a source SVM/Vserver of vs1.vcluster1, it will by default attempt to create the destination volume as 'vs1.cluster1_vol1_data_protection', which is an invalid volume name.
    • An error will be reported until you change the volume name.

Note: Renaming an SVM in ONTAP is not a 'cifs server netbios name change'.

Additional Information

 

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.