Hi Jack,
I have three ADSM servers running on the same MVS LPAR because of the
reasons you mentioned. The only thing you need to remember to change is your
TCPPort's. I use 1500, 1502 and 1504.
I also tried to do the export/import's on the nodes. However when I ran into
some rather large Novell clients it became easier to just start all over
with the backups. The exports would run over 24 hours and cause very high
CPU usage.  It started to impact my nightly backups.

The only other issue's you may run into is if you do a lot of restores from
one node to another.  If the two nodes are located in separate servers you
will need to add the -server option to your restore.

Becky Buechler
Kimberly Clark Corporation
email: buechler AT kcc DOT com




> -----Original Message-----
> From: Jack Xu [SMTP:jack.f.xu AT BANKERSTRUST DOT COM]
> Sent: Wednesday, November 18, 1998 3:02 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Move Nodes to another ADSM server
>
> Hi,
>
> I have an ADSM server Ver 3 Release 1 Level 1.3 running on MVS.  Since the
> ADSM database getting too large -- about 17 GB and will keep growing, we
> have about 250 nodes backing up to the server and have long retention
> period,  I plan to setup another ADSM server on the same MVS machine and
> move some nodes to this new ADSM server using Export/Import . Has anyone
> done this before? Any suggestions, advice and comments will be greatly
> appreciated.
>
> Thanks and regards
> Jack