From our Insight Conference Labs.. an example of how to move a vFiler root volume. It requires that you enable the network after... a little bit of a shell game... I recommend trying it in the simulator or with a test vFiler first, then when comfortable run it on your vFiler.
--------------------------------------------------------------------------------------------
This lab will move the vfiler root volume for fas6280a_vfiler1 running on the fas3270 node. The vfiler must be stopped, destroyed and recreated using the same root volume name (the new root must be renamed to the old root name). This is quite different from moving a vfiler0 root volume using “vol options volname root”.
You can rename the volume with “vol rename old new” anytime, however to acdtually move the root volume requires that we destroy and recreate the vFiler using the same name of the root volume before/after the move to another aggregate.
Volume Data Motion (when supported by NAS volumes) was introduced in Data ONTAP 8.0.1. When supported on NAS it will eliminate the need for this lab. Volume Data Motion for NAS works in 8.0.1 but is only supported for SAN volumes and availability of the volume is not guaranteed for NAS.
The procedure below will move the fas6280a_vfiler1 root volume from aggr1 to aggr_root
- Create new root vol, restrict it, and vol copy the existing root to the newroot
- fas3270> vol create newroot -s none aggr_root 20m
- fas3270> vol restrict newroot
- fas3270> vol copy start -S fas6280a_vfiler1_root newroot
- Stop and Destroy the vfiler (we will recreate later with newroot after swapping names)
- fas3270> vfiler stop fas6280a_vfiler1
- fas3270> vfiler destroy fas6280a_vfiler1 # confirm “YES”
- Rename volumes so the newroot is the same name as oldroot
- fas3270> vol rename fas6280a_vfiler1_root oldroot
- fas3270> vol rename newroot fas6280a_vfiler1_root
- Online the new root volume and recreate the vfiler
- fas3270> vol online fas6280a_vfiler1_root
- fas3270> vfiler create fas6280a_vfiler1 -r /vol/fas6280a_vfiler1_root
NOTE: the ns1 interface will not be configured and needs to be configured. You can ifconfig the interface, or use the “setup -e”, but setup -e will wack some files since the setup command updates hosts.equiv, exports, resolv.conf, etc. These can be restored from the .bak versions copied at setup time or from snapshots. You will need to fix the rc file in a production environment (.105 will be left over from the prior lab…multistore doesn’t always clean up rc as expected).
- fas3270> vfiler status -a # not the interface is unconfigured
- fas3270> ifconfig ns1 alias 192.168.150.103 # might not be an alias in your case.
- alternatively (wacks some files) - fas3270> vfiler run fas6280a_vfiler1 setup -e ns1:192.168.150.103:255.255.255.0 (don't use setup - use ifconfig)
- fas3270> vfiler status -a # not the interface is configured
