1.  I looked in the log, expiration is not completing on it's own, it's
being stopped at the end of two hours.  There has to be some way to see
how far expiration has gotten to.  There has to be some internal way in
which expiration keeps track of where it left off, it doesn't always
just start over does it?

2.  Still reading through the PDF on DRM.

Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Monday, October 13, 2003 10:27 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 2 Questions: Expiration and DB backups


>1.  How can I tell if expiration has made it all the way through?
Right now I am only running it 2
>hours a day and I think it's way behind but I can't prove it.
>
If it finishes before the two hours are up, it has made it all the way
thru; otherwise it has not.

>2.  As part of my daily housekeeping on TSM, the script deletes DB
backups older then 14 days
>from the system.  The tapes have already been sent offsite.  Can
anyone recommend an easy way
>I can figure which tapes are the deleted ones that I can call back
onsite to reuse?
>
Use the DRM feature.

Daivd Ehresman