Release notes
Set autocommit periods for SnapLock volumes before reverting
Contributors
Suggest changes
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
Data protection with the CLI
-
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
To revert from ONTAP 9, the value of the autocommit period for SnapLock volumes must be set in hours, not days. Before attempting to revert, you must check the autocommit value for your SnapLock volumes and modify it from days to hours, if necessary.
-
Verify that there are SnapLock volumes in the cluster that have unsupported autocommit periods:
volume snaplock show -autocommit-period *days -
Modify the unsupported autocommit periods to hours:
volume snaplock modify -vserver vserver_name -volume volume_name -autocommit-period value hours