Veritas NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 8.1.2 Upgrade Guide
- About changes in NetBackup 8.1.2
- Veritas Smart Meter introduced
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- HP-UX and AIX support change
- Newer Red Hat Linux compilers used with NetBackup 8.1.2
- VxUpdate replaces update_clients script in NetBackup 8.1.2
- Port 443 required for NetBackup web user interface
- About MSDP
- Performance issues with upgrades to NetBackup 8.1.2 from NetBackup 8.0 and earlier
- About certificate requirements for NetBackup 8.1
- SCCM and Chef deployment tools and documentation now available
- Potential required changes for NetApp clusters
- About automatic file changes from an upgrade
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Known catalog backup limitation
- Available NetBackup upgrade methods
- About Veritas Services and Operations Readiness Tools
- Recommended SORT procedures for new installations
- Recommended SORT procedures for upgrades
- About the NetBackup preinstall checker
- Planning for an upgrade
- About planning a NetBackup 8.1.2 upgrade
- How to plan for an upgrade to NetBackup 8.1.2
- About Veritas Smart Meter
- Best practices for Veritas Smart Meter
- Creating the user account to support the NetBackup web server
- About NetBackup 8.1.2 support for Fibre Transport Media Server with RHEL 7.5
- MSDP changes in NetBackup 8.1
- About security certificates for NetBackup hosts
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.1.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX/Linux server software to NetBackup 8.1.2
- Post-install procedure for upgrading to NetBackup 8.1.2
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup master server web server user and group creation
- Generate a certificate on the inactive nodes of a clustered master server
- About the NetBackup Java Runtime Environment
- About the NetBackup web user interface
- About the NetBackup answer file
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.2
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Installation and upgrade requirements for UNIX and Linux
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Upgrading clients after servers are upgraded
- Install and upgrade of the UNIX and Linux client binaries with native installers
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
- Post upgrade procedures for Amazon cloud storage servers
MSDP upgrade considerations for NetBackup 8.1
Because of the changes in the fingerprint algorithm for MSDP in NetBackup 8.1, consider your MSDP environment as you plan your upgrade path. Any NetBackup 8.0 and older host cannot access the NetBackup 8.1 MSDP because of the new fingerprint algorithm. Failed NetBackup jobs can result from a failure to plan for this condition.
If the media servers list for an 8.1 MSDP storage server contains 8.0 or older servers, you can experience failures because of the new algorithm. If the common media server between an 8.1 server and an 8.0 server is the 8.0 server, jobs can fail. If you use client direct, the client must be upgraded to 8.1 or you can experience client direct restore errors. These failures are because the 8.0 and older hosts cannot access the 8.1 server.
As you plan your upgrade, if you have multiple media servers as part of an MSDP environment, consider the options shown:
Upgrade all MSDP media servers that share access rights to each other together. Upgrade all clients that use client direct to these MSDP disk pools.
This option insures there are no interruptions in your environment.
Upgrade MSDP media servers and clients using client direct as your environment allows and make no configuration changes.
If the selected common media server is not a NetBackup 8.1 server, the risk is restores, verifies, imports, and optimized duplication may fail. If client direct is used on older clients, you can experience client direct restore errors. This failure is because of the algorithm change.
Upgrade MSDP media servers and clients using client direct as your environment allows. Modify your list of credentialed media servers for the upgraded storage servers to only include NetBackup 8.1 servers.
This action effectively revokes access rights for the non-upgraded servers to the upgraded servers. The risk is previously configured operations may stop working because of the access change. If you choose this option, you should make detailed notes about the configuration changes so you can revert those changes once all media servers are upgraded.
If duplication jobs copy from an 8.1 MSDP to an 8.0 or older MSDP, then create a storage unit for the older MSDP. Restrict the list on that new storage unit to the 8.1 host. You must change any storage lifecycle policy (SLP) controlled duplication jobs if they copy from an 8.0 or older MSDP host to an 8.1 MSDP host. Set the Alternate Read Server on the duplication stage to the 8.1 media server.