In <810B92702CCED11191EC00805FA6F42AD0E5 AT magic.charlottepipe DOT com>, on
02/12/99
at 03:00 PM, "Agnew, Doug" <dagnew AT CHARLOTTEPIPE DOT COM> said:
>As I have been building a disaster recovery plan with ADSM, I have been
>trying to identify and eliminate all single points of failure. Now I've
>run up against one that won't go away, the database backup.
>As I read the manuals, I note that there is no way to create a duplicate
>copy of the database backup tape. So, if I lose (through media failure or
>whatever) the latest database backup or ANY in the series of the latest
>full and subsequent incremental backups, I cannot restore my database to
>'last backup'.
>Granted, if I have two servers and do a server-to-server backup of the
>database and then copy that archive file, I do get a copy of the database
>backup. But dual servers is not in the current configuration YET and I
>can't find any other way to avoid this single point of failure situation.
>Am I just not thinking clearly or is this a legitimate problem??
>TIA
>Doug Agnew
>DBA
>Charlotte Pipe & Foundry
>dagnew AT charlottepipe DOT com
>{As always, opinions stated herein are mine alone ......}
You can copy the dbb volumes outside of ADSM and use the copies to
restore the database. See the admin ref, appendix b, the section "restore db
to a point in time, history file unavailable".
We copy the dbb volumes and send the copies offsite, keep the volumes
adsm knows about on-site.
Keeping track of the copy volser's is the trick with this method. We do the
dbb to
specific volumes and do the copy to volser+100.
(We have an os/390 server.)
--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
=========================================================================
|