SnapLock interaction with a vFiler unit

SnapLock disallows vFiler unit creation if the root of the vFiler unit is on a SnapLock volume.

In the release before Data ONTAP 7.3.1, the vFiler units can be created with the root on a SnapLock volume. After you upgrade to Data ONTAP 7.3.1, these vFiler units continue to operate. However, an error message is raised when these vFiler units are started. The intention of the error message is to warn about the unsupported configuration.

In Data ONTAP 7.3.1, SnapVault is vFiler unit enabled. Because the SnapLock for SnapVault feature is a SnapVault configuration with SnapVault secondary on the SnapLock volume, the following SnapVault options are also available on the vFiler unit:

snapvault.access
snapvault.enable

Creating the root of a vFiler unit from a SnapLock volume to a non-SnapLock volume
You cannot move the 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.
Limitations of vFiler units on SnapLock volumes
Following are the limitations of vFiler units on SnapLock volumes: