umur
ADSM.ORG Senior Member
Hello,
I was wondering about the retention rules on copy storage pools. Do they follow the retention rule of the primary storage pool they are copied from? Or is there a rule on DRM preferences? This may be a simple question, however I was unable to find an answer...
Right now, I am using delete volume to clear tapes returning from disaster recovery site... As you are guessing, this is tiring manual labor and it always has the risk of me deleting a wrong tape, so I would like to apply a best practice on this subject to let these tapes become scratch without an intervention by an admin or operator.
Currently, the primary storage pools archives are kept for 45 days, and backups are kept like this:
Versions Data Exists: No Limit
Versions Data Deleted: 4
Retain Extra Versions: 60
Retain Only Version: No Limit
And I copy primary pools using "backup stg" command. I am currently working on TSM 5.4.3.0 but I am willing to upgrade to 5.5.x if that provides a solution.
Regards,
Umur
I was wondering about the retention rules on copy storage pools. Do they follow the retention rule of the primary storage pool they are copied from? Or is there a rule on DRM preferences? This may be a simple question, however I was unable to find an answer...
Right now, I am using delete volume to clear tapes returning from disaster recovery site... As you are guessing, this is tiring manual labor and it always has the risk of me deleting a wrong tape, so I would like to apply a best practice on this subject to let these tapes become scratch without an intervention by an admin or operator.
Currently, the primary storage pools archives are kept for 45 days, and backups are kept like this:
Versions Data Exists: No Limit
Versions Data Deleted: 4
Retain Extra Versions: 60
Retain Only Version: No Limit
And I copy primary pools using "backup stg" command. I am currently working on TSM 5.4.3.0 but I am willing to upgrade to 5.5.x if that provides a solution.
Regards,
Umur