Thank you Tom. Wanda also had a great suggestion.
I am looking at both suggestions to see which one works
best in our environment. I will be performing a test D/R
within the next couple of weeks.
Angel
----Original Message-----
From: KauffmanT [SMTP:KauffmanT AT NIBCO DOT COM]
Sent: Wednesday, October 13, 1999 9:23 AM
To: ADSM-L
Cc: KauffmanT
Subject: Re: Crash recovery doc.
We've got all the ADSM data on a seperate volume group, and recover
the
group with restvg.
1) create an exclude file for the VG in /etc
our /etc/exclude.adsmdatavg contains the two characters /*
2) save the VG with savevg (savevg -e -i -f /DR/backup.adsmdatavg)
this will create a 50KB or 100KB file in the /DR directory -
no
userdata, just the LV and filesystem definitions
3) reload (at the D/R center) with your MKSYSB
4) restvg -f /DR/backup.adsmdatavg hdiskn hdiskn+1 . . . use enough
drives
to re-create the VG
5) We have a library here, and use manual drives at the D/R site - so
we
edit the devconfig file to change the
library to manual
6) Do the dsmserv restore db to restore from your most current ADSM
database
backup
7) In our case, re-define the library as manual again
8) start formatting runs against the storage pool files
This process has worked through 5 successfull ADSM recoveries, and 3
successfull SAP database recoveries so far.
Tom Kauffman
NIBCO, Inc
> -----Original Message-----
> From: ANGEL BUGARIN [SMTP:ANGEL.BUGARIN AT MAIL.SPRINT DOT COM]
> Sent: Wednesday, October 13, 1999 1:34 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Crash recovery doc.
>
> ADSM will be reinstalled using the mksysb. This way the orginal
files
> and configurations will be intact.
>
> One method of crash recovery I was thinking of is running a tar
against
> the filesystems. If any of the disk fails, I would install the OS
using
> the
> mksysb which also contains the ADSM server application then
restoring
> the files. Any thoughts on this?
>
> -----Original Message-----
> From: PrathW1 [SMTP:PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU]
> Sent: Wednesday, October 13, 1999 5:48 AM
> To: ADSM-L
> Cc: PrathW1
> Subject: Re: Crash recovery doc.
>
> If the ADSM server application is in rootvg, will it be
> reinstalled
> as part of restoring the mksysb, or do you intend to reinstall
it
> from the
> CD?
>
> > -----Original Message-----
> > From: ANGEL BUGARIN [SMTP:ANGEL.BUGARIN AT MAIL.SPRINT DOT COM]
> > Sent: Tuesday, October 12, 1999 10:04 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Crash recovery doc.
> >
> > Hello everyone. I need to create a documentation on
> > crash recovery. The crash is defined as "all disk drives
> > are completely thrashed/inaccessible" that a reinstallation
> > of the ADSM server application is required. The following
> > are facts:
> >
> > 1. We don't have DRM installed.
> > 2. The ADSM server application is installed in rootvg.
> > 3. The data and recovery log are in a seperate volume
> group(adsmvg).
> > 4. We perform a full ADSM database backup after all regular
> > backup processes are completed.
> > 5. A listing of the device config(devconf.bk) and volume
history
> > (volhist.bk) is created. A copy of the dsmserv.opt is
also
> made.
> > The devconf.bk, volhist.bk and dsmserv.opt are placed in
a
> > directory
> > called /mksys which is included in our weekly OS backup.
> >
> > I understand that after ADSM is reinstalled, it does not know
about
> > the tape volumes in the volhist.bk or their contents. In
general,
> what
> > are the steps to perform to bring ADSM back to the last full
> database
> > backup--that is if still possible.
> >
> > Your suggestions or comments are appreciated.
> >
> > Thanks,
> > angel
> >
> >
> >
>
>
--openmail-part-0e855a12-00000001--
=========================================================================
|
