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 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 10.4 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
About the NetBackup preinstall checker
The NetBackup installer includes a preinstall checker. This feature helps to determine if your computer is ready for a successful installation or upgrade.
The check runs automatically when you start an installation. The results of the check are shown at the following point:
UNIX or Linux install script
After you accept the end user license agreement but before the installation starts.
Windows installation wizard
On the Ready to Install the Program screen, where the Installation Summary appears.
Additionally, you can run the preinstall checker through VxUpdate. See NetBackup Upgrade Guide for more information on using VxUpdate to run the check.
NetBackup uses a preinstallation program that does a check at the beginning of installations or upgrades. The check looks for any known problems that you can eliminate so the operation can succeed. The checks that are performed are developed from customer input on the previous problems that were encountered during installations and upgrades. Veritas can update the checker whenever new customer feedback is received. Refreshes are not dependent on a NetBackup release. If your server can connect to telemetry.veritas.com, NetBackup automatically updates the checker with the latest version when the installation or the upgrade starts.
One of the tests that is performed is a comparison of the locally installed Emergency Engineering Binary (EEB) updates with the fixes included with the version of NetBackup being installed. If any of the preinstall tests fail, a message appears to indicate what type of action is required.
Some test failures are considered minor and let you continue with the installation or the upgrade. Critical test failures prevent the installation or the upgrade from happening. The output informs you that other action must be taken before you can proceed safely with the installation or the upgrade.
The preinstall check results are stored in the following locations:
Linux
In the installation trace file in the following path:
/usr/openv/tmpWindows
In the following directory:
%ALLUSERSPROFILE%\Veritas\NetBackup\InstallSummary\