Yes you can as long as extending that file to 30 extra days doesn't exceed the maximum retention policy for the SmartLock domain. You can do this in the same way you would with NTAP, that is, set the atime to the new expiration time. When SmartLock sees an atime in the future (which in normal situations should not happen) it will treat that as the expiration time for the file. So from NFS, you could use something like 'touch -at file' or if you have a script that can change file metadata via system calls that would work too. There's an equivalent thing for Windows, but I don't know it off the top of my head, but it would work similarly.
Thank you for that information. I will review it in details.
Meanwhile, as far as I understand SmartLock functionality can be accessed using the EMC's OneFS API, which is a REST based API. On the other hand files on Isilon can be accessed either via the same OneFS API or using standard operating systems File I/O functions. So my question, is it possible to apply retention rules on the file stored within the Isilon using only operating systems File I/O functions? For example NetApp's Snaplock mechanism allows setting retention using both proprietary and general operating systems APIs. I was wondering if Isilon SmartLock can also support such dual interfaces.
If all you want to do is extend the retention time of an individual file, you can do this via standard protocols by over-riding the atime of the file which is what NTAP SnapLock supports as well. The SmartLock domain will have a maximum retention time set and you would not be able to extend it beyond that, however you could extend the maximum time via the CLI or API as an admin.
Thank you for this very helpful information. One question though since you already touched it.
If I need to set the initial retention on the file, let's say for 30 days, and after that to extend it for another 30 days depending on external conditions. Is it possible to achieve via standard protocols by extending the atime of the file. I know that NTAP SnapLock supports that scenario, but can I do it with the Isilon SmartLock as well?
AdamFox
254 Posts
0
September 22nd, 2016 11:00
Yes you can as long as extending that file to 30 extra days doesn't exceed the maximum retention policy for the SmartLock domain. You can do this in the same way you would with NTAP, that is, set the atime to the new expiration time. When SmartLock sees an atime in the future (which in normal situations should not happen) it will treat that as the expiration time for the file. So from NFS, you could use something like 'touch -at file' or if you have a script that can change file metadata via system calls that would work too. There's an equivalent thing for Windows, but I don't know it off the top of my head, but it would work similarly.
Hope this helps
RobChang-Isilon
136 Posts
0
September 21st, 2016 20:00
Hi,
See if there's info here you need:
http://doc.isilon.com/onefs/8.0.0/api/en-us/03-ifs-br-system-config-api.htm
Use browser search for "SmartLock". You'll see supported API calls.
evgvk_asg
4 Posts
0
September 22nd, 2016 06:00
Thank you for that information. I will review it in details.
Meanwhile, as far as I understand SmartLock functionality can be accessed using the EMC's OneFS API, which is a REST based API. On the other hand files on Isilon can be accessed either via the same OneFS API or using standard operating systems File I/O functions. So my question, is it possible to apply retention rules on the file stored within the Isilon using only operating systems File I/O functions? For example NetApp's Snaplock mechanism allows setting retention using both proprietary and general operating systems APIs. I was wondering if Isilon SmartLock can also support such dual interfaces.
AdamFox
254 Posts
0
September 22nd, 2016 08:00
If all you want to do is extend the retention time of an individual file, you can do this via standard protocols by over-riding the atime of the file which is what NTAP SnapLock supports as well. The SmartLock domain will have a maximum retention time set and you would not be able to extend it beyond that, however you could extend the maximum time via the CLI or API as an admin.
evgvk_asg
4 Posts
0
September 22nd, 2016 10:00
Thank you for this very helpful information. One question though since you already touched it.
If I need to set the initial retention on the file, let's say for 30 days, and after that to extend it for another 30 days depending on external conditions. Is it possible to achieve via standard protocols by extending the atime of the file. I know that NTAP SnapLock supports that scenario, but can I do it with the Isilon SmartLock as well?
evgvk_asg
4 Posts
0
September 22nd, 2016 11:00
Thank you. Would I be able to test this scenario using the Isilon Simulator?