Usually this is a load issue.  It SHOULD work just fine.
But EXPIRATION hits the data base and the log really hard.

It might make your migration run longer; do you care?

The most common issue people have when running two DB-intensive operations
together is running out of log space.

If those two ideas don't bother you, go ahead and try it, see if you like
the results.

I have 1 TSM server that is lightly loaded most of the time, on that one I
don't care when expiration runs.
BUT, on my biggest TSM server which is beaten senseless every day, I don't
dare let EXPIRATION run while other stuff is running.

So it just depends on your situation.





-----Original Message-----
From: Rob Hefty [mailto:R.Hefty AT LABSAFETY DOT COM]
Sent: Tuesday, March 11, 2003 9:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Migration vs. Expiration


Hello All,

Is there any reason that any one can think of that one shouldn't run
expiration along with migration?  Currently we have all of our maintenance
jobs single thread through a third party scheduler and I was looking to cut
down on time.  Our expiration process takes about 3 hours and migration
takes around 1 hour.

Thanks,
Rob