Hi all,
I changed the snaplock volume to 0d today in the morning. I think it took some time to make it active... Now I can create a file, make it read only and delete it. No problem. Modifying the file is still not permitted but thats ok...
Thanks for your help.
Regards,
Steffen
-----Original Message----- From: Steiner, Jeffrey [mailto:Jeffrey.Steiner@netapp.com] Sent: Monday, September 15, 2008 1:47 PM To: Roesler, Brigitte; Steffen Kammerer Subject: RE: Snaplock Enterprise
If you keep reading that KB article, there's a note at the bottom that explains that 0d=infinite was due to a bug. It was NOT the intended function of 0d. A retention of 0d should be immediately deleteable unless you're subject to the bug which was fixed in 7.1.2. I learned of this bug the hard way when I snaplocked about 2TB of data into infinity and had to get the entire aggregate replaced.
-----Original Message----- From: Roesler, Brigitte [mailto:brigitte.roesler@siemens.com] Sent: Monday, September 15, 2008 12:42 PM To: Steffen Kammerer Cc: ROESLER, BRIGITTE; Steiner, Jeffrey Subject: AW: Snaplock Enterprise
Hello,
maybe the NetApp-articel "https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb18 752" will help / will be of interest.
Aggregates / Volumes created with the Snap Lock Compliance license cannot be changed to the Snap Lock Enterprise license.
So be very careful with the snaplock options "0d", because **************************** 0d is the same as "infinite" **************************** .
Therefore we set the minimum and default snaplock period to "1d".
Best regards, Brigitte Rösler
-----Ursprüngliche Nachricht----- Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Steiner, Jeffrey Gesendet: Montag, 15. September 2008 12:42 An: Steffen Kammerer; toasters@mathworks.com Betreff: RE: Snaplock Enterprise
Sorry, I mentally transposed Enterprise and Compliance. In any case, the volume type is tied to the aggregate type.
Still, you should be able to delete the file with a retention time of 0d. That means WORM but deleteable right away. I've done it within scripts a few times where I needed a file WORM right away but there was a delay in determining what the retention time should be. The script set that later on.
From: Steffen Kammerer [mailto:steffen.kammerer@brainlab.com] Sent: Monday, September 15, 2008 11:17 AM To: Steiner, Jeffrey; toasters@mathworks.com Subject: RE: Snaplock Enterprise
I have set the retention time to 0d but it is not deleteable... I think you have to wait for at least 23 hours 59 minutes and 59 seconds...
I have installed snaplock enterprise, so I can offline and destroy volumes to test...
From: Steiner, Jeffrey [mailto:Jeffrey.Steiner@netapp.com] Sent: Monday, September 15, 2008 12:12 PM To: Steffen Kammerer; toasters@mathworks.com Subject: RE: Snaplock Enterprise
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