Skip to main content
NetApp Knowledge Base

How to move a vfiler from one volume to another within the same filer?

Views:
578
Visibility:
Public
Votes:
0
Category:
data-ontap-7
Specialty:
7dot
Last Updated:

Applies to

  • MultiStore/vFiler
  • Data ONTAP 7 and earlier

Answer

You can use snapmirror (volume SnapMirror® (VSM) or qtree SnapMirror® (QSM)), ndmpcopy to move the vfiler unit from source to destination with in the same filer as below:

Original Vfiler configuration is as below:

fas3020cl1> vfiler status -r

vf1 running
ipspace: default-ipspace
IP address: 10.61.84.32 [unconfigured]
Path: /vol/org/qt [/etc]
UUID: 908bd298-0d18-11de-9592-00a09809694e
fas3020cl1>

Here the vfiler named vf1 resides on path /vol/org/qt.

In order to move this vfiler vf1 to a different volume, follow the below steps:

  1. qtree snapmirror /vol/org/qt /vol/new/qt

    Note: The destination qtree name should be same as the original. Later we will change the destination volume name as the original as well.

  2. Vfiler stop vf1
  3. vfiler destroy vf1
  4. vol rename org old
  5. vol rename new org
  6. vfiler create vf1 -r /vol/org/qt.
  7. vfiler run vf1 setup

For example:

fas3020cl1> vfiler status -r
vfiler0 running
ipspace: default-ipspace
IP address: 10.61.84.30 [e0a]
Path: / [/etc]
UUID: 00000000-0000-0000-0000-000000000000

vf1 running
ipspace: default-ipspace
IP address: 10.61.84.32 [unconfigured]
Path: /vol/org/qt [/etc]
UUID: 908bd298-0d18-11de-9592-00a09809694e
fas3020cl1>

fas3020cl1> vol create new aggr0 1g

fas3020cl1> snapmirror initialize -S /vol/org/qt /vol/new/qt <<< Make sure the destination qtree name is same as source.

fas3020cl1> snapmirror quiesce /vol/new/qt

fas3020cl1> snapmirror break /vol/new/qt

fas3020cl1> vfiler stop vf1 <<< This step stops the vfiler running on original volume/qtree

fas3020cl1> vfiler destroy vf1 <<< This step destroys the vfiler running on original volume/qtree

fas3020cl1> vol rename org old <<< Change the original volume to something else.

fas3020cl1> vol rename new org <<< Change the new volume to vfilers original volume name.

Now recreate the vfiler unit vf1 to run from the newly created volume as below:

fas3020cl1> vfiler create vf1 -r /vol/org/qt
Sun Mar 8 02:54:45 GMT [fas3020cl1: cmds.vfiler.info:notice]: vFiler unit vf1 restored.
vf1 running
ipspace: default-ipspace
IP address: 10.61.84.32 [unconfigured]
Path: /vol/org/qt [/etc]
UUID: 908bd298-0d18-11de-9592-00a09809694e
Protocols allowed: 7
Allowed: proto=rsh
Allowed: proto=ssh
Allowed: proto=nfs
Allowed: proto=cifs
Allowed: proto=iscsi
Allowed: proto=ftp
Allowed: proto=http
Protocols disallowed: 0
The etc configuration directory for vfiler "vf1" is /vol/org/qt/etc.
The IP addresses of vfiler "vf1" are still unconfigured.
To use these addresses, you must configure them using the
setup command. You can also manually configure addresses
with the ifconfig command and make those settings
persistent by adding the ifconfig command lines to /etc/rc.
fas3020cl1> Sun Mar 8 02:54:45 GMT [fas3020cl1: cmds.vfiler.info:notice]: vFiler unit vf1 initialized.

fas3020cl1>

Note: Most vfiler configurations will have more than one volume or qtree path as their resource. In such cases, the vfiler assign should be performed to move those resources from the hosting vfiler0 to this vfiler upon recreating the vfiler.

Additional Information

N/A

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.