video on demandRestoring the root volume of an SVM
If the root volume of a Storage Virtual Machine (SVM) becomes unavailable, clients cannot mount the root of the namespace. In such cases, you must restore the root volume by promoting another volume to facilitate data access to the clients.
For SVMs with FlexVol volumes, you can promote one of the following volumes as the root volume:
Load-sharing mirror copy
Data-protection mirror copy
A new FlexVol volume
Note: If you want to restore the root volume of an SVM with Infinite Volume, you must contact technical support.
Starting from clustered Data ONTAP 8.2, SVM root volume is created with 1 GB size to prevent any failures when mounting any volume in the SVM root volume due to lack of space or inodes. Therefore, if you are promoting a new FlexVol volume, it should be at least 1 GB in size.
Situation:
cluster91::> vol show -vserver tempsvm
Vserver Volume Aggregate State Type Size Available Used%
--------- ------------ ------------ ---------- ---- ---------- ---------- -----
tempsvm datavol n2_aggr1 online RW 100MB 94.79MB 5%
tempsvm rv n2_aggr1 online RW 20MB 18.80MB 5%
2 entries were displayed.
1. Promoting a loadshare: (create svm, create loadshare, promote loadshare)
cluster91::> vol create -vserver tempsvm -volume rvls -aggregate n2_aggr1 -size 20m -type dp
cluster91::> snapmirror create -source-path tempsvm:rv -destination-path tempsvm:rvls -type ls
cluster91::> snapmirror initialize-ls-set -source-path tempsvm:rv
cluster91::> snapmirror promote -destination-path tempsvm:rvls
Note: this will delete the original rootvolume. You can rename the new rootvolume.
cluster91::> vol rename -vserver tempsvm -volume rvls rv
2. Create a snapmirror and make a dp destination the new rootvolume.
cluster91::> vol create -vserver tempsvm -volume rvdp -aggregate n2_aggr1 -size 20m -type dp
cluster91::> snapmirror create -source-path tempsvm:rv -destination-path tempsvm:rvdp
cluster91::> snapmirror initialize -destination-path tempsvm:rvdp
cluster91::*> snapmirror break -destination-path tempsvm:rvdp
cluster91::*> volume make-vsroot -vserver tempsvm -volume rvdp
cluster91::*> snapmirror delete -destination-path tempsvm:rvdp
cluster91::*> snapmirror release -destination-path tempsvm:rvdp
cluster91::*> vol offline -vserver tempsvm -volume rv
cluster91::*> vol delete -force true -vserver tempsvm -volume rv
cluster91::*> vol rename -vserver tempsvm -volume rvdp -newname rv
cluster91::*> mount -vserver tempsvm -volume datavol -junction-path /datavol
Note: Client mounts will be stale.
Note: Make sure you connect the correct policies to the volume if needed.
3. Create new volume and use make-vsroot.
cluster91::*> vol create -vserver tempsvm -volume rvnew -aggregate n2_aggr1 -size 20m
cluster91::*> volume make-vsroot -vserver tempsvm -volume rvnew
cluster91::*> vol offline -vserver tempsvm -volume rv
cluster91::*> vol destroy -force true -vserver tempsvm -volume rv
cluster91::*> vol rename -vserver tempsvm -volume rvnew -newname rv
cluster91::*> mount -vserver tempsvm -volume datavol -junction-path /datavol
Note: Client mounts will be stale.
Note: Make sure you connect the correct policies to the volume if needed.
2.