"pending expiration", "immediate expiration" and "minus-infinite" relation

xyzegg

ADSM.ORG Member
Joined
Jun 27, 2011
Messages
48
Reaction score
0
Points
0
PREDATAR Control23

Hi,


Could someone could explain to me what is the difference between "pending expiration" and "immediate expiration" in TSM context and how it correlates to "minus-infinite" stamp considering a copygroup definition like this:

Versions Data Exists: No Limit
Versions Data Deleted: No Limit
Retain Extra Versions: 92
Retain Only Version: 92

I just read a good article on expiration (https://www-304.ibm.com/support/docview.wss?uid=swg21224145), but I'm still confused.
 
PREDATAR Control23

If you have a file backed up with multiple versions, and backup a new version, if the total number of versions now exceeds the "Versions Data Exists", TSM gives it a minus-infinite date so that it's expired the next time expiration runs. Because your "Versions Data Exists" is set to no limit, the total number of versions of a given file will never exceed it.

This means that in your case, files only expire by age and not when a given number of versions is reached. Many use a combination of the two. Depends on the data and your requirements.
 
PREDATAR Control23

VDE works with REV.
VDD works with ROV

The following are regarding the files existing on the work station.
Versions Data Exists: No Limit <= How many inactive versions to be kept.
NOTE: The most recent version is the 'active' version and this never expire.
Retain Extra Versions: 92 <= How long to keep the inactive version

With the above settings,you are keeping ALL the versions.
Once 92 days have been reach, the files will be marked for expiration.
Your limiting factor is time not quantity.

The following are regarding the files no longer existing on the workstation.

Versions Data Deleted: No Limit <= How many versions to be kept.
Retain Only Version: 92 <+How long to keep the inactive version.

With the above, when the file no longer exist on the work station ALL the versions are kept.
The "active" version becomes an "inative" version.
Once 92 days have pass, then ALL the versions will be deleted.

Good Luck,
Sias
 
PREDATAR Control23

VDE works with REV.
VDD works with ROV

The following are regarding the files existing on the work station.
Versions Data Exists: No Limit <= How many inactive versions to be kept.
NOTE: The most recent version is the 'active' version and this never expire.
Retain Extra Versions: 92 <= How long to keep the inactive version

With the above settings,you are keeping ALL the versions.
Once 92 days have been reach, the files will be marked for expiration.
Your limiting factor is time not quantity.

The following are regarding the files no longer existing on the workstation.

Versions Data Deleted: No Limit <= How many versions to be kept.
Retain Only Version: 92 <+How long to keep the inactive version.

With the above, when the file no longer exist on the work station ALL the versions are kept.
The "active" version becomes an "inative" version.
Once 92 days have pass, then ALL the versions will be deleted.

Good Luck,
Sias

So... We can't ever really expect to see the "minus-infinte" stamp on files bind to a management class like that. Right?

Thanks for the explanation!
 
PREDATAR Control23

If you wanting to keep everything forever with the current settings.
Bad news, your not.
The data are only kept for 92 days.
Your not going to see anything beyond 92 days.

If you need to keep the data forever.
Can set everything to NoLimit.
If you do, there will be an increase an increase in scratch tape usage and the TSM Server database will grow. Also there is a possibility that you may encounter rebinding.

Other options.
- Use the archive feature.
- Use the generate backup set.
- Export the node data

Good Luck,
Sias
 
Top