NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.3 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.3
- License file required for upgrade
- Windows primary server upgrades are slowed if a large number of files are in the installation directory
- About NetBackup database changes
- Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
- Java GUI and JRE installation optional for some computers
- Logging directory permissions require reset on rollback
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- External certificate authority certificates supported in NetBackup 8.2 and later
- About Veritas Usage Insights
- Best practices for Veritas Usage Insights
- Planning for an upgrade
- General upgrade planning information
- About planning a NetBackup 10.3 upgrade
- How to plan for an upgrade to NetBackup 10.3
- Legacy logging directory security update
- Unified logging security update
- Notifications, Messages, and Resiliency configuration information are not upgraded
- Known catalog backup limitation
- About security certificates for NetBackup hosts
- About automatic file changes from an upgrade
- Reduce the job database size before upgrade
- Known SUSE Linux primary server upgrade issue
- Performance and tuning considerations
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 10.3 support for Fibre Transport Media Server with RHEL 7.5 and later
- MSDP changes in NetBackup 8.1
- Potential required changes for NetApp clusters
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Upgrade issue with pre-8.1 clients and 8.1 or later media servers
- General upgrade planning information
- Primary server upgrade
- About primary server upgrades
- Preinstall procedure for upgrading to NetBackup 10.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.3
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.3
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup primary server web server user and group creation
- NetBackup database user
- Generate a certificate on the inactive nodes of a clustered primary server
- About the NetBackup Java Runtime Environment
- Add or Remove Java GUI and JRE after upgrade
- About the NetBackup web user interface
- About the NetBackup answer file
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Configure the NetBackup IT Analytics Data Collector manually for NetBackup
- Manually upgrading the NetBackup IT Analytics Data Collector
- Persistent Java Virtual Machine options
- About RBAC bootstrapping
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Upgrade requirements for UNIX and Linux
- Upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster upgrades
- Removing a clustered media server by migrating all data to a new media server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Upgrade failure rollback steps
- Size guidance for the NetBackup primary server and domain
Upgrading Linux server software to NetBackup 10.3
You should schedule your upgrade and reconfiguration for a time when backups do not run. However, the upgrade procedure instructs you to deactivate all policies to ensure that backups do not interfere with the upgrade. You can also temporarily modify policies so that backups do not run while you upgrade and reconfigure NetBackup.
To upgrade Linux server software to 10.3
- Log on as the root user on the server.
- If the NetBackup Administration Console is open, you must close it now.
- (Conditional) For clustered environments, perform the following tasks:
If necessary, edit the
bp.confand thevm.conffiles as follows:If a
REQUIRED_INTERFACEentry exists, replace it with aCLUSTER_NAMEentry. Otherwise, add a newCLUSTER_NAMEentry. This entry should be defined as the virtual server name.For a primary server, make sure that the first
SERVERentry matches theCLUSTER_NAMEentry for thebp.conffile.Take the NetBackup Server Resource (ServerResource) offline. Use the command shown:
/opt/VRTSvcs/bin/hares -offline ServerResource -sys $nodename
Freeze the NetBackup Group so that migrations do not occur while the inactive nodes are upgraded. Use the command shown:
/opt/VRTSvcs/bin/hagrp -freeze group -persistent
If you have a VCS cluster configured, you can freeze the NetBackup Group by using the Cluster Manager interface or the command line.
Before you proceed with a cluster upgrade, refer to the NetBackup Clustered Primary Server Administrator's Guide for other cluster upgrade requirements.
- NetBackup scripts that are not covered in Chapter 1 that you modified are removed when you run the upgrade script. More information about this topic is available.
See About automatic file changes from an upgrade.
Save any files that you have modified and want to keep.
- Navigate to the location where the installation images reside. Enter the command that is shown to start the upgrade script:
./install
- Follow the prompts in the installation script to install the NetBackup server binaries.
- (Conditional: For primary server only) If prompted, provide the name of the service user account you want to use to start most of the daemons. This prompt is shown if the installer cannot retrieve the service user value from the
bp.conffile or if the server user is root.Enter the name of the service user account to be used to start most of the daemons
Please note:
The service username cannot exceed 32 characters and can only contain English characters.
Veritas does not recommend that you use the root user as the service user.
You cannot use the nbwebsvc user as the service user.
The nbwebgrp group must be a secondary group of the service user.
Ownership of the
/usr/openvdirectory changes to the new service user account that you specified here.Using a service account involves a one-time conversion that may significantly increase the upgrade time based on your catalog size.
If you want to change the service user account after the installation, use the nbserviceusercmd --changeUser command.
For more details on the service user account, see: https://www.veritas.com/docs/100048220
- (Conditional: For primary server only) If prompted, provide the non-root database user name. The prompt is only shown if the service user is root.
ATTENTION! The NetBackup services currently use a root system account, which is not recommended. NetBackup is unable to use this account for the new scale-out database server process. Provide an alternative account name that meets the following criteria: - Root accounts are not allowed. - The username must be 1-31 characters. - The username must contain only English characters. - The nbwebsvc user should not be used as the scale-out database user.
- (Conditional: For primary servers only) If prompted, reply to the question regarding the infinite expiration conversion:
NetBackup 9.0 and later versions support the retention periods that extend beyond the year 2038. To ensure compatibility with previous NetBackup versions, all items with an infinite expiration date are updated to reflect the new infinite expiration date value. This conversion may extend the time that is required to complete the upgrade. Review the following article for more information: https://www.veritas.com/content/support/en_US/article.100048600 Date of collection: date_time NetBackup state: online|offline Records found: records Conversion time estimate: time (hh:mm) Please see the linked article to obtain a more accurate estimate of how long the conversion may take. Would you like to continue with the upgrade? [y,n]
- (Conditional: For media servers only) If your environment uses an external certificate authority, provide the external certificate authority information at the prompts shown:
Enter the certificate file path or q to skip security configuration: /usr/eca/cert_chain.pem Enter the trust store location or q to skip security configuration: /usr/eca/trusted/cacerts.pem Enter the private key path or q to skip security configuration: /usr/eca/private/key.pem Enter the passphrase file path or q to skip security configuration (default: NONE): /usr/eca/private/passphrase.txt
Note:
Be aware the passphrase file path is optional.
- (Conditional: For media servers only) When prompted, provide the required information for the CRL configuration:
Should a CRL be honored for the external certificate? 1) Use the CRL defined in the certificate. 2) Use the CRL from a file path. 3) Do not use a CRL. q) skip security configuration CRL option (1):
- (Conditional: For media servers only) If you specified Use the CRL from a file path, you must enter the path to the CRL location:
Enter the CRL location path or q to skip security configuration: /usr/eca/crl
- (Conditional: For media servers only) The installer echoes the configuration information you entered and attempts to retrieve details for the external certificate:
External CA values entered: Certificate file path: /usr/eca/cert_chain.pem Trust store file path: /usr/eca/trusted/cacerts.pem Private key file path: /usr/eca/private/key.pem Passphrase file path: /usr/eca/private/passphrase.txt CRL check level: Use the CRL from a file path. CRL location path: /usr/eca/crl Getting external CA certificate details Issued By : CN=IITFRMNUSINT,O=Veritas,OU=iitf Subject Name : CN=cuomovm04,O=Veritas,OU=iitf Expiry Date : Oct 31 17:25:59 2019 GMT SHA1 Fingerprint : 62:B2:C3:31:D5:95:15:85:9D:C9:AE:C6:EA:C2: DF:DF:6D:4B:92:5B Serial Number : 0x6c7fa2743072ec3eaae4fd60085d468464319a Certificate Path : /usr/eca/cert_chain.pem Validating host ECA certificate. NOTE: Depending on the network, this action may take a few minutes. To continue without setting up secure communication, press Ctrl+C. - (Conditional: For media servers only) If the external certificate enrollment pre-check finishes successfully, select 1 and press Enter to continue.
The external certificate enrollment pre-check is successful. The external certificate is valid for use with primary server name How do you want to proceed? 1) Continue the installation using this certificate. 2) Modify the external CA values entered. 3) Abort the installation. Default option (1):
- (Conditional: For media servers only) If the external certificate enrollment pre-check fails, select from the choices shown. The default is 2.
The external certificate enrollment pre-check failed. The external certificate is not valid for use with primary server name How do you want to proceed? 1) Continue the installation and set up external certificates later. 2) Modify the external CA values entered. 3) Abort the installation. Default option (2):
- (Conditional: For media servers only) When prompted, indicate how the upgrade should handle the Java GUI and JRE binaries.
The Java GUI and JRE packages are currently install_state on this host.
The Java GUI and JRE can be optionally included with NetBackup. The Java GUI and JRE enable the NetBackup Administration Console and the Backup, Archive and Restore (BAR) GUI. Choose an option from the list below.
1) Update the Java GUI and JRE.
2) Remove the Java GUI and JRE.
If you specify 1, the Java and JRE binaries are installed or upgraded, based on the status of the server. If you specify 2, the Java and JRE binaries are removed or excluded, based on the status of the server.
- (Conditional: Primary server upgrades from pre-NetBackup 10.3 to NetBackup 10.3 and later) When prompted, indicate how the upgrade should handle license information.
Are the license files downloaded from the Veritas licensing portal? (y/n):
If you have not downloaded your license from the Veritas Entitlement Management System portal, answer n. You are then prompted to use a temporary production license for upgrades. The installer cannot proceed without a license or a temporary production license, and exits gracefully. More information is available: https://www.veritas.com/support/en_US/article.100058779
If you have already downloaded the license, then answer y. You are then prompted to provide the file path for the license you want to use. When you provide a license file path, NetBackup validates the file exists, is a valid file for NetBackup, the contents were not modified, it is not expired etc. After NetBackup determines the license is valid, the installer shows the license details and prompts the user to add this license. If user answers y the license is added. In case of invalid license, installer provides reason why the file is invalid and prompts you to provide new license file path.
Upgrades from versions earlier than NetBackup 8.1.2 only support the production licenses that are downloaded from VEMS or the evaluation license. You cannot use the temporary production license when you upgrade from a NetBackup version earlier than 8.1.2.
You can also install additional licenses.
- When the script finishes, the binaries are successfully installed.
Proceed to the post-installation procedure.
More information is available.