Backup, Restore, Cleanup, Compress Created By: Leslie Clark on 09/07/99 at 05:29 PM Category: Netview for Unix Subject: Backup, Restore, Cleanup, Compress ------------------------------ NETVIEW Database maintenance process: This document describes the following aspects of NETVIEW database maintenance: I BACKUP II RESTORE III CLEANUP IV COMPRESSION ALWAYS backup of /usr/OV/databases before performing the compression or cleanup procedures. ------------------------------------------------------------------------ I. BACKUP These steps backup BOTH the NetView databases and general configuration files. 1) Use File ->exit to stop all NETVIEW gui's. 2) Enter: ovstop to stop all NETVIEW daemons 3) Load a tape into the machine 4) Enter: cd /usr/OV 5) Enter: tar -cvf/dev/rmt0 databases conf 6) Label tape with the date ------------------------------------------------------------------------ II. RESTORE These steps restore BOTH the NetView databases AND general configuration files. Based on your situation, you may not want to restore the configuration files. 1) Use File ->exit to stop all NETVIEW gui's 2) Enter: ovstop to stop all NETVIEW daemons 3) Load the restore tape in the machine 4) Clear the current databases: Enter: rm -fr /usr/OV/databases/* Enter: rm -fr /usr/OV/conf/* 5) Restore the old databases: Enter: cd /usr/OV Enter: pax -rvf tarfile -pe databases conf 6) Restart the NETVIEW daemons (ovstart) 7) Bring up the EUI (nv6000) ------------------------------------------------------------------------ III. CLEANUP 1) Stop all Netview gui's 2) Stop the netmon daemon (ovstop netmon) 3) Run: ovmapcount -a >outfile1 4) This step requires NetView V4 with PTF U453385 or NetView v5.1, or Contact support for an efix for NetView V4 PTF U451880 or NetView v5.0. If you do not meet this requirement, please go to step 5. a) Run: ovmapcount -b >mapcountb.txt b) If you have errors listed under the heading: "Checking map objects without corresponding objects in the object database", you must delete the indicated symbols. Use the following suggested procedure to locate the symbols for deletion. If there are no errors listed, go on to step 5. c) Enter ovw& to bring up the NetView GUI. Note: You DO NOT want to start netmon at this time. d) Select This may take a long time to complete, so please be patient. e) If errors are listed by ovmapcount -b under the heading "Checking map objects without corresponding objects in the object database", a symbol and submap will be identified. Use the search feature of the "locate submap" window to find by name the submap containing the bad symbol. Enter the name of the submap in the search window and press enter. One or more submaps satisfying your search argument will be highlighted. Move up and down the list by selecting and . Select for each one and examine it for the symbol name identified. In the case of multiple submaps and symbols with the same name, the bad symbol can be identified by using the right mouse button on the symbol to bring up the menu. Select and when NO OBJECT INFORMATION can be displayed, the bad symbol has been located. f.) When the bad symbols is located, Select the symbol, Select , , , . g.) Repeat steps 4e and 4f for all the symbols listed under "Checking map objects without corresponding objects in the object database". h.) If the NetView system contains multiple maps, each one must be opened (, ) and steps 4d through 4g must be performed for each. i.) Enter ovmapcount -b > mapcountb2.txt, to confirm that you have cleaned up all the errors. j.) Before going on to step 5, Select , , to stop all NetView GUI's. 5) Run: /usr/OV/bin/ovtopofix -A 2>&1 | tee /tmp/fix.out or... /usr/OV/bin/ovtopofix -A >/tmp/fix.out 2>&1 If you see in ovtopofix "removed from topology, still in 1 maps", This means that the topo object was deleted, but there is an object in the object database still lingering. ... Bring up the NETVIEW EUI and select , , , put in the selection name for the wording "removed from topology, still in 1 maps" and press . ... Open the submap containing the located object and delete the object from all submaps. Repeat this process for all the objects that have that string. 6) Repeat step 5 until the ovtopofix runs cleanly. Contact Tivoli support if you have any questions. ------------------------------------------------------------------- IV. COMPRESSION NOTE: There are two database infrastructures possible for NetView and they require two different compression techniques. 1) Verify the need for compression: a) cd to /usr/OV/databases/openview/ovwdb/current b) ls -l value_info.pag (note size is in bytes) c) du -a value_info.pag (note size is in 512 byte blocks) d) multiply output result of the 'du -a' command by 512 to convert it to the units in bytes e) If the 'ls -l' output gets to 50% larger than converted 'du -a' output, it is time to compress. 2) VERY IMPORTANT: Ensure that you have a good backup of /usr/OV/databases before starting the compression. 3) Verify that the ulimit statements recommended in the NetView V5 release notes, have been added to either the /etc/rc.nfs or the /etc/Tivoli/oserv.rc file. If these are not present, nvTurboDatabase processing may fail due to memory problems. (In NetView V5.0 release notes - page 33; NetView V5.1, page 10) 4) Identify whether you have OLD or NEW format database infrastructure. Please use the appropriate technique or risk damage to your databases. The OLD infrastucture executes the ovwdbdmap utility and the NEW enhanced format executes /usr/OV/service/nvTurboDatabase. One can identify the NEW enhanced infrastructure by the presence of the file /usr/OV/databases/openview/ovwdb/current/value_info.cfg. 5) Compress the databases, using the OLD or NEW format steps, as determined by step '4' above. OLD FORMAT: To compress the object database: a) Stop all the NetView GUIs b) Stop the NETVIEW daemons using ovstop. c) Tar /usr/OV/databases to create a backup. d) IMPORTANT: make sure the filesystem containing the database has at least 20% freespace. If not, the compression process will probably corrupt the object database. e) Compress the object database using ovwdbdmap -c f) After the compression is complete, bring up all the daemons and EUI and allow the synchronization process to complete. This step will probably take longer than normal, but it is an important part of the process. g) Once the newly compressed database is completely synchronized, it may be used or tarred for backup (after stopping the daemons again). NEW ENHANCED FORMAT: To compress the object database: a) This step is CRITICAL to success. Confirm that you have enough free space, in the filesystem that contains the /usr/OV directory. For many users this will be the /usr filesystem. If you have a /usr/OV filesystem, then that is where the free space must exist. Issue the 'df' command to review your fileystems and the free space for each. To calculate the MINIMUM free space needed: - cd /usr/OV/databases/openview/ovwdb - du -rs (this shows the # of 512 byte blocks used currently by the ovwdb database) - Double the output of the 'du -rs' command. This value is the mimimum free space needed. b) Stop All gui's c) ovstop the NetView daemons d) The command can be run in one of 2 ways. (If in doubt, run with the 'speed' option. For most customers, that is the only option they will ever need to use) To compress BOTH the ovwdb and topology databases, and to setup for faster database access: Run '/usr/OV/service/nvTurboDatabase speed' To compress only the value_info part of the ovwdb database: Run '/usr/OV/service/nvTurboDatabase space' e) The compress creates .BAK files in the /usr/OV/databases/openview/ovwdb/current directory. These *.BAK files may be removed when you are comfortable that all has gone well. The original file name & type was NVTURBO NOTES with a time stamp of 2/22/99 13:46:36. ...........................