See Chapter 8 for info on database maintenance, and Appendix G
for info on compression of the regular form and the turbo form
of the Netview flat database files. Gareth's instructions cover
the salient points of Chapter 8, and look good to me.
If your Netview is the only Tivoli thing on the system, a standalone
TMR, you probably don't need to do the wchkdb -u reqularly. I do it
once after everything is installed, and do the Tivoli backup of the
TMR (on the Tivoli desktop, Desktop, ..Backup). The Tivoli database
won't be changing in this case. In a full-blown Tivoli environment,
these steps are normally run on a very regular basis.
There is a backup menu on the context menu of the Netview icon, which
is probably what you are referring to, and Gareth's instructions
manually perform the most useful parts of that function. You MUST keep
all of the files under /usr/OV/databases/openview backed up together.
If you have added third-party products that update the database, you
should probably also back up symbols/C, fields/C, and bitmaps/C.
Then there is the matter of compression. Compression, especially for
rather large networks, ought to be done regularly as well. How you
do this depends on whether you are running the turbo form or not.
Read more about it. It's best to compress before it gets too big
to compress!
As for frequency, it does not hurt to maintain the database this weekly.
Certainly take the backup after you are happy with how the map looks,
and after any major changes, or after compression. And if you ever do
a restore, be sure to take a new backup after everything resynchs.
In addition, a bootable backup of the entire system is in order (mksysb
or sysback on AIX). I don't know how you do that on the other operating
systems, but at least think about transferring your Netview database
backups off to another system or medium.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
"Gavin Newman" <NEWMANGJ@banksa.com.au>@tkg.com on 09/11/2000 02:01:55 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: Re: [NV-L] Restore Object DB
Gareth
This is an area which concerns me greatly as I cannot find any clear
instructions in any of the manuals I have as to what should be backed up
and how and what to restore if there are ever any problems. I was told at
one stage by a Tivoli rep to do a wchkdb -u on my machines then run Tivoli,
select the Netview Policy region and select the Backup option.
I have been doing this each week now but I am now wondering if this is
enough? A definitive run down on the sort of periodic backup and
maintenance (a sort of "Care and Feeding of your Netview System") that
should be done would be a great help.
Cheers - Gavin Newman
>>> <Gareth_Holl@tivoli.com> 10/09/2000 06:07:19 >>>
You should probably be restoring the /usr/OV/databases/openview directory
(all
three databases together). I don't backup /usr/OV/databases because it
includes
the snmpCollect data files which can be quite large, particularly if you
backup
frequently. You can backup your snmpCollect data separately and less
frequently.
Typically I would back up NetView's Object, Topology, and Map databases,
plus
some configuration files as follows (this example only shows a backup to a
local
file system - substitute for your preferred archive mechanism):
cd /usr/OV
tar -cvf /backup/OV-files.tar databases/openview/ conf/ app-defaults/
To restore the databases and config files from the local file system:
cd /usr/OV/
[The following step adds an extra degree of safety as you can always move
"openview-date" back to "openview" if your restore fails.]
mv databases/openview databases/openview-date (eg. openview-09092000)
pax -rvf /backup/OV-files.tar -pe
At this point, I would restart netview (without netmon running) and let the
maps
synchronise. Then you should close the GUI and run the database maintenance
utilities to ensure database consistency:
ovmapcount -a > /tmp/mapcounta.txt
ovmapcount -b > /tmp/mapcountb.txt
ovtopofix -A 2>&1 | tee topofix.txt
[You should check for errors and take appropriate action, such as removing
symbols from the map(s) if they are reported as not existing in the object
and/or topology databases]
Enter "ovw &" to start the NetView GUI. Note: DO NOT start netmon at this
time. Wait for the topology and object databases to sync up with each
other.
This step usually takes longer than usual (after using the ovtopofix
utility)
but it is an important part of the process. Now enter "ovstart netmon" to
start
the netmon daemon. You should be good to go.
Please note this is my working process and it may not necessarily be the
best
possible method. You should also refer to the NetView Install and
Configuration
Guide because I think it may provide a procedure for backup and restore ??
I hope this helps,
Gareth Holl
Software Engineer
Olympics Advocate
gholl@tivoli.com
Tivoli Systems / IBM Corporation
Research Triangle Park, NC 27703. 1-800-TIVOLI-8
Jean.M.SCHMIDT@odot.state.or.us on 09/08/2000 05:58:29 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: Gareth Holl/Tivoli Systems)
Subject: [NV-L] Restore Object DB
I need to restore the object db from backup. Which files do I need to
restore, the ones in usr/OV/databases/openview/ovwdb or the ovw files in
usr/OV/bin?
Jean Schmidt
ODOT Network Management
503 986-3245
jean.m.schmidt@odot.state.or.us
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
**********************************************************************
***** IMPORTANT INFORMATION *****
This document should be read only by those persons to whom
it is addressed and its content is not intended for use by
any other persons. If you have received this message in
error, please notify us immediately. Please also destroy and
delete the message from your computer. Any unauthorised form
of reproduction of this message is strictly prohibited.
Bank SA is not liable for the proper and complete transmission
of the information contained in this communication, nor for any
delay in its receipt.
**********************************************************************
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|