NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.3 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.3
- License file required for upgrade
- Windows primary server upgrades are slowed if a large number of files are in the installation directory
- About NetBackup database changes
- Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
- Java GUI and JRE installation optional for some computers
- Logging directory permissions require reset on rollback
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- External certificate authority certificates supported in NetBackup 8.2 and later
- About Veritas Usage Insights
- Best practices for Veritas Usage Insights
- Planning for an upgrade
- General upgrade planning information
- About planning a NetBackup 10.3 upgrade
- How to plan for an upgrade to NetBackup 10.3
- Legacy logging directory security update
- Unified logging security update
- Notifications, Messages, and Resiliency configuration information are not upgraded
- Known catalog backup limitation
- About security certificates for NetBackup hosts
- About automatic file changes from an upgrade
- Reduce the job database size before upgrade
- Known SUSE Linux primary server upgrade issue
- Performance and tuning considerations
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 10.3 support for Fibre Transport Media Server with RHEL 7.5 and later
- MSDP changes in NetBackup 8.1
- Potential required changes for NetApp clusters
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Upgrade issue with pre-8.1 clients and 8.1 or later media servers
- General upgrade planning information
- Primary server upgrade
- About primary server upgrades
- Preinstall procedure for upgrading to NetBackup 10.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.3
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.3
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup primary server web server user and group creation
- NetBackup database user
- Generate a certificate on the inactive nodes of a clustered primary server
- About the NetBackup Java Runtime Environment
- Add or Remove Java GUI and JRE after upgrade
- About the NetBackup web user interface
- About the NetBackup answer file
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Configure the NetBackup IT Analytics Data Collector manually for NetBackup
- Manually upgrading the NetBackup IT Analytics Data Collector
- Persistent Java Virtual Machine options
- About RBAC bootstrapping
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Upgrade requirements for UNIX and Linux
- Upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster upgrades
- Removing a clustered media server by migrating all data to a new media server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Upgrade failure rollback steps
- Size guidance for the NetBackup primary server and domain
Configure the NetBackup IT Analytics Data Collector manually for NetBackup
The primary server installation deploys the NetBackup IT Analytics Data Collector binaries automatically as part of a successful NetBackup installation. The binaries are installed to install_path\Veritas\ (Windows) or /usr/openv/analyticscollector (Linux). This section details the steps that are required to manually configure the Data Collector.
Keep the following details handy when you configure the Data Collector:
Name of the Data Collector (as configured on the Veritas Alta or NetBackup IT Analytics Portal).
Passcode of the Data Collector (as configured on the Veritas Alta or NetBackup IT Analytics Portal).
Data receiver URL (generated when you create the Data Collector on the Veritas Alta or NetBackup IT Analytics Portal). Ensure the NetBackup primary server can resolve the host name of the Data Receiver URL.
Key file path (generated when you create the Data Collector on the Veritas Alta or NetBackup IT Analytics Portal and copied to the NetBackup primary server).
See the Add/Edit Data Collectors section in the NetBackup IT Analytics User Guide for more information.
To configure the Data Collector manually on Windows:
- Create a response file as a batch script responsefile.cmd with the contents shown. These are the responses to the user input required to configure the Data Collector.
SET DATACOLLECTOR_NAME=name_of_the_data_collector SET DATACOLLECTOR_PASSCODE=passcode_for_the_data_collector SET DATARECEIVER_URL=data_receiver_URL SET DATACOLLECTOR_KEY_FILE_PATH=path_to_the_key_file SET HTTP_PROXY_CONF=N SET PROXY_HTTP_URL= SET PROXY_HTTP_PORT= SET PROXY_HTTPS_URL= SET PROXY_HTTPS_PORT= SET PROXY_USERID= SET PROXY_PASSWORD= SET PROXY_NOT_FOR=
- Update the value for each field with appropriate data. A sample response file is also available in the installer media in
x64\ITA_DC\responsefile.cmd. - Run the command shown:
"C:\ProgramData\Veritas\NetBackup IT Analytics\DC\configure.cmd" \RESPFILE:response_file_path \INSTALL_TYPE:CONFIG
- Validate the Data Collector integration with NetBackup IT Analytics by going to
C:\Program Files\Veritas\analyticscollector\mbs\bin\and running this command:checkinstall.bat
If the Data Collector is configured with the Portal, the response is displayed as SUCCESSFUL.
Note:
If there is a version mismatch of
aptare.jarbetween the Data Collector and the portal, execution of the checkinstall.bat command starts an auto-update of the Data Collector.
To configure the Data Collector manually on Linux:
- Create a response file with the contents shown. These are the responses to the user input required to configure the Data Collector:
COLLECTOR_NAME=name_of_the_data_collector COLLECTOR_PASSCODE=passcode_for_the_data_collector DR_URL=data_receiver_URL COLLECTOR_KEY_PATH=path_to_the_key_file HTTP_PROXY_CONF=N HTTP_PROXY_ADDRESS= HTTP_PROXY_PORT= HTTPS_PROXY_ADDRESS= HTTPS_PROXY_PORT= PROXY_USERNAME= PROXY_PASSWORD= PROXY_EXCLUDE=
- Update the value for each field with appropriate data.
A sample response file is available on the install media and from
/usr/openv/analyticscollector/installer/responsefile.sampleon the primary server. - Run the command:
/usr/openv/analyticscollector/installer/dc_installer.sh -c responsefile_path
- Validate the Data Collector integration with NetBackup IT Analytics by navigating to
/usr/openv/analyticscollector/mbs/bin/and running ./checkinstall.shIf the Data Collector is able to communicate with the NetBackup IT Analytics Portal, the response is displayed as SUCCESSFUL.
Note:
If there is a version mismatch of
aptare.jarbetween the Data Collector and the portal, execution of the checkinstall.sh command starts an auto-update of the Data Collector.
On Linux:
To start the Data Collector processes, run:
/usr/openv/analyticscollector/mbs/bin/aptare_agent start
To stop the Data Collector processes, run:
/usr/openv/analyticscollector/mbs/bin/aptare_agent stop
To get the status of the Data Collector processes, run:
/usr/openv/analyticscollector/mbs/bin/aptare_agent status
On Windows: Review the status of Aptare Agent, Aptare Kafka, and Aptare Zookeeper services on the Windows service panel.
Note:
If the Data Collector is configured with an on-premises NetBackup IT Analytics Portal, then to edit any of the Data Collector properties on the Portal, refer to Edit NetBackup IT Analytics Data Collector credentials section in the NetBackup IT Analytics User Guide.