ADSM-L

Re: Wouldn't it be nice if...

2001-06-04 12:56:49
Subject: Re: Wouldn't it be nice if...
From: "Cook, Dwight E" <cookde AT BP DOT COM>
Date: Mon, 4 Jun 2001 11:53:33 -0500
Now beyond my earlier statement on DASD units to keep a copy of the files in
the remote location...

Just treat the TSM db like any other db.  
Say, once a week, take a full db backup, take that to the remote location,
and do a restore there... (with commit=no)
then, say, once daily (or more often) take incremental backups and apply
them to the remote location (with commit=no)
An easy way to deal with the daily incrementals would be to put them to a
disk file, ftp it to the other server and apply it.

We've moved environments by taking the full backup, performing the restore
to the "other" tsm server (commit=no) then when it was time to actually
swing over to the new server, we disabled sessions, ensured all disk data
was migrated to tape, took an incremental db backup (to a disk file), ftp'ed
it to the other server and did a restore db blah commit=yes.
So there would be nothing from keeping someone from doing something similar
over an extended period of time in order to keep a remote site in a recovery
mode... and if you have another atl with all your copy tapes in it... you
could be up and running within 30 minutes.  At least I could make that
guarantee!

This would take very few ksh scripts to automate... (ok, so this is all
based on running in an aix environment or other unix environment)

Dwight



<Prev in Thread] Current Thread [Next in Thread>