Policy Domain Retention Period

[Snafu]

Hi

I'm new to TSM and I'm hoping that someone can clarify something for me in relation to the backup retention period in the Policy Domain.

What exactly does the Backup Retention Period in the Domain Properties actually do? The Help indicates that it's a number days inactive versions are kept under certain conditions. My understanding was that Management class dealt with inactive retention times.

Thanks

 

[Mikey D]

BACKRETention Specifies the number of days (from the date the backup versions became inactive) to retain backup versions that are no longer on the client file system. This parameter is optional. You can specify an integer from 0 to 9999. The server uses the backup retention value to manage inactive versions of files when any of the following conditions occur: * A file is rebound to a new management class, but neither the new management class nor the default management class contains a backup copy group. * The management class to which a file is bound no longer exists, and the default management class does not contain a backup copy group. * The backup copy group is deleted from the management class to which a file is bound and the default management class does not contain a backup copy group.


ARCHRETention Specifies the number of days (from the date of archive) to retain archive copies. This parameter is optional. You can specify an integer from 0 to 30000. The server uses the archive retention value to manage archive copies of files when either of the following conditions occur: * The management class to which a file is bound no longer exists, and the default management class does not contain an archive copy group. * The archive copy group is deleted from the management class to which a file is bound and the default management class does not contain an archive copy group.

 

[TonyB]

hehe - in short, its a failsafe... if you backup/archive a file on day 1 to class SNAFU, then that file gets deleted from the client node (i.e. can no longer be rebound to a new mgmt class) on day 2, then on day 3 you remove the SNAFU management class (perhaps intending to replace it with the "FUBAR" class) - the server doesn't know how to expire the object anymore. At this point the failsafe domain-level class is used.

 

[kerryadelfred]

hiii

i m new in this forums and i just need a help in it
and i wish that this site will response me well,,,

________________________
"Want to get-on Google's first page and loads of traffic to your website? Hire a SEO Specialist from Ocean Groups seo pecialist
"

 

[pageranking]

google ranking

Define a new policy domain just for the HSM for Windows client. Define a policy set for the new domain. Define a new management class with an archive copy group that specifies an appropriate retention period for migration copies. Assign the new management class as the default for the new policy domain and policy set. Validate and activate the policy set. Update the HSM for Windows client node to become a member of the new policy domain.
As a result, all migration and archive copies on the Tivoli Storage Manager server that are associated with the HSM for Windows client node and that were previously bound to the old default management class are rebound to the new default management class.

If the HSM for Windows client node name is the same as the backup-archive client node name, this change can also affect the archive copies created by the backup-archive client.