ADSM-L

Re: HACMP config for ADSM

1999-10-31 12:12:58
Subject: Re: HACMP config for ADSM
From: Rodrigo Gazzaneo <rodrigo_gazzaneo AT HOTMAIL DOT COM>
Date: Sun, 31 Oct 1999 12:12:58 EST
Kells,

> > > Second is a particular opinion that although ADSM is
> > > installed on /usr/lpp/adsmserv, you should never
> > > keep your configuration files and even your ADSM
> > > startup directory on ROOTVG, because if you needed
> > > to restore from mksysb tape you would be erasing
> > > important application configuration.
> >
> >      Like what?
>
> Like dsmserv.opt, like dsmserv.dsk, like volhist and
> devconfig. If they are overwritten for older versions,
> your ADSM may go very crazy ...

    dsmserv.opt -- unlikely to change, and changes are unlikely to affect
                            an emergency recovery (maybe memory changes
etc).

Ok. But still you may lose some work on tuning. You
could live with that. Like I said, on a more
complicated site, people wouldn't like to live
with that.


    dsmserv.dsk -- will be recreated when you recreate the dbs and logs


This is the point I disagree. Why recreate dbs and logs ?
In my solution, all you have to do is import ADSM external
VG and start it, everything you need will be there, you
won't move a muscle on reconfiguration, recovering files,
editing anything. This is HACMP, not DRM.

You won't have to run DRM. Besides DRM is an expensive
feature and not everybody buys it. Would they have to
reinstall and reconfigure ADSM all the time ? In my
solution the answer is no. In your solution, the
answer seems to be yes.

Imagine a cluster that has to rebuild ADSM database
everytime it does a failover ...

    You forgot the step of re-installing the ADSM binaries, patches etc
back onto the ADSM server. :)

No, I didn't. ADSM binaries and patches are on
rootvg. You restore rootvg, you restore ADSM.


     What can I say, I don't think you've given my point of view enough
credit.

No, Kells. Your solution works fine. Only you will have
a lot more work to do. Like I said before, if you are
ok with it, then it is ok.

In your cluster solution, you will be dealing with a
very dangerous aspect of HACMP : the possibility of
having different data files on each site of the cluster.
Have you ever worked with HACMP ? CLAM and IBM
does not suggest this kind of solution ...

   From this discussion, I don't think you're paranoid enough about being
able
to recover your data, but hey -- that's your comfort level.

Please, don't use such word as "paranoid". But as a system
support specialist, I should be very concerned with
data protection, availability and consistency, because they
are often much more dear to the corporation then a
humble system support specialist.

Kells, HACMP is not DRM.

Finally, if you think I am paranoid with recovery, maybe
you should change your opinion before working on a
bigger, critical, big-money-flying-around solution.

Good luck, though.

best regards,
Rodrigo

PS: let's stop this discussion ? You have your
point and I have mine.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
<Prev in Thread] Current Thread [Next in Thread>