Veritas NetBackup™ Installation Guide
- Preparing for installation
- Restrictions on the NetBackup installation directory
- Creating the user account to support the NetBackup web server
- About compatibility between NetBackup versions
- About Veritas Services and Operations Readiness Tools
- Recommended SORT procedures for new installations
- Recommended SORT procedures for upgrades
- About NetBackup software availability
- About storage device configuration
- How to install NetBackup
- About security certificates for NetBackup hosts
- SCCM and Chef deployment tools and documentation now available
- Support is discontinued for push installation of a master server
- NetBackup licenses
- Installing server software on UNIX systems
- Installation and upgrade requirements for UNIX and Linux
- Do not mix non-English versions of Windows and UNIX platforms unless master and media servers are NetBackup appliances
- NetBackup installations on environments that run different versions of UNIX-based operating systems
- Special installation guidelines for Solaris systems
- Special installation guidelines for HP-UX systems
- Special guidelines for AIX master servers
- Special installation guidelines for UNIX clustered environments
- How the installation script works
- About mounting the NetBackup software media
- Installing NetBackup master server software on UNIX
- Installing NetBackup media server software on UNIX
- About pushing client software from a master server to clients
- Installation and upgrade requirements for UNIX and Linux
- Installing server software on Windows systems
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Performing local, remote, or clustered server installation on Windows systems
- Post-installation tasks for NetBackup cluster environments
- Verifying Windows cluster installations or upgrades
- Installing NetBackup servers silently on Windows systems
- About the administrative interfaces
- About the NetBackup Administration Console
- Installing the NetBackup Administration Console
- Installing multiple versions of the NetBackup Administration Console on Windows
- Removing earlier versions of the NetBackup Administration Console on Windows
- About the NetBackup Remote Administration Console
- Installing the NetBackup Remote Administration Console
- Installing NetBackup client software
- About NetBackup client installation
- About NetBackup client installation on Windows
- About NetBackup client installation on UNIX/Linux
- About UNIX/Linux client installation methods
- Installing UNIX clients locally
- Install and upgrade of the UNIX and Linux client binaries with native installers
- About remote installation methods for UNIX/Linux clients
- Adding a UNIX/Linux client after initial server installation
- Upgrading clients after servers are upgraded
- Configuring NetBackup
- Upgrading NetBackup software
- Removing NetBackup server and client software
- About NetBackup server software removal on UNIX systems
- About NetBackup client software removal on UNIX and Linux systems
- Removing NetBackup from UNIX and Linux servers and clients
- About NetBackup server software removal on Windows systems
- Removing NetBackup server and client software from Windows servers, clusters, and clients
- Removing NetBackup LiveUpdate from Windows systems
- About removal of the Java Console state data from Windows servers and Windows clients
- Removing a clustered media server by migrating all data to a new media server
- Reference
- Generate a certificate on the inactive nodes of a clustered master server
- About the NetBackup answer file
- NetBackup master server web server user and group creation
- About the NetBackup Java Runtime Environment
- Using NetApp disk arrays with Replication Director
- Security updates to the NetBackup database
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.