Veritas NetBackup™ Upgrade Guide
- About changes in NetBackup 9.0
- Planning for an upgrade
- General upgrade planning information
- About upgrade tools
- Upgrade operational notes and limitations
- Master server upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
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.
Veritas supports moving the NetBackup 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 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 about the nbdb_move is available.
Table: NetBackup installation and upgrade requirements for Windows and Windows clusters
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.
Make sure that you have all of the following items:
To install NetBackup on Windows 2012 R2, Windows 2012 UAC-enabled, and Windows Server 2016 environments, you must log on as the official administrator. Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. To allow users in the Administrators Group to install NetBackup, disable UAC.
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 master server installation.
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.
Devices such as robots and standalone tape drives must be installed according to the manufacturers' instructions and recognized by the Windows software.
When you are prompted for server names, always enter the appropriate host names. Do not enter IP addresses.
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 2012/2012 R2 Server Core/Windows 2016
You can only install NetBackup on these computers with the silent installation method.
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.
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:
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.
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:
If you use a NetBackup Certificate Authority, you must know the CA Certificate fingerprint of the master 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.
(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 master 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:
Customer Registration Key for Veritas Usage Insights
Beginning with NetBackup 8.1.2, you must specify a Customer Registration Key for Veritas Usage Insights. More information about Veritas Usage Insights is available:
During install and upgrade to NetBackup 8.1.2, please allow the installer to copy the
Be aware that NetBackup does not support the short file name format (8.3 format) for the customer registration key file name.