Veritas NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 8.1.2 Upgrade Guide
- About changes in NetBackup 8.1.2
- Veritas Smart Meter introduced
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- HP-UX and AIX support change
- Newer Red Hat Linux compilers used with NetBackup 8.1.2
- VxUpdate replaces update_clients script in NetBackup 8.1.2
- Port 443 required for NetBackup web user interface
- About MSDP
- Performance issues with upgrades to NetBackup 8.1.2 from NetBackup 8.0 and earlier
- About certificate requirements for NetBackup 8.1
- SCCM and Chef deployment tools and documentation now available
- Potential required changes for NetApp clusters
- About automatic file changes from an upgrade
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Known catalog backup limitation
- Available NetBackup upgrade methods
- About Veritas Services and Operations Readiness Tools
- Recommended SORT procedures for new installations
- Recommended SORT procedures for upgrades
- About the NetBackup preinstall checker
- Planning for an upgrade
- About planning a NetBackup 8.1.2 upgrade
- How to plan for an upgrade to NetBackup 8.1.2
- About Veritas Smart Meter
- Best practices for Veritas Smart Meter
- Creating the user account to support the NetBackup web server
- About NetBackup 8.1.2 support for Fibre Transport Media Server with RHEL 7.5
- MSDP changes in NetBackup 8.1
- About security certificates for NetBackup hosts
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.1.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX/Linux server software to NetBackup 8.1.2
- Post-install procedure for upgrading to NetBackup 8.1.2
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup master server web server user and group creation
- Generate a certificate on the inactive nodes of a clustered master server
- About the NetBackup Java Runtime Environment
- About the NetBackup web user interface
- About the NetBackup answer file
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.2
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Installation and upgrade requirements for UNIX and Linux
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Upgrading clients after servers are upgraded
- Install and upgrade of the UNIX and Linux client binaries with native installers
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
- Post upgrade procedures for Amazon cloud storage servers
Generate a certificate on the inactive nodes of a clustered master server
After finishing a clustered master server installation or upgrade, you must generate a certificate on all inactive nodes. This procedure is required for backups and restores of the inactive node of the cluster to succeed.
Generating the certificate on the inactive nodes in a clustered master server
Note:
Unless otherwise indicated, all commands are issued from the inactive node
- (Conditional) Add all inactive nodes to the cluster.
If all the nodes of the cluster are not currently part of the cluster, start by adding them to the cluster. Please consult with your operating system cluster instructions for assistance with this process.
- Run the nbcertcmd command to store the Certificate Authority certificate on the inactive node.
UNIX: /usr/openv/netbackup/bin/nbcertcmd -getCACertificate
Windows: install_path\NetBackup\bin\nbcertcmd -getCACertificate
- Run the nbcertcmd command to generate the host certificate on the inactive node.
nbcertcmd -getCertificate
- (Conditional) If the nbcertcmd -getCertificate command fails with an error message indicating that a token is needed, you need a token from the Certificate Authority. Use the steps that are shown to get and correctly use the token.
On the active node, use the bpnbat command as shown to authorize the necessary changes. When you are prompted for the authentication broker, enter the virtual server name, not the local node name.
bpnbat -login -loginType WEB
On the active node, use the nbcertcmd command to create a token.
nbcertcmd -createToken -name token_name
The token name is not important to this procedure. When the command runs, it displays the token string value. Note this value as it is necessary for the next command.
On the inactive node, use the authorization token with the nbcertcmd command to store the host certificate.
nbcertcmd -getCertificate -token
This command prompts you for the token string value. Enter the token string from the nbcertcmd -createToken command.
Additional information about certificates is available. Please see the section on deploying certificates on master server nodes in the Veritas NetBackup Security and Encryption Guide.