You will undoubtedly get lots of other opinions on this.  Here's mine -

Hot standby is fine for non-database programs but NetView is not one of those.
For failover to work, you have to stop all the daemons on the one machine and
restart them on the other.  It is always messy.   Operators usually have a
difficult time remembering what to do in all cases.

If you want simple and easy backup, just install a second machine with NetView
on it.  You can always copy the databases from one to the other every night if
they must be synchronized in that way.  Then your backup is always up.  And I
have never met an operator yet who did not understand the backup procedure
called "walk to the other box and use it instead".

James Shanks
Tivoli (NetView for UNIX) L3 Support



Danny Lee <dannyl AT ibk.com DOT au> on 08/19/99 07:06:06 AM

Please respond to dannyl AT ibk.com DOT au

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Hot standby configuration for Netview for Unix




Hello Netviewers,

    Can anyone advise on a standard or recommended configuration for
setting up a hot-standby or disaster recovery Netview server?  ie.  the
current production Netview server is happilly managing whole network.
How should one setup a second/development Netview server that could be
activated either manually or automatically in the event that the
production server becomes inoperational?

Will appreciate any input.

Thanks,
    Danny