Volume rehost will result in a full outage during cutover as volumes need to be moved between SVM;’s which typically is two storage systems.
Principle steps for vol rehost
- Umount vol
- Move vol to another svm
- Mount vol and add a junction point
Vol unmount
fascls02::volume> vol unmount -vserver SVM01 -volume SVM01_vol05
fascls02::volume> vol show -vserver SVM01 -volume SVM01_vol05 -fields aggr-list,junction-path
vserver volume aggr-list junction-path
——- ———– ——————— ————-
SVM01 SVM01_vol05 fascls02_01_sata8t_01 –
Vol rehost ( change SVM on a vol )
fascls02::volume> vol rehost -vserver SVM01 -volume SVM01_vol05 -destination-vserver SVM09
Warning: Rehosting a volume from one Vserver to another Vserver does not change the security information on that volume.
If the security domains of the Vservers are not identical, unwanted access might be permitted, and desired access might be denied. An attempt to
rehost a volume will disassociate the volume from all volume policies and policy rules. The volume must be reconfigured after a successful or
unsuccessful rehost operation.
Do you want to continue? {y|n}: y
[Job 71] Job succeeded: Successful
Info: Volume is successfully rehosted on the target Vserver.
Set the desired volume configuration – such as the export policy and QoS policy – on the target Vserver.
Vol show
fascls02::volume> vol show -vserver SVM09 -volume SVM01_vol05 -fields aggr-list,junction-path
vserver volume aggr-list junction-path
——- ———– ——————— ————-
SVM09 SVM01_vol05 fascls02_01_sata8t_01 –
Vol mount (mount a vol to a junction path manually)
fascls02::volume> vol mount -vserver SVM09 -volume SVM01_vol05 -junction-path /SVM01_vol05
Warning: The export-policy “default” has no rules in it. The volume will therefore be inaccessible over NFS and CIFS protocol.
Do you want to continue? {y|n}: y
fascls02::volume> vol show -vserver SVM09 -volume SVM01_vol05 -fields aggr-list,junction-path
vserver volume aggr-list junction-path
——- ———– ——————— ————-
SVM09 SVM01_vol05 fascls02_01_sata8t_01 /SVM01_vol05