My mailbox has received your message.
I will be out of the office until June 7, 2000.
If you need immediate attention please call the help
desk at x8915.
I will review my messages when I return on June 7th.

>>> "ADSM-L AT VM.MARIST DOT EDU" 05/24/00 17:07 >>>

I have four disk pools which I migrate to tape daily, using the HIGHM=0 LOWM=0
method, requiring four admin schedules to drop the thresholds, then four more to
raise them, plus the issue of timing them so they don't overlap and utilize too
many tape drives all at once.

The thought occurred to me to do it this way, instead: Write a single macro or
script a la:

MOVE DATA <diskpoolA> <targettapepool> WAIT=YES
MOVE DATA <diskpoolB> <targettapepool> WAIT=YES
MOVE DATA <diskpoolC> <targettapepool> WAIT=YES
MOVE DATA <diskpoolD> <targettapepool> WAIT=YES

And the questions thus arose:
1) Would this work?
2) Is it more or less efficient than dropping the migration thresholds?
3) Are there considerations I'm missing?

PS - The "why four disk pools" has a standard answer: Money - i.e. adding SSA
drawer space and drives doesn't really qualify as "disk is cheap". The four disk
pools are 1- Archive, 2 - Picky API client #1, 3 - Picky API client #2, 4 All
the other luckless backup clients. Pool #4 migrates during the backups.

Regards, Steven
Steven Chaba, (confused) Lead Analyst, ADSM/AIX/HACMP
Rochester Gas & Electric Corporation
Rochester, NY USA