Ray,
Others have responded with the simple way of doing this. When you have multiple tape
drives you'll find tthat you need to increase the number of precess and then you'll
find that each backup stg command has to finish all its tasks before it completes.
Thus you'll be stuck waiting for the copy of your biggest node's data to complete.
There is a more complex way which will use your drives more effectively
My main TSM Server has four separate major stgpool hierarchies. "A" goes direct to
tape, B, C and D go disk to tape, and there are actually two diskpools in the
hierarchy one onsite and one online but offsite (the offsite pools are mainly for
failing over in event of disaster, but occasionally overnight data spills to them)
I have 3 drives available for the copypools and a different four for the primary tape
pools
My process is
run the backup diskpools script
backup stg diskpool01 tapecopy-mc maxpr=3
backup stg diskpool1M tapecopy-mc maxpr=3
backup stg diskpool02 tapecopy-md maxpr=2
backup stg diskpool2M tapecopy-md maxpr=2
backup stg diskpool04 tapecopy-MB maxpr=3
backup stg diskpool4M tapecopy-MB maxpr=3
backup stg dirdisk tapecopy-mb maxpr=2
backup stg dirseq tapecopy-mb maxpr=2
del sch wait_for_diskpools type=a
def sch wait_for_diskpools t=a cmd='run wait_for_diskpools' active=yes
startt=NOW+0:05 peru=o
The wait_for_diskpools script checks to see whether all diskpools have finished
processing, and if they have kicks of the tapepool copies, otherwise it schedules
itself for 5 minutes into the future.
select process_num from processes where process='Backup Storage Pool'
and status not like 'Primary Pool TAPEPOOL-_,%'
if (rc_ok) goto resched
issue message I 'Backup of diskpools is complete'
run backup_tapepools
exit
resched:
del sch wait_for_diskpools type=a
def sch wait_for_diskpools t=a cmd='run wait_for_diskpools' active=yes
startt=NOW+0:05 peru=o
issue message I 'Backup diskpool Stg is running. Next check scheduled for 5 minutes'
The backup_tapepools script is similar to the backup_diskpools script with the obvious
changes, and the wait_for_tapepools script is similar to wait_for_diskpools, but it
then kicks off a script to do local and remote database backups, a DR Plan prepare,
and expire inventory, which are all straightforward.
HTH
Steve
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> [EMAIL PROTECTED] 09/09/2004 18:10:13 >>>
All,
I would like to have a script automatically run to backup the disk
stgpool, then tape pool, and finally the database. Obviously i don't want
them all to kick off at the same time. Is there a way to run them
sequentially so tape pool backup doesn't start until disk pool backup
is done, db backup doesn't start till tape pool backup is done??
ray
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean http://www.r-a-y.org
Systems Engineer Southeastern Louisiana University
IBM Certified Specialist AIX Administration, AIX Support
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
***********************************************************************************
This email, including any attachments sent with it, is confidential and for the sole
use of the intended recipient(s). This confidentiality is not waived or lost, if you
receive it and you are not the intended recipient(s), or if it is transmitted/received
in error.
Any unauthorised use, alteration, disclosure, distribution or review of this email is
prohibited. It may be subject to a statutory duty of confidentiality if it relates to
health service matters.
If you are not the intended recipient(s), or if you have received this email in error,
you are asked to immediately notify the sender by telephone or by return email. You
should also delete this email and destroy any hard copies produced.
***********************************************************************************
