ADSM-L

Re: TDP R/3 Versioning and Off-site Vaulting

2002-03-25 11:55:21
Subject: Re: TDP R/3 Versioning and Off-site Vaulting
From: Nicholas Cassimatis <nickpc AT US.IBM DOT COM>
Date: Mon, 25 Mar 2002 11:52:52 -0500
Instead of playing with the utl file, why not modify the TSM storage pools?
Send the backup to a primary pool with no volumes assigned to it, then
modify the nextpool parameter as needed.  All week it points to your normal
onsite tape pool, but for the weekly backup you want offsite, it points to
another pool.  This other pool is backed up to your offsite pool.  Two
admin schedules is all it takes for the swapping, and another one for the
backup storagepool.

Pools:

Storage      Device       Estimated    Pct    Pct  High  Low  Next Stora-
Pool Name    Class Name    Capacity   Util   Migr   Mig  Mig  ge Pool
                               (MB)                 Pct  Pct
-----------  ----------  ----------  -----  -----  ----  ---  -----------
SAPDBTAPE    IBM3590      154,439.8   19.9   20.0   100   70
SAPDBTAPE    IBM3590      154,439.8   19.9   20.0   100   70
SAPDBDISK    DISK               0.0    0.0    0.0    90   70  SAPDBTAPE
SAPDBTAPE2   IBM3590       65,400.0    4.7    4.7    50    5
OFFSAPDBTAPE IBM3590     21,578,596   32.4

(The numbers above are way off - just copied from a server I have to get
the format correct)

Schedules:

(Assume SAP database backup starts at 02:00 on Saturday, runs for 4 hours)

01:58 Saturdays         "upd stg sapdbdisk nextpool=sapdbtape2"
06:30 Saturdays         "upd stg sapdbdisk nexpool=sapdbtape"
06:30 Saturdays         "backup stg sapdbtape2 offsapdbtape"

I would modify the "normal" condition as close to the backup starting as
possible - if TSM is offline at 1:58, it's unlikely to be back up by 02:00.
And, of course, give enough time after the backup for the backup to run
long.

Nick Cassimatis
nickpc AT us.ibm DOT com

There's more than one way to skin a cat, but you'll go through a lot of
cats to figure them all out.