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 binaries installed on primary and media servers
- 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
- Minimum operating system versions
- Client push staging area no longer populated
- Windows compiler and security requirements for NetBackup 10.5 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
Installation requirements for Windows and Windows clusters
Table: 10.5 requirements for Windows and Windows clusters describes the requirements to prepare your Windows systems for 10.5 installation. Use this table as a checklist to address each item.
For the most up-to-date information about installation requirements, Veritas recommends use of the SORT website. More information about SORT is available.
See About Veritas Services and Operations Readiness Tools.
Caution:
Veritas supports moving the 10.5 catalog with the nbdb_move command to a non-default location on a Windows cluster after installation or upgrade. Before any upgrades, however, you must move the 10.5 catalog back to the default location for the upgrade to succeed. Do not attempt a 10.5 upgrade if the catalog is not in the default location. You primary server is rendered unusable if you fail to move the database back to the default location before upgrade. More information about the nbdb_move is available.
Table: 10.5 requirements for Windows and Windows clusters
Check | Requirement | Details |
|---|---|---|
Operating system |
| |
Memory | Use the information that is shown to correctly size your server:
| |
Disk space |
Note: The value for disk space is for initial installation only. The 10.5 catalog requires considerably more space once the primary server is placed in a production environment. | |
General requirements | Make sure that you have all of the following items:
| |
Remote and cluster installations | In addition to all previously stated installation requirements, the following guidelines apply to remote installations and cluster installations:
More information about cluster requirements is available. | |
Remote Administration Console host names | You must provide the names of the Remote Administration Console hosts during primary server installation. | |
10.5 communication |
Make sure that your network configuration allows all servers and clients to recognize and communicate with one another. Generally, if you can reach the clients from a server by using the ping command, the setup works with 10.5.
| |
CIFS-mounted file systems |
Veritas does not support installation of 10.5 in a CIFS-mounted directory. File locking in CIFS-mounted file systems can be unreliable. | |
Storage devices | Devices such as robots and standalone tape drives must be installed according to the manufacturers' instructions and recognized by the Windows software. | |
Server names | When you are prompted for server names, always enter the appropriate host names. Do not enter IP addresses. | |
Mixed versions | Make sure to install 10.5 servers with a release level that is at least equal to the latest client version that you plan to use. Earlier versions of server software can encounter problems with later versions of client software. | |
Other backup software | Remove any other vendor's backup software currently configured on your system. The backup software of another vendor can negatively affect how 10.5 installs and functions. | |
Web Services | Beginning with NetBackup 8.0, the NetBackup primary server includes a configured Tomcat web server to support critical backup operations. This web server operates under user account elements with limited privileges. These user account elements must be available on each primary server (or each node of a clustered primary server). More information is available: See NetBackup primary server web server user and group creation. Note: Veritas recommends that you save the details of the user account that you use for the 10.5 Web Services. A primary server recovery requires the same 10.5 Web Services user account and credentials that were used when the 10.5 catalog was backed up. Note: If the 10.5 PBX is running in secure mode, please add the web service user as authorized user in PBX. More information about determining PBX mode and how to correctly add users is available. | |
CA Certificate fingerprint |
(Conditional) For media servers and clients only: If you use a NetBackup Certificate Authority, you must know the CA Certificate fingerprint of the primary server at time of installation. This requirement only applies if you use a NetBackup Certificate Authority. More information is available about the details on the CA Certificate fingerprint and its role in generation of security certificates. | |
Authorization Token |
(Conditional) For media servers and clients only: In some cases, the installer requires an authorization token to successfully deploy security certificates. More information is available about the details on authorization tokens and their role in generation of security certificates. In some cases, if you use a NetBackup Certificate Authority, the installer requires an authorization token to successfully deploy security certificates. More information is available about the details on authorization tokens and their role in generation of security certificates. | |
External certificate authority | For primary servers (including cluster): The configuration of an external certificate authority is a post-installation activity. For media servers and clients: You can configure the ECA during the install procedure or after the installation completes. More information about post-installation configuration is available: https://www.veritas.com/support/en_US/article.100044300 For more information, see the 10.5 Security and Encryption Guide and refer to the chapter on external CA and external certificates. |