Rodrigo Gazzaneo wrote:

> I have one doubt.
>
> For the solution of moving binaries on the
> cluster, how do you install ADSM on a
> different directory ?

    I don't know why you would want to install ADSM in a different directory,
but with the use of symlinks, you certainly can (after the fact -- ugly at
upgrade time :).

  My point was that if you wanted to store the binaries on the shared disk that
move from the primary machine to the failover machine, that is an option.  It
is also a guarantee against split brain syndrome.  :)  On a Solaris box, that
would
be my approach, as the whole pkgadd kludge stuff doesn't thrill me -- although,
I haven't seen what joys and delights Installshield gives us.  :)

  ie mount /dev/blockdev /usr/lpp/adsmserv

     where /dev/blockdev lives in a shared AIX volume group

>
> Every time I install it the filesets go
> to the same place ...
>
> It is a lot easier to install it on
> both servers and share only
> config files, db, log, pools, etc.
>

   Actually, I'd be willing to say that it's a lot easier to install the whole
mess on
shared disk.  The downside is that doing upgrades is messier in that you may
have
to failover to the machine in which the binaries were originally installed.
Offhand,
I can't recall if there was any license info that was keyed to a host id (I
think there
is), so the only thing that would have to be done is to make a symlink that
would
point to the correct license file for each server.

  <Shrug>  Either way works.  I implemented the ADSM environment basically in
the manner you describe.


kells


>
> regards,
> Rodrigo
>
> >From: Kells Kearney <kells AT WINTERLAND.MAINLAND.AB DOT CA>
> >Reply-To: kells AT winterland.mainland.ab DOT ca
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: Re: HACMP config for ADSM
> >Date: Fri, 29 Oct 1999 13:33:08 -0400
> >
> >   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
> >
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com