Veritas NetBackup™ OpsCenter Administrator's Guide
- Overview of NetBackup OpsCenter
- About OpsCenter
- About OpsCenter components
- About starting the OpsCenter console
- About OpsCenter console components
- About the View pane
- Sizing the Content pane
- About using tables
- Installing OpsCenter
- About planning an OpsCenter installation
- About the OpsCenter licensing model
- Managed NetBackup master server considerations
- About designing your OpsCenter Server
- About planning an OpsCenter Agent deployment
- Installing OpsCenter on Windows and UNIX
- About OpsCenter upgrade on Windows and UNIX
- About post-installation tasks
- About uninstalling OpsCenter on Windows and UNIX
- About clustering OpsCenter
- About planning an OpsCenter installation
- Getting started with OpsCenter
- Administering OpsCenter
- About the services and processes used by OpsCenter
- OpsCenter server scripts on Windows and UNIX
- About OpsCenter database administration
- About backup and restore of OpsCenter and OpsCenter Analytics
- About communication ports and firewall considerations in OpsCenter
- About OpsCenter log files
- Understanding OpsCenter settings
- Setting user preferences
- About managing licenses
- Configuring the data purge period on the OpsCenter Server
- Configuring SMTP server settings for OpsCenter
- Adding host aliases in OpsCenter
- Merging objects (hosts) in OpsCenter
- Modifying tape library information in OpsCenter
- Copying a user profile in OpsCenter
- Setting report export location in OpsCenter
- About managing Object Types in OpsCenter
- About managing OpsCenter users
- About adding AD / LDAP user groups in OpsCenter
- About managing recipients in OpsCenter
- About managing cost analysis and chargeback for OpsCenter Analytics
- Understanding data collection
- About data collection in OpsCenter
- About managing OpsCenter Agents
- About managing OpsCenter Data Collectors
- About configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing master server details and data collection status
- Collecting data from PureDisk
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter views
- View filters in OpsCenter
- Monitoring NetBackup using OpsCenter
- Controlling the scope of Monitor views
- About monitoring NetBackup using the Overview tab
- About monitoring NetBackup jobs
- Monitor > Services view
- About monitoring Audit Trails
- Managing NetBackup using OpsCenter
- About managing alert policies
- About creating (or changing) an alert policy
- About managing NetBackup storage
- About managing NetBackup devices
- About Operational Restore and Guided Recovery operations
- About Operational Restores from OpsCenter
- About OpsCenter Guided Recovery
- Troubleshooting Guided Recovery
- About managing NetBackup Hosts
- About managing NetBackup Deployment Analysis
- Data compilation for the Capacity License report
- Generating a Capacity Licensing report
- Supporting Replication Director in OpsCenter
- Understanding and configuring OpsCenter alerts
- About using SNMP
- About using SNMP
- Reporting in OpsCenter
- About OpsCenter reports
- Report Templates in OpsCenter
- About managing reports in OpsCenter
- Creating a custom report in OpsCenter
- About managing My Reports
- About managing My Dashboard
- About managing reports folders in OpsCenter
- About managing report schedules in OpsCenter
- About managing time schedules in OpsCenter
- Appendix A. Additional information on PureDisk data collection
- Appendix B. Attributes of NetBackup data
- Appendix C. Man pages for CLIs
- Appendix D. Creating views using CSV, TSV, and XML files
- Appendix E. Error messages in OpsCenter
Upgrading OpsCenter on UNIX
Use the following procedure to upgrade to OpsCenter software on UNIX hosts.
Note:
Veritas recommends that you do not cancel or interrupt the installation process once it is started.
To upgrade OpsCenter Server on UNIX
- If you plan to upgrade your backup product and OpsCenter, ensure that you upgrade OpsCenter first. When upgrading OpsCenter, always upgrade the OpsCenter Server first followed by the Agent and then the View Builder.
- Open a UNIX console and log on as root on the target host.
- Mount the OpsCenter product DVD on the OpsCenter Server that you want to upgrade.
- Type the following command: ./install. Press Enter.
- The Welcome message is displayed. Press Enter to continue.
- The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter Server is already installed. The installer also examines the system for existing packages.
- The following prompt is displayed:
Where should the existing OpsCenter database and configuration files be backed up? An 'OpsCenterServer_backup' directory will be created within the directory that you specify to store these files. (/var/symantec/)
Type the directory name in which the existing OpsCenter database and configuration files can be saved and then press Enter.
To accept the default directory path (/var/symantec), press Enter.
- The installer displays a list of components that will be installed or upgraded like PBX, OpsCenter Server, OpsCenter user interface and so on. Review this list and press Enter to continue.
- The installer prompts you with the following question:
installOpsCenterServer is now ready to upgrade OPSCENTERSERVER. Are you sure you want to upgrade OPSCENTERSERVER? [y,n,q] (y)
Press Enter to continue OpsCenter upgrade.
- The installer prompts you with the following question:
Participate in the NetBackup Product Improvement program? [y,n,q] (y)
Press Enter if you want to participate in the NetBackup Product Improvement program or press n if you do not want to participate.
- The installer prompts you with the following question:
Do you want to import users from <remote AT host name> to OpsCenter AT?
Press Enter to import users from the earlier OpsCenter versions.
For more details, refer to the About Importing Authentication Settings section.
If the import fails, you need to reset password of all OpsCenter(vx) users.
- By default, in OpsCenter, the database is upgraded in the beginning. However, you can choose to first upgrade the OpsCenter software.
See About OpsCenter upgrade failure scenarios.
The database upgrade process starts. In this process, the OpsCenter data is migrated to the new OpsCenter database version. The database process may take time depending on your database size.
The following message is displayed:
The database upgrade is in progress. This may take some time based on the database size. You can see the progress and current status in
/var/tmp/(directory)/db/log/dbManager_<timestamp>_.log file.
After complete installation, the logs are copied to the following location:
/var/VRTS/install/logs/LogDirectory/db/log
LogDirectory is generated during the upgrade progress.
- The installer displays the OpsCenter packages that are installed. Depending on the installed packages, the following message may be displayed:
The following packages were found on the system. However the package versions are older than the ones required by OpsCenter. VRTSOpsCenterServer existing version was found on the system, but OpsCenter requires VRTSOpsCenterServer new version VRTSOpsCenterGUI existing version was found on the system, but OpsCenter requires VRTSOpsCenterGUI new version VRTSOpsCenterLegacyServer existing version was found on the system, but OpsCenter requires VRTSOpsCenterLegacyServer new version
The installer then uninstalls the older packages and installs new version of OpsCenter Server.
- OpsCenter Server is installed. Configuration changes are made to the system.
- All the OpsCenter processes are started. The following information is also displayed:
Web URL to access OpsCenter console
Location of install log and summary files.
Note:
After successful upgrade, OpsCenter database password is set to an auto-generated string, if the earlier password is still the default one, that is 'SQL'. Veritas recommends that you change the database password after the installation.
See Changing the OpsCenter database administrator password.
If you had changed the default password in the earlier version, you do not need to change it again. The installer retains the old password that you can use in the current version.