You can use tar to backup your NetView databases, but you need to use pax
to restore them.
And it looks like you should compress your databases with the utilities in
/usr/OV/service.
Here's re-post of Leslie Clark's succinct and excellent advice on this
subject.
James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Please note that my new id is jshanks@us.ibm.com
"Leslie Clark" <lclark@us.ibm.com>@tkg.com on 05/18/2001 09:45:31 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Netview Maint. Issues and Problems
... this is
what I recommend to all customers I visit. You can check the man pages
for explanations of these commands. The functions are outlined in the
Diagnostics manual.
Reorganizing the Databases
From time to time it is advisable to re-synchronize the various netview
databases. I recommend that you do it weekly. It is not necessary to
take the map down while you do this, but it is recommended.
1.) ovmapcount -a
2.) ovstop netmon
3.) ovtopofix -a (watch the output for any instructions)
4.) ovstart
5.) ovobjprint -S (note number of objects in database)
6.) ovtopodump -l (note real numbers of nodes, interfaces)
Backing up and restoring the Netview database(s)
All of the databases for the maps are under /usr/OV/databases/openview.
They can be backed up to disk at some point where the map is just the
way you want it, and restored to that point in case of a problem. Even
if it is a little out of date, it will quickly synchronized and become
current, saving you from redoing all of your cutting and pasting.
Do this weekly, or after major changes, or before software updates.
If you DO restore it, be sure to save it again after it synchs up!
Your backup directory is /_______/backups
To save the netview databases:
cd /_________/backups
tar -cvf nvdb.baknn.tar /usr/OV/databases/openview
where nn is some unique number or date indication.
To restore:
cd /_________/backups
pax -rp e -f nvdb.bknn
(Use pax for the restore because Netview databases are sparse filesystems.
Using tar to restore them would result in very large, mostly empty, files.
The pax command understands sparse files and restores them using only the
necessary space.)
It is best to do the backup when everything is shut down, but not
essential.
To do the restore, you must close all maps and do an ovstop.
When restoring, you may find it necessary to do an ovw -fields, ovw
-verify,
ovw -config. If you restore a backup made on another system, or before the
ip address was changed, you will also need to do a
/usr/OV/service/reset_ci ( the chicken soup of Netview...)
mapadmin -u <hostname>
Compressing the databases
Classic database format: (Initially, on rediscovery, this is the format)
Further compression is necessary somewhat less frequently.
Check monthly this way
1) cd to /usr/OV/databases/openview/ovwdb/current
2) ls -l value_info.pag (note size is in bytes)
3) du -a value_info.pag (note size is in 512 byte blocks)
4) multiply output result of the 'du -a' command by 512 to get bytes
5) If the 'ls -l' output gets to 50% larger than converted 'du -a'
output, it is time to compress.
After a backup, and making sure you have 20% free space in the
/usr/OV/filesystem, compress the databases with:
ovwdbdmap -c
and then take a new backup. Note that if the value_info.pag does not
compress, then it did not need compression. If you are using a seedfile
with oids rather than address ranges for restriction, then you may have
a large number of 'stub' objects in the database which will cause the
'ls' value to be many times larger than the 'du' value, but still not be
compressable. If this is the case, it is recommended that you switch
to the turbo form of the database.
-- OR --
Turbo database format:
Further compression is necessary somewhat less frequently.
Do it monthly this way:
1) Take a backup (see above)
2) Make sure you have space in /usr/OV
a) cd to /usr/OV/databases/openview/ovwdb
b) du -rs (note size is in 512 byte blocks)
c) Double this. This is how much space you need free in /usr/OV (est
50MB)
d) Check space in /usr/OV with df -ks /usr/OV
3) Close all guis
4) Stop daemons (ovstop)
5) /usr/OV/service/nvTurboDatabase speed
6) Take a new backup.
Remember that you are using the Turbo form of the database as opposed to
the regular or classic format, in case you are asked.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Sebastian.Szumczyk@natned.com.pl@tkg.com on 08/31/2001 09:28:47 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: [NV-L] value_info.ovf?
hi,
right now i'm tryin' to make full backup of my aix 4.3 but i've got a
problem with a file called value_info.ovf. the file's got more than 1,2 GB
and smitty can not backup it. my question is how to backup it in different
way, and what's the file in fact (visual database???)? i also know, that i
can not use tar command to backup the netview database cause it can't
backup
null files, is it true? what can you recommend me instead of this?
the problem is very urgent:-(((
thanx for any mail
regards
sebastian szumczyk
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|