Re: things NOT expiring
2001-07-10 13:30:55
Subject: |
Re: things NOT expiring |
From: |
Nicholas Cassimatis <nickpc AT US.IBM DOT COM> |
Date: |
Tue, 10 Jul 2001 13:11:37 -0400 |
For #3, after the db2adutl command tells TSM to delete the file, it is kept
for the "Retain Last Version" number of days, per the management class it's
bound to. 90 days is a common number there (for me, at least), so that
means you're keeping 90 versions more than you need to. You can fix this
by binding the database backups to a management class where this value is
set to 0. On the TSM Server, you'd create the new management class (I
called mine DATABASE to make things easy), and then added the following
line to the include/exclude list on the client (in this case AIX, be
basically the same on NT):
include /NAMEOFDATABASE database
Unfortunately the old backups don't rebind (since they don't have a backup
run against them, they won't), but in "Retain Last Version" days, they'll
all be gone.
Nick Cassimatis
nickpc AT us.ibm DOT com
Today is the tomorrow of yesterday.
|
|
|