I've done it from scratch on AIX, and the rule about size is the same:
The new LOG and DB must be at least as large as the old ones for the RESTORE
DB to work.

Regarding steps, I think it the steps are different depending on whether the
db and log are "corrupt" or "lost".

If you are just reloading the log and db volumes with the RESTORE DB (say to
put your data base back to an earlier level), nothing else is necessary
because your dsmserv.dsk file is still intact and that is where the db and
log volumes are defined.
(I think the name is slightly different on MVS, but the name is in the MVS
start proc.)  ADSM looks in the dsmserv.dsk file when it starts to find the
data base and log.  If the information there is not correct, it can't even
find the DB, must less restore it.

If you are in an entirely new environment, say on new hardware in a DR site,
and you have just created your db and log volumes with dsmfmt, THEN you have
to run DSMSERV FORMAT (was DSMSERV INSTALL in V2) to update the dsmserv.dsk
file, before you can run RESTOREDB.

In this case it doesn't matter if the db and log space is made up of
different size files than the original DB, or if the names are different,
just as long as the total available space is at least as large as when the
data base was backed up.

Hope this makes sense!

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************



> -----Original Message-----
> From: Dwight Cook [SMTP:decook AT AMOCO DOT COM]
> Sent: Tuesday, April 20, 1999 4:15 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: ADSM on AIX _ database recovery task
>
>      Now where I've done this in V2 under mvs I had to ensure I started
>      ADSM and "extend db" & "extend log" to the exact values they were
> when
>      the db backup was created to get the restore db to work...
>
>      Under AIX I've  never rebuilt the system on an entirely new
>      environment, only started with a server, shut it down, and did the
>      restore db with the existing DB & LOG vols that hadn't changed
> (extend
>      wise) since the backup db was created...
>
>      later,
>            Dwight
>
>
> ______________________________ Reply Separator
> _________________________________
> Subject: ADSM on AIX _ database recovery task
> Author:  thaddad (thaddad AT COLUMBIAENERGYGROUP DOT COM) at unix,mime
> Date:    4/20/99 2:48 PM
>
>
> My scenario is: ADSM database is corrupt/lost Here are steps Ive
> documented  to
> recover it. Am I on track??
>
> 1. Halt ADSM.
> 2. Recover volume history and device configuration files by recreating
> them
> from a remote copy of each file or
>     from contents of a recent DRM plan. (these must exist before the
> database
> restore is attempted)
> 2. If database and log volumes do not exist, reformat them with DSMSERV
> DSMFMT
> respectively.
> 3. Restore database from a full backup ( Im running daily full backups ).
>      DSMSERV RESTORE DB
> 4. Start the ADSM server
> 5. Run AUDIT VOLUME FIX=YES to check for inconsistences between volumes
> and the
> database that was restored.