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
Installation and upgrade requirements for Windows and Windows clusters
Table: NetBackup installation and upgrade requirements for Windows and Windows clusters describes the requirements to prepare your Windows systems for NetBackup 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 NetBackup catalog to a non-default location on a Windows cluster after installation or upgrade. Before any upgrades, however, you must move the NetBackup catalog back to the default location for the upgrade to succeed. Do not attempt a NetBackup upgrade if the catalog is not in the default location. You master server is rendered unusable if you fail to move the database back to the default location before upgrade. More information is available.
Table: NetBackup installation and upgrade requirements for Windows and Windows clusters
Check | Requirement | Details |
|---|---|---|
Operating system |
| |
Memory |
For additional information about memory requirements, refer to the NetBackup Backup Planning and Performance Tuning Guide. | |
Disk space |
Note: The value for disk space is for initial installation only. The NetBackup catalog requires considerably more space once the master server is placed in a production environment. For additional information on sizing requirements for the NetBackup catalog, refer to the NetBackup Backup Planning and Performance Tuning Guide. | |
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. Veritas NetBackup Clustered Master Server Administrator's Guide | |
Remote Administration Console host names | You must provide the names of the Remote Administration Console hosts during master server installation. | |
NetBackup 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 NetBackup.
| |
CIFS-mounted file systems |
Veritas does not support installation of NetBackup 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 NetBackup 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. | |
Installations on Windows 2008/2008 R2 Server Core, 2012/2012 R2 Server Core/Windows 2016 | You can only install NetBackup on these computers with the silent installation method. See Installing NetBackup servers silently on Windows systems. | |
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 NetBackup installs and functions. | |
Web Services | Beginning with NetBackup 8.0, the NetBackup master 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 master server (or each node of a clustered master server). More information is available: See NetBackup master server web server user and group creation. Note: Veritas recommends that you save the details of the user account that you use for the NetBackup Web Services. A master server recovery requires the same NetBackup Web Services user account and credentials that were used when the NetBackup catalog was backed up. Note: If the NetBackup 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: You must know the CA Certificate fingerprint of the master server at time of installation. 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. |
See Installation and upgrade requirements for UNIX and Linux.