In the part 3 of this series I will be blogging about litigation hold and delete hold from a technology perspective and specifically how it is implemented using IBM Infosphere Optim solution.This is a confusing topic and even many senior practitioners get confused when using these terms in the Optim world. Hope this article would serve as a reference for the community.You can use Optim’s Litigation Hold to protect information in an Archive File for legal inquiry or investigation. Litigation Hold prevents deletion of the file and supersedes any retention setting. So lets understand the differences between Litigation hold and Delete hold in Optim.
Litigation hold is “ONLY” relevant when we are using a backup device like a WORM Device like Hitachi Content Archive Platform (HCAP) or a Centera / Tivoli etc backup devices.For implementing Litigation hold you will need to setup a storage profile using one of these backup devices and using appropriate retention policies. If Litigation Hold is set for an Archive File, you cannot delete the Archive File or Directory entry.
“Delete Hold” can be specified for Archive files stored in a Optim Server having a storage profile not backing up to a backup device and having a retention policy specified. If Delete Hold is set for an Archive File, you cannot delete the Archive File or Directory entry.
Now since we know the definitions lets dig a bit deeper on how to implement both of these.My intention is not to go through all the steps but give enough hints to enable to reader to take it forward once he reads this article. I am trying to be as elaborate as I can be without being accused of blasphemy in the blogging world :).
For illustration purposes we will consider Centera integration with IBM Optim but there are other options available for backup devices. The central piece of the litigation hold is again the storage profile. Shown below is a typical screenshots of how to create a Centera specific storage profile.
The minimum retention period is measured from the time the Archive Process copies the Archive File to Centera. After the minimum retention period expires, the file can be deleted from Centera. This setting is available only when the Allow User to alter Minimum Retention check box in Product Options is selected.
Note: If Litigation Hold is set for an Archive File stored on a Centera backup device, you cannot delete the Archive File from storage, regardless of the file retention setting.
You can select an option to delete the Archive File from disk.
Select an option to
- Delete the Archive File from disk immediately after the Archive Process is complete
- Delete the Archive File from disk after the specified period, measured from the time the Archive File was last accessed, either by Optim™ or other software
- Not delete the Archive File from disk.
Select an option to
- Delete the Archive File from disk immediately after the recall is complete
- Delete the Archive File from disk after the specified period, measured from the time the recall is complete.
Select check box to specify a date after which the Archive File is automatically deleted.
Specify the name of the Storage Profile defined above to be referenced during the Archive Process to complete the integration of IBM Optim with Centera.
Phew!! That brings us to the end of this series of discussions on data retention using IBM Optim. I wont say that we have covered all the nuts and bolts of data retention but hopefully enough to clear some doubts. I will be back next week with some new topic related to IBM Optim and others.
Hope you enjoyed reading this blog and do send me your valuable comments. In case you would want me to blog on something specific to IBM Optim do let me know and I would attempt to include that in my future blogs.
Well this is much food for thought for now. Till next time its me Girish, signing off.