When you set a file to read-only with a retention time of zero days, the file should be WORM but deleteable immediately. A snaplock volume is tied to the overall aggregate, so it is correct that a Snaplock Enterprise aggregate can host only Snaplock Enteprise volumes.
Be extremely careful. If you commit a file with a particular retention date, you cannot delete the volume or the aggregate until all the contained files are expired. There is no back door.
________________________________
From: Steffen Kammerer [mailto:steffen.kammerer@brainlab.com] Sent: Monday, September 15, 2008 10:13 AM To: toasters@mathworks.com Subject: Snaplock Enterprise Hi all, have anyone experienced snaplock enterprise? I have a snaplock enterprise aggregate in which I create volumes. As far as I know the volume will inherit the snaplock enterprise. The compliance clock is also set. -- The options of my testvol look like xxxxxx> vol options testvol nosnap=off, nosnapdir=off, minra=off, no_atime_update=on, nvfail=off, ignore_inconsistent=off, snapmirrored=off, create_ucode=off, convert_ucode=off, maxdirsize=20971, schedsnapname=ordinal, fs_size_fixed=off, snaplock_enterprise, guarantee=volume, svo_enable=off, svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, no_i2p=off, fractional_reserve=100, snaplock_default_period=min, snaplock_minimum_period=0d, snaplock_maximum_period=30y, extent=off, try_first=volume_grow snaplock options look like xxxxxx> options snaplock snaplock.autocommit_period none snaplock.compliance.write_verify off -- If I copy data in this volume (using cifs) and change the files to read only I can not change data any more. But the snaplock_minimum_period is set to 0 days. Now my final question: Is it not possible to create volumes within a snaplock enterprise aggregate without using snaplock enterprise?! Do you have any hints?! Regards, Steffen