Veritas NetBackup™ Upgrade Guide
- Introduction
- Planning for an upgrade
- General upgrade planning information
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 8.3 support for Fibre Transport Media Server with RHEL 7.5
- 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
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX and Linux server software to NetBackup 8.3
- Post-install procedure for upgrading to NetBackup 8.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 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
- Add or Remove Java GUI and JRE after upgrade
- About the NetBackup web user interface
- About the NetBackup answer file
- 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
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your OpsCenter server and your NetBackup Master Server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Index
Errors when Bare Metal Restore information is replicated using Auto Image Replication
Successful Auto Image Replication (AIR) of Bare Metal Restore (BMR) information requires two things. First, the master server in the target domain must have BMR enabled. Second, the master server in the target domain must be at the same or higher version of NetBackup than any clients that send BMR information. For example, if the master server in the target domain is NetBackup 8.3 and the client in the originating domain is 7.7.3, AIR works correctly.
If the client in the originating domain is NetBackup 8.3 and the master in the target domain is 7.7.3, the BMR information fails to replicate. All other information is successfully sent, only the BMR information is not replicated. You can restore the contents of the client, but you cannot use BMR.
More information about this topic is available.