ADSM-L

Cleanup Backupgroups and Expiration Processing

2002-12-18 11:37:15
Subject: Cleanup Backupgroups and Expiration Processing
From: Cinda Mullen <cmullen AT ASCENSIONHEALTH DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 18 Dec 2002 10:36:26 -0600
TSMers...

We are running OS390 2.10 with a 4.2.3 TSM Server.

We upgraded to 4.2.3 in November and have been running cleanup
backupgroups off and on since that time to try to get the system object
issue resolved.  (Sure wish there was a duration parameter for the
cleanup so, we could stop it automatically instead of having to babysit
it on the weekends:)

Some days we skip the running of cleanup backupgroups and run expiration
processing to try to catch up on expiration for all the other things.

It just seems like we are going in circles, run cleanup...stop it...run
expiration...etc. and nothing ever gets caught up.

How is everyone else doing this?  IBM could give us no idea as to how
long the cleanup backupgroups might take to get all the way through.
I'm guessing we've ran it at least 20 days for 5-6 hours each day and we
don't know how much longer we will have to run it.

And, we are not getting all the way through expiration processing like
we used to do because we used to run it daily and now it is just once or
twice a week.

Anyway, was just curious as to how everyone has handled this monster and
how long it finally took to get everything cleaned up.

Thanks in advance for any input.

Cinda Mullen
Ascension Health ISD



NOTE: This e-mail message may contain information that may be privileged,
confidential, and exempt from disclosure.  It is intended for use only by
the person to whom it is addressed. If you have received this message in
error, please do not forward or use this information in any way, delete it
immediately, and contact the sender as soon as possible by the reply option
or by telephone at the telephone number listed (if available).  Thank you.

<Prev in Thread] Current Thread [Next in Thread>