Hello -
I have a question in regards to the snaplock compliance Autocommit feature. We currently have a volume contained in an aggregrate that has snaplock compliance applied too it. We have used this volume for a few years now without issue. In our environment we have a 2003 server that sends files to this snaplock volume with the read-only flag set on it already. Currently we are in the process of migrating to a new server and have the option to eliminate some software that was marking the read-only flag for us. This would eliminate complexity and cost. We are looking at this because we found the option for the snaplock compliance volume called snaplock_autocommit_period. My question is currently we are using this option but would like to turn it on. Will turning this feature on have any adverse effects on the rest of the volume which already contains sensitive data or will it only apply to new files being sent to the volume? As always, I appreciate the help and advice.
Environment:
FAS2240-2
8.1.1 7-mode
Cifs, NFS, Snaplock Compliance