Re: [NV-L] Synchonising 2 Netview Databases [SEC=UNCLASSIFIED]

[Leslie Clark <lclark@us.ibm.com>]

You can do it. 

First, you must have the same configurations
in /usr/OV/fields/C/*, user/OV/symbols/C/*, usr/OV/bitmaps/C/*, /usr/OV/conf/oid_to_type
and /usr//OV/conf/C/oid_to_sym.  If you have made changes to the delivered
files, get them straight first. Next. make sure both Netview servers are
in the discovery and are recognized as Netview servers. Also the same name
resolution, especially for the Netview servers.  You will also want
precisely the same configurations on what controls your discovery, unless
you disable discovery on the secondary. 

Tar up the database on the first system:
        tar
-cvf  nvdb.tar /usr/OV/databases/openview
OR use the nvhotbackup command, since
it pauses daemons. 

Transfer that to the secondary system,


Shut down netview fully on the second
system:
        ovstop
nvsecd

Take a backup of the secondary system.
        tar
-cvf  nvdb.sec.tar /usr/OV/databases/openview

Restore the database:
        pax
-rp e -f nvdb.tar

You can ignore errors about directories
already existing.
 
Restart the daemons from scratch as
they are at boot:
        /etc/init.d/netnmrc
   (or where ever it is on Solaris)

Correct the identity issues:
        /usr/OV/service/reset_ci
        /usr/OV/bin/mapadmin
-u <hostname>

That should do it. Remember to copy
over anything else you change as you configure things on the primary. Like
trapd.conf or snmpCol.conf for instance. 

If Support has told you that you won't
be supported when you have problems with a database that was restored from
another system, then you have to consider that. You should keep a backup
of the secondary for that purpose. If you have trouble after restoring
from the primary, restore that backup and see if you have the same problem.
         

There is also some capability in recent
maintence releases to enable the sending of traps from one to another so
that when you discover stuff on the primary, the trap to the secondary
can cause the secondary to discover it as well. I have not tried that method.



Cordially,

Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
(248) 552-4968 Voicemail, Fax, Pager

"Hart, Matthew MR 2" <Matthew.Hart2@defence.gov.au>
Sent by: nv-l-bounces@lists.ca.ibm.com

11/06/2007 06:33 PM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
cc
Subject	[NV-L] Synchonising 2 Netview Databases [SEC=UNCLASSIFIED]

Hi all,
 
We have 2 netview servers where the failover
needs to be a mirror of the primary. I've tried keeping them synced by
rsyncing the netmon seed files, location.conf etc., but unfourtuntely or
network changes too frequently for this to be effective (meaning that usually
you have to repeat what you've done on primary server on the failover server).
 
I've heard of people copying the databases
from one server to another, which would solve my problem if I could do
this every night. However, it seems as though you cannot simply rsync the
/usr/OV/databases directory over because you get a whole bunch of errors.
Does anyone know how to do this?
 
I'm running 7.1.5 sp1 on the two solaris
machines. They are on two differnent subnets (which I think is important,
according to IIBM support).
 
Thanks for any help in advance.
 
-Matt_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)