SnapLock logging has certain limitations.
- SnapLock logging fails if there is not enough space in the logging volume.
- SnapLock logging fails if the required licenses are not installed and enabled.
The log volume is a SnapLock Compliance volume; therefore, you need to install and enable the SnapLock Compliance license.
- SnapLock logging fails if the volume used for logging is not available (is offline or does not exist).
- You cannot move a SnapLock log volume from the default vFiler unit to any other vFiler unit.
- If you want to use NTFS or a mixed security style for SnapLock logging, you must upgrade the storage system to Data ONTAP 7.3.2 or later.
In such a case, you must upgrade both the nodes in an HA pair to Data ONTAP 7.3.2 or later. This ensures that the SnapLock logging operation works correctly during a takeover.