NetBackup™ Installation Guide
- Preparing for installation
- General installation information
- Available NetBackup installation methods
- About compatibility between NetBackup versions
- About NetBackup software availability
- Required libraries missing from some Linux distributions
- How to install NetBackup
- Creating the user account to support the NetBackup web server
- About storage device configuration
- About security certificates for NetBackup hosts
- Environment variable for certificate key size
- Restrictions on the NetBackup installation directory
- NetBackup database is not supported on the btrfs file system
- Installation operational notes and limitations
- Windows compiler and security requirements for NetBackup 10.4 and later installation
- Java GUI and JRE installation optional for some computers
- Enable 8dot3 name file setting for the NetBackup primary servers
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- Host ID-based certificate is not deployed during installation on 8.1 media server or client host with dual stack configuration
- External certificate authority certificates supported in NetBackup 8.2 and later
- SCCM and Chef deployment tools and documentation now available
- Known SUSE Linux primary server install issue
- Performance and tuning considerations
- SORT information
- Veritas NetInsights Console information
- General installation information
- NetBackup licenses
- Installing server software on UNIX systems
- Installation requirements for UNIX and Linux
- Do not mix non-English versions of Windows and UNIX platforms unless primary 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 Linux clustered environments
- How the installation script works
- Installing NetBackup primary server software on Linux
- Installing NetBackup media server software on Linux
- About pushing client software from a primary server to clients
- Installation requirements for UNIX and Linux
- Installing server software on Windows systems
- Installation requirements for Windows and Windows clusters
- Requirements for Windows cluster installations
- 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 web user interface
- 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 and Linux
- Configuring NetBackup
- Removing NetBackup server and client software
- About NetBackup server software removal on Linux 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
- 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 primary server
- NetBackup database user
- About the NetBackup answer file
- About the NetBackup IT Analytics Data Collector
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Manually configure the NetBackup IT Analytics Data Collector
- Persistent Java Virtual Machine options
- About RBAC bootstrapping
- NetBackup primary server web server user and group creation
- About the NetBackup Java Runtime Environment
- Add or Remove Java GUI and JRE after install
- Using NetApp disk arrays with Replication Director
- Security updates to the NetBackup database
- Size guidance for the NetBackup primary server and domain
Generate a certificate on the inactive nodes of a clustered primary server
After finishing a clustered primary 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 primary 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.
Linux: /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 primary server nodes in the NetBackup Security and Encryption Guide.