Veritas NetBackup™ Upgrade Guide
- Introduction
- 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
Upgrade requirements for UNIX and Linux
Table: NetBackup requirements for UNIX and Linux describes the requirements to prepare your UNIX and Linux systems for NetBackup upgrade. 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.
Table: NetBackup requirements for UNIX and Linux
Check | Requirement | Details |
---|---|---|
Operating System |
| |
Memory |
| |
Disk space |
If space is an issue, you can install NetBackup on an alternate file system. The installation lets you select an alternate install location, and creates the appropriate link from /usr/openv. 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. | |
General requirements |
| |
Clustered systems |
More information about cluster requirements is available. | |
NFS compatibility | Veritas does not support installation of NetBackup in an NFS-mounted directory. File locking in NFS-mounted file systems can be unreliable. | |
Kernel reconfiguration | For some peripherals and platforms, kernel reconfiguration is required. For more details, see the NetBackup Device Configuration Guide. | |
Before NetBackup installation, confirm the system libraries that are shown are present. If any library is not present, install the one provided by your operating system.
| ||
For Red Hat Linux, NetBackup requires server networking. | ||
Other backup software | Veritas recommends that you remove any other vendor backup software currently configured on your system before you install this product. Other vendor backup software 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). You must create these required account elements before installation. 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. By default, the UNIX installation script attempts to associate the web server with user account nbwebsvc and group account nbwebgrp. You can override these default values with the NetBackup installation answer file. You must populate the NetBackup installation answer file on the target host before you start the UNIX installation script. Populate the NetBackup installation answer file with custom web server account names as shown.
| |
Customer Registration Key for Veritas Smart Meter | Beginning with NetBackup 8.1.2, you must specify a Customer Registration Key for Veritas Smart Meter. More information about Veritas Smart Meter is available: See About Veritas Smart Meter. During install and upgrade to NetBackup 8.1.2, please allow the installer to copy the Note: Be aware that NetBackup does not support the short file name format (8.3 format) for the customer registration key file name. |