Active Version - The most recent backup copy of an object stored in TSM storage for an object
that currently exists on a file server or workstation.
An active version remains active and exempt from deletion until it is replaced by a new backup
version, or TSM detects during a backup that the user has deleted the original
object from a file server or workstation.
Inactive version denotes an object (file, directory) in TSM server storage which has left Active state, meaning that it no longer represents the copy of the file which is
presently on the client.
The transition from Active to Inactive is irrevocable.
File Versioning, File Retention and File Expiration Explained
https://www-304.ibm.com/support/docview.wss?uid=swg21224145
http://kb.wisc.edu/helpdesk/page.php?id=9682
- 10 years retention of last active and inactive data
The active version is the most recent backup of the file.
The verdeleted works hand in hand with retonly=3650.
We have the following setting "...verdeleted=nolimit ... retonly=3650..." .
When the file no longer exist on the work station, the active version will become an incative version and all the other inactive version will be kept for 10 years.
NOTE: If the node is move to another domain or there is a change in the setting. The node will encounter what is known as rebinding.
Rebinding is the process of associating a file with a backed-up file with a new management
class name.
If the node is move to another domain and the retention is shorter, anything beyond the new limit will be delete due to the new setting.
If we need to keep data for 10 years, there will be an increase in scratch tape usage, the TSM Server database will grow.
The TSM application and hardware will go out of support.
Do suggest archive, since data bound to the archive mgmtclass does not encounter rebinding.
Or generate backup sets.
The verexist works hand in hand with retextra.
We have the following setting "...verexists=nolimit ... retextra=31...".
The limiting factor is time.
If the file changes every day, and we do a backup once a day.
We will have 31 versions of the file.
On the 32nd day, the file will be marked for expiration.
If we do more than one backup, and the file have changed since the last backup.
We can have more than 31 versions of the file.
- 31 days and 31 versions of active data
The most recent backup will be the active version and the reset will be inactive versions.
If you need 31 days of active versions for 31 days. Would generate a backup set with a retention of 31days.
Good Luck,
Sias
