You cannot move a vFiler unit from a SnapLock volume to a non-SnapLock volume. You can only re-create a vFiler unit (with the same configuration as in the SnapLock volume) in the non-SnapLock volume. Therefore, to recover from a situation where the root of a vFiler unit is in a SnapLock volume, you need to re-create the root of the vFiler unit in the non-SnapLock volume.
Step
- To re-create a vFiler unit in a non-SnapLock volume, enter the following command:vfiler create vfilername -r path
where vfilername is the vFiler unit with the root on the non-SnapLock volume.
Re-creating the vFiler unit in a non-SnapLock volume
The following example shows how to re-create the vFiler unit (with the same configuration as in the SnapLock volume) in a non-SnapLock volume:
- Consider a vFiler unit, vfiler1, having its root in the SnapLock volume sle0 (at /vol/sle0/etc). Copy /etc from sle0 to vfvol0, where vfvol0 is a non-SnapLock volume.
- Rename SnapLock volume sle0 to sle0_temp and non-SnapLock volume vfvol0 to sle0.
- Enter the following command:vfiler create vfiler1 -r /vol/sle0 This command re-creates the vFiler unit with its root on /vol/sle0/etc (which is actually the non-SnapLock volume).
- Rename sle0 to vfvol0 in the non-SnapLock volume and temp_sle0 to sle0 in the SnapLock volume.
The vFiler unit, vfiler1, is created with its root directory switched from /vol/sle0/etc/ in the SnapLock volume to /vol/vfvol0/etc/ in the non-SnapLock volume.