DOCUMENTATION: How to preserve Veritas NetBackup (tm) Advanced Reporter (NBAR) data before upgrading to NetBackup 6.0 or later

Article:TECH46039  |  Created: 2008-01-24  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH46039
Article Type
Technical Solution

Product(s)

Environment

Issue



DOCUMENTATION: How to preserve Veritas NetBackup (tm) Advanced Reporter (NBAR) data before upgrading to NetBackup 6.0 or later

Solution



Manual: Veritas NetBackup (tm) 6.0 Installation Guide

Modification Type: Addition

Modification:
NetBackup Advanced Reporter (NBAR) is not supported with NetBackup 6.0 and later releases.  NBAR can no longer be used for reporting after the server is upgraded. Only NetBackup Operations Manager (NOM) may be used for reporting after upgrading the server to NetBackup 6.0 or later.

Before upgrading the server to NetBackup 6.0 or 6.5, follow these steps to retain historical NBAR data and disable NBAR data collection. Special instructions for installing NetBackup are also included.  Data Collected with NBAR still needs to be viewed using the NBAR viewing process, the following instructions are to disable the collection script to avoid corruption or bad data being added to the historical file.

UNIX
1.  Stop all NBAR daemons by running the usr/openv/nbar/bin/nbar.sh script

2. Remove the crontab entries for arloader and arpusher. This will stop future data collection for NBAR. You can remove the crontab entries for arloader and arpusher using the arconfig command.  The following command will remove both arloader and arpusher crontab entries:

./arconfig.sh --zap

You may list the crontab entries to verify that the arloader and arpusher entries have been removed:

crontab -l

3. Add the following line to the nbar.conf file to prevent the loader from erasing any historical data:

purgefrequency=never

4. Make arloader.sh and arpusher.sh unexecutable, using the chmod command:

chmod a+r arloader.sh
chmod a+r arpusher.sh

You may verify that the executable bits have been removed:

ls -l arloader.sh
ls -l arpusher.sh

5. Comment out the following line from the usr/openv/nbar/bin/nbar.sh script.  This will prevent armonitor from starting.

On Solaris, comment out this line:

# nohup $NBARBIN/armonitor > /dev/null 2>&1 &

On AIX and HP, comment out this line:

# $NBARBIN/armonitor &

6.  NetBackup upgrade on Solaris happens in two steps:

a. The user uninstalls the current version of NetBackup.  

The NetBackup uninstall script checks for dependencies and it will give a warning about the VRTSnbaro package. The user should ignore this warning, enter Yes and continue with package removal.

## Verifying package dependencies.
WARNING:
   The <VRTSnbaro> package depends on the package
  currently being removed.
Dependency checking failed.

Do you want to continue with the removal of this package [y,n,?,q] y
## Processing package information.
## Executing preremove script.

b. The user installs NetBackup 6.0 or NetBackup 6.5.

The NetBackup 6.x installation script detects the NBAR package and asks if the user would like to exit and remove the package.  The user should say no to this step and continue with installation.

This is an example of the install trace on Solaris:

You have the following optional NetBackup product installed:
VRTSnbaro
If you intend to upgrade this product, you should remove
its software prior to upgrading it.

Do you want to exit this script so you can remove packages now? [y,n] (y) n

Note: Select "y" if other products are listed that do need to be removed.  Once those are removed restart the installation and select "n" when no other products are listed.

On HP and AIX, the installation script doesn't give any warning while upgrading.

For more information about NetBackup upgrade to 6.x, refer to the NetBackup installation manuals, found below in the Related Documents section.

7. Start NBAR database and Web GUI Engine daemon by running the nbar.sh script.  If you have removed the NBAR package, the data is placed in the /tmp directory as a ".z" file.   Please note that this data is at risk if the system is rebooted, and will need to be recovered from a backup if a reboot occurs.  You will need the NBAR package installed and configured as noted in this tech note to read the historical data.



Windows
1. Go to bin directory and use the arconfig utility to remove the loader and pusher schedules. This command will remove the 'at' entry which starts the loader and pusher:

arconfig.bat --zap

2. Add the following line to the nbar.conf file to prevent the loader from erasing any historical data.

purgefrequency=never

3. Stop and disable the 'NBAR System Monitor' service.

Go to Start -> Settings -> Control Panel -> Administrative Tools -> Services

Stop the 'NBAR System Monitor Service' and select Properties and change the Startup Type to disabled.

4.  Now the server can be upgraded to NetBackup 6.0 or 6.5. For more information about NetBackup upgrade to 6.x, refer to the NetBackup installation manuals, found below in the Related Documents section.


Additional Note on viewing NBAR historical data
Whenever you want to see historical NBAR data, select the proper time frame and reporting day.



Legacy ID



281578


Article URL http://www.symantec.com/docs/TECH46039


Terms of use for this information are found in Legal Notices