Paul,
Not sure what your retention looks like, but if you move the nodes to a
different domain with a different retention (smaller), then the data will
get bound to the new policy after a backup is performed and the new data
retention will kick in at that time. I believe that your understanding of
version deleted (verd) is off. The verde is only used once a file has been
deleted from the client.
Example: a file has been deleted from the client node, AND an incremental
backup is run, the TSM client will inform the TSM server of this fact.
This results in following actions on the TSM server:
a) The TSM server deactivates the active version of the file and no more
versions are inserted into the database.
b) The VERDELETED parameter is used to limit the number of versions held
by the TSM Server. Any number of versions in excess of the VERDELETED
setting will be marked for immediate expiration and purged (via the
same mechanism as described above in Case A).
c) All the inactive versions are tracked in the Expiring.Objects table.
Each version of the file is purged in accordance to the settings of the
RETEXTRA
parameter, except for the LAST version. Its deactivation date will
be evaluated against the RETONLY parameter of the management class
setting. This is a
safety feature of TSM to allow the last version (most recent) to be
recoverable for an extended period of time, should a user wish.
So a setting of 30 30 30 365 would keep 30 active versions (1 active 29
inactive) if a file is deleted TSM would keep 30 inactive versions and
based in the deactivate date would keep each version, except the last, for
30 days. The last inactive version would be kept for 365 days, the 365
days started the day it was deactivated, so actually that file would be
around for an additional 335 days when it became the only version of the
file still on the TSM Server.
Best Regards,
_________________________________________________________
email: ron.delaw...@us.ibm.com
From: Paul_Dudley <pdud...@anl.com.au>
To: ADSM-L@VM.MARIST.EDU
Date: 06/04/15 17:35
Subject: [ADSM-L] Moving nodes to a new policy
Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
If I have nodes that are currently under a policy that keeps 5 backup
versions, can I move them to another policy which keeps only 2 backup
versions?
Will TSM then start expiring all the older backup versions of files which
are no longer needed?
We have two nodes which are taking up a lot of backup space in TSM and
want to reduce this.
Thanks & Regards
Paul Dudley
pdud...@anl.com.au
ANL DISCLAIMER
This e-mail and any file attached is confidential, and intended solely to
the named add
ressees. Any unauthorised dissemination or use is strictly prohibited. If
you received
this e-mail in error, please immediately notify the sender by return
e-mail from your s
ystem. Please do not copy, use or make reference to it for any purpose, or
disclose its
contents to any person.
