John,

Based on my experiences what you will lose is definitions for new
tape devices. All of your newly defined database and logvolumes
will be used (the restore only needs at least as much DASD for DB
and Log as the backed up database used, anything more is gravy).

I think that the backup/restore method is the best way of
transporting an ADSM server from one machine to another, both for
the reasons that you suggest, and also because it will give you
experience in restoring an ADSM database when you are not under
the pressure of having to get a down system back up.

 -- Tom

"It's a dog eat dog world,                Thomas A. La Porte
 and I'm wearing milkbone underwear."     DreamWorks SKG
              - Norm Peterson             <tlaporte AT anim.dreamworks DOT com>

On Thu, 30 Apr 1998, 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
>