When we upgraded out NT based ADSM server, we used the opportunity to
test
disaster recovery, (ie restoring without export/import.)

We built our new server, loaded the operating system, and ADSM.
Defined the Database and recovery log (If I remember right, we didn't
duplicate
the old server, but used fewer and larger database volumes, and took the
opportunity
to increase the size.

We cheated a little by migrating all our diskpools to tape, instead of
having
to restore storage pools.

We then ran our database backup, and Shut down the old server.

On the new server...
we copied the following files to the new server (We copy these to floppy
during each
database backup) Device configuration file, Server options file, and
volume history
file.
We registered our licenses
defined our tape libraries (Duplicated the old system)
stoped the ADSM Server
ran the following command from the dos prompt
'dsmserv restore db todate=today' (This won't work without a copy of the
volume history file)
rebooted the server, and everything has been working fine since.

(I don't know for sure that all steps we performed are necessary, it
worked the first
time, and we didn't test further.)



Rushton, John D wrote:
>
> We would like to move two of our ADSM servers from one machine to another.
> My thoughts on this were to set up ADSM on the new machine, perform an
> EXPORT SERVER/IMPORT SERVER to copy over all of the admin, nodes, etc. to
> the new server and format and define the new database, recovery log and
> storage volumes.    Then I would perform a full ADSM DB backup on the old
> machine and then do a DSMSERV RESTORE DB on the new machine.
>
> One question that I have is whether all of my work on the new machine
> (definition of new storage pool volumes, etc  - which is different from the
> old machine's setup due to more disk space and different file system names)
> is going to get wiped out with the RESTORE DB - what exactly will the
> RESTORE DB restore on a non-corrupt system???
>
> There was another post this morning about copying an ADSM database volume
> from one machine to another.   Is that a supported means of moving an ADSM
> server from one machine to another?    If I did that, would I have to set up
> the new machine with identical file systems and dataset names as the old
> machine???
>
> Any assistance that can be provided would be muchly appreciated...
> John Rushton
> Lockheed Martin M&DS