ADSM tells where its database volumes are from the
/usr/lpp/adsmserv/bin/dsmserv.dsk
file.  Note that the database volume names are also encoded in the database, so

you cannot simply just move the volumes around.  (Tried it! :)

  When you do the HA implementation, if you decide to put the binaries on a
shared disk, the license file will be on the shared disk as well.  As the
implementation
that I've done was on AIX, the cleanest way to keep the file package management

software (lpp) happy was to keep binaries on both boxes.  If you do this,
remember
to keep the licenses consistent on both sides.


kells


Stuart Robertson wrote:

> I need to setup an ADSM system that will fail over to another RS/6000 if
> there is a problem with primary system.
>
> The system as it has been installed (not by me!) has the database and
> recovery log volume group failing over - which is obviously required.
>
>   ------------------------------------------------------------------------
>
>  But
> I can see no way of telling ADSM on the backup system to use this database
> and recovery log - any ideas.
>
> The only way I can think of doing this is to fail over the binaries as well
> as the database and essentially fail everything over.
>
> As an aside how does ADSM know where to look for its database volumes?
>
> Stuart