Yes...you may have missed something, but it could be
environmental...
"MY" environment:
all flavors of backups and archives (NT, os/2 (don't laugh), novell,
aix)..including oracle...etc 6pm to 6am
7:29 turn off reclaimation (reclaim no) - so no tape drives are used
for this
7:29 turn off migration (upd stgpools) - so no tape drives are used
for this
7:30 move data commands from disk to tape (tape local)
after that backup stg pools (tapepoolx to tapepooly)....to make the
vault copy
bring tapes back from the vault
backup the tsm database
eject vault copy of tapes including the backup of the tsm database
spit out select statement reports to show tape operators what will
be ejecting (to go to the vault) and what should be brought
back the next day from the vault
turn on reclaimation
update stg pools such that migration can happen
***by the way, I use an 'external' scheduler (like Maestro, ESP,
ca7, autosys, etc...) and leverage it to run move datas prior to backup
storage pools,
which all finish prior to the backup of the database...etc....the
tsm internal scheduler doesn't have this kind of capability.
Fyi Thanks Tim Williams
(972) 376-7774
Daniel Swan/TM <[EMAIL PROTECTED]>
08/08/2000 04:37 PM
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:
Subject: Help with scheduling ADSM tasks into blocks of time.
I'm re-engineering our schedule, and I'd like to dedicate blocks of
time to
particular tasks. I think I have a rough understanding of what
I require, but please tell me if I am missing anything. Of course,
you
folks don't know my exact requirements, but if anything jumps out at
your
that seems a little off base, let me know.
Unix backups: 6pm-midnite
NT Backups: Midnite-6am.
Copy Storagepool to DRMpool (tape): 6am-??
Drmtapes picked up and go offsite: 2pm.
Start Oracle hot backups (2 at a time) 6am - 6pm
Reclamation: 2pm-6pm.
Best regards,
Dan.
