NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.4 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.4
- 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
- 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.4 upgrade
- How to plan for an upgrade to NetBackup 10.4
- 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
- Windows compiler and security requirements for NetBackup 10.4 and later upgrade
- Creating the user account to support the NetBackup web server
- About NetBackup 10.4 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.4
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.4
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.4
- 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
- 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
- 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
Additional post-upgrade steps for NetApp clusters
After a NetBackup upgrade, review your NetApp cluster configuration as additional steps may be required to insure everything continues to work as expected. Table: Additional required NetApp cluster changes lists the various configurations and how to proceed.
Caution:
If at any time after the upgrade the mode changes from Node scope to Vserver aware, you must perform the additional steps. Failure to perform the additional steps places your data at risk.
Table: Additional required NetApp cluster changes
NetApp cluster mode at time of upgrade | Changes to NetApp cluster mode after upgrade | More information |
|---|---|---|
Node scope mode | No changes | Veritas and NetApp both recommend that you change to Vserver aware mode at your earliest convenience. |
Node scope mode | Change to Vserver aware mode | Additional steps required. See “Additional changes for Node scope mode to Vserver aware mode”. |
Vserver aware mode | Not applicable | Additional steps required. See “Additional changes required for NetApp clusters in Vserver aware mode”. |
Note:
Once a media server detects Vserver aware mode, no further backup activities are performed on any other media server running any earlier releases of NetBackup.
If you change from Node scope mode to Vserver aware mode, you must do the following:
Additional changes for Node scope mode to Vserver aware mode
- Enable the Vserver aware mode on the cluster by disabling node-scope-mode.
- If there are tape devices attached to the cluster nodes, you must reconfigure them. Configure the tape devices to use the cluster-management logical interface (LIF) as the NDMP host for the device configuration. NetBackup does not support use of node name for device configuration.
See the NetBackup NAS Administrator's Guide for additional information.
- Credential all the LIF that are used for backups.
This activity includes the Cluster Management LIF as well as any Vserver Data LIFs that are used for backup policies.
See the NetBackup NAS Administrator's Guide for additional information.
- Update the database for all existing NDMP hosts in your environment. Use the command that is shown to update the database.
tpautoconf - verify NDMP_host_name
- Update or replace any storage units that use the node names of the cluster to use the cluster LIF.
- Update or replace any existing policies that back up the cluster.
You must use either the Data LIF or the Cluster-management LIF as the client name. NetBackup does not support the use of the node name for the client name. The backup selections may also need to be modified.
- Add an intercluster management LIF for each node that does not host a cluster management LIF.
The NetApp cluster requires this activity to perform NDMP 3 way or NDMP Remote backups. Without these LIFs, all 3 way or remote backups from the volumes that are not hosted on the same node as the cluster management LIF fail.
- To restore, verify, or duplicate the old images, you may have to use alternate read host.
Additional changes required for NetApp clusters in Vserver aware mode
- Run tpautoconf command on each Vserver. This command must be run from the media servers that have credentials to the Vserver.
tpautoconf - verify ndmp_host
Once the command runs successfully, the output of the nbemmcmd should look similar to the following:
servername1@/>nbemmcmd -listsettings -machinename machinename123 - machinetype ndmp NBEMMCMD, Version: 7.7 The following configuration settings were found: NAS_OS_VERSION="NetApp Release 8.2P3 Cluster-Mode" NAS_CDOT_BACKUP="1" Command completed successfully. NAS_OS_VERSION displays the NetApp Version. NAS_CDOT_BACKUP tells us if NetBackup uses the new cDOT capabilities.
The tpautoconf - verify ndmp_host command is not required when a new Vserver is added.
- Add devices to the NDMP cluster as necessary and access them using the cluster management LIF. As you add devices, you must discover the devices.
- Add storage units for the newly discovered devices.
- Update any existing policies that back up the cluster.
You must use either the Data LIF or the Cluster-management LIF as the client name. NetBackup does not support the use of the node name for the client name. The backup selections may also need to be modified.