Veritas NetBackup™ Installation Guide
- Preparing for installation
- General installation information
- Available NetBackup installation methods
- About compatibility between NetBackup versions
- About NetBackup software availability
- 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 9.1 and later installation and upgrade
- Java GUI and JRE installation optional for some computers
- Enable 8dot3 name file setting for NetBackup master servers that support NAT
- 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
- NetBackup 8.2 and later RHEL 8 installation issue
- NetBackup 8.2 and later SUSE 15 installation issue
- External certificate authority certificates supported in NetBackup 8.2 and later
- SCCM and Chef deployment tools and documentation now available
- Known SUSE Linux master server install issue
- 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 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 UNIX clustered environments
- How the installation script works
- 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 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 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
- 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
- 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
- Persistent Java Virtual Machine options
- About RBAC bootstrapping
- NetBackup master 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 master server and domain
- Index
Silently installing NetBackup media server software on UNIX and Linux
You can install NetBackup UNIX and Linux media servers with native installers. You can use either the NetBackup install script or your preferred installer method.
For Linux: rpm, yum, etc.
For Solaris: pkginfo, pkgadd
A successful installation or upgrade is recorded in the /usr/openv/pack/install.history file.
To install the UNIX or Linux media server binaries using native installers:
- Please create the NetBackup installation answer file (
NBInstallAnswer.conf) in the media server/tmpdirectory. More information about the answer file and its contents is available. - Populate
NBInstallAnswer.confwith the following required information:SERVER=master_server_name CLIENT_NAME=media_server_name MACHINE_ROLE=MEDIA LICENSE=license_key
Be aware you can use CLIENT_NAME=XLOCALHOSTX instead of stating the media server name explicitly.
- (Conditional) If your environment uses a NetBackup Certificate Authority, populate
NBInstallAnswer.confwith the following required information:CA_CERTIFICATE_FINGERPRINT=fingerprint
Example (the fingerprint value is wrapped for readability):
CA_CERTIFICATE_FINGERPRINT=01:23:45:67:89:AB:CD:EF:01:23:45:67: 89:AB:CD:EF:01:23:45:67
Depending on the security configuration in your NetBackup environment, you may need to add the AUTHORIZATION_TOKEN option to the answer file. Additional information about the AUTHORIZATION_TOKEN option is available.
- (Conditional) If your environment uses an external certificate authority, populate
NBInstallAnswer.confwith the following required information:ECA_CERT_PATH
Use this field to specify the path and the file name of the external certificate file. This field is required to set up an external certificate from a file.
ECA_TRUST_STORE_PATH
Use this field to specify the path and the file name of the file representing the trust store location. This field is required to set up an external certificate from a file.
ECA_PRIVATE_KEY_PATH
Use this field to specify the path and the file name of the file representing the private key. This field is required to set up an external certificate from a file.
ECA_KEY_PASSPHRASEFILE
Use this field to specify the path and the file name of the file that contains the passphrase to access the keystore. This field is optional and applies only when setting up an external certificate from a file.
ECA_CRL_CHECK_LEVEL
Use this field to specify the CRL mode. This field is required. Supported values are:
USE_CDP: Use the CRL defined in the certificate.
USE_PATH: Use the CRL at the path that is specified in ECA_CRL_PATH.
DISABLED: Do not use a CRL.
SKIP: Used to skip setting up the certificate authority. To skip the ECA configuration, you must set all required ECA_ values to SKIP. Be aware that if you continue with the installation without a certificate authority, the backups and restores fail.
ECA_CRL_PATH
Use this field to specify the path to the CRL associated with the external CA certificate. This field is required only when ECA_CRL_CHECK_LEVEL is set to USE_PATH. If not applicable, leave this field empty.
- Additionally, you can add the optional parameters shown to the
NBInstallAnswer.conffile.INSTALL_PATH
Additional LICENSE entries
Additional SERVER entries
More information about each option is available.
- Download the server package that matches your server platform to a system with sufficient space. Then extract the required server package.
Extract the contents of the server package file. Example:
For Linux Red Hat:
tar -xzvf NetBackup_9.1_LinuxR_x86_64.tar.gz
For Linux SuSE:
tar -xzvf NetBackup_9.1_LinuxS_x86_64.tar.gz
For Solaris SPARC:
tar -xzvf NetBackup_9.1_Solaris_Sparc64.tar.gzFor Solaris x86:
tar -xzvf NetBackup_9.1_Solaris_x86.tar.gz
- Change to the directory for your desired operating system and copy server files to the media server.
Operating system directory:
For Linux Red Hat:
NetBackup_9.1_LinuxR_x86_64/linuxR_x86/anbFor Linux SuSE:
NetBackup_9.1_LinuxS_x86_64/linuxS_x86/anbFor Solaris SPARC:
NetBackup_9.1_Solaris_Sparc64/solaris/anbFor Solaris x86
NetBackup_9.1_Solaris_x86/solaris_x86/anb
Copy server files to the computer to be installed
Linux:
VRTSnetbp.rpmandVRTSpddes.rpmLinux Red Hat:
VRTSpddei.rpmSolaris:
VRTSnetbp.pkgandVRTSpddes.pkg
- Extract the client binaries and copy them to the media server:
Extract the client binaries:
tar -xzvf client_dist.tar.gz
Change directory to your desired operating system:
Red Hat:
openv/netbackup/client/Linux/RedHat2.6.32SuSE:
openv/netbackup/client/Linux/SuSE3.0.76SPARC:
openv/netbackup/client/Solaris/Solaris10Solaris_x86:
openv/netbackup/client/Solaris/Solaris_x86
Copy the files that are shown to the media server.
Note:
The installation of the Java GUI and the JRE is optional. If you do not want them installed, omit the copy and the install of the
VRTSnbjavaandVRTSnbjrepackages.Linux
VRTSnbpck.rpm VRTSpbx.rpm VRTSnbclt.rpm VRTSnbjre.rpm VRTSnbjava.rpm VRTSpddea.rpm VRTSnbcfg.rpm
Solaris
.pkg_defaults VRTSnbpck.pkg.gz VRTSpbx.pkg.gz VRTSnbclt.pkg.gz VRTSnbjre.pkg.gz VRTSnbjava.pkg.gz VRTSpddea.pkg.gz VRTSnbcfg.pkg.gz
Note:
The Solaris client binaries include a hidden administration file called .pkg_defaults. This administration file contains default installation actions.
- (Conditional) For Solaris, extract the compressed package files with the command shown:
gunzip VRTS*.*
This action extracts all the package files as shown:
VRTSnbpck.pkg VRTSpbx.pkg VRTSnbclt.pkg VRTSnbjre.pkg VRTSnbjava.pkg VRTSpddea.pkg VRTSnbcfg.pkg
- Install the files in the order that is shown with the commands shown:
Linux
rpm - U VRTSnbpck.rpm rpm - U VRTSpbx.rpm rpm - U VRTSnbclt.rpm rpm - U VRTSnbjre.rpm rpm - U VRTSnbjava.rpm rpm - U VRTSpddea.rpm rpm - U VRTSpddes.rpm rpm - U VRTSpddei.rpm rpm - U VRTSnbcfg.rpm rpm - U VRTSnetbp.rpm
Note that
VRTSpddei.rpmis for Linux Red Hat only.Solaris
Use the pkgadd -a admin -d device [pkgid] command as shown to install the files:
pkgadd -a .pkg_defaults -d VRTSnbpck.pkg VRTSnbpck pkgadd -a .pkg_defaults -d VRTSpbx.pkg VRTSpbx pkgadd -a .pkg_defaults -d VRTSnbclt.pkg VRTSnbclt pkgadd -a .pkg_defaults -d VRTSnbjre.pkg VRTSnbjre pkgadd -a .pkg_defaults -d VRTSnbjava.pkg VRTSnbjava pkgadd -a .pkg_defaults -d VRTSpddea.pkg VRTSpddea pkgadd -a .pkg_defaults -d VRTSpddes.pkg VRTSpddes pkgadd -a .pkg_defaults -d VRTSnbcfg.pkg VRTSnbcfg pkgadd -a .pkg_defaults -d VVRTSnetbp.pkg VRTSnetbp
The -a option defines a specific admin (.pkg_defaults) to use in place of the default administration file. The admin file contains default installation actions.
The -d device option specifies the source of the software packages. A device can be the path to a device, a directory, or a spool directory.
Use the pkgid parameter to specify a name for the package being installed. This parameter is optional.
- If you decide to install the Java GUI or the JRE after the installation completes, additional information is available.