Veritas NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 8.1.1 Upgrade Guide
- About changes in NetBackup 8.1.1
- 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
- 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
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.1.1
- 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.1
- Post-install procedure for upgrading to NetBackup 8.1.1
- About mounting the NetBackup software media
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- 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 answer file
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.1
- About NetBackup software availability
- About the NetBackup media kit
- About the NetBackup Electronic Software Distribution (ESD) images
- 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
Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.1
If you use cloud storage in your NetBackup environment, you may need to update your cloud configuration file on the NetBackup master server immediately after you install or upgrade to NetBackup 8.1.1. If a cloud provider or related enhancement is not available in the cloud configuration file after upgrading to NetBackup 8.1.1, related operations will fail.
Veritas continuously adds new cloud support to the cloud configuration files between releases. The cloud storage support included in the NetBackup 8.1.1 final build matches that which is contained in the cloud configuration package version 2.3.2.
Updating your cloud configuration files is necessary only if your cloud storage provider was added to the cloud configuration package version 2.3.3 or newer. The following cloud support has been added to version 2.3.3 but were not included in the NetBackup 8.1.1 final build:
Deutsche Telekom Open Telekom Cloud (S3) - Changed default URL style
IBM Cloud Object Storage (S3) - Cold storage class
IBM Cloud Object Storage (S3) - Flex storage class
IBM Cloud Object Storage (S3) - EU Cross Region
IBM Cloud Object Storage (S3) - EU South Region
IBM Cloud Object Storage (S3) - Standard storage class
IBM Cloud Object Storage (S3) - US Cross Region
IBM Cloud Object Storage (S3) - US East Region
IBM Cloud Object Storage (S3) - Vault storage class
Iron Mountain Iron Cloud (S3)
NetApp StorageGRID (S3) - LAN
NetApp StorageGRID (S3) - Changed default URL style for WAN
NooBaa (S3)
Oracle Cloud Infrastructure (S3)
For the latest cloud configuration package, see the following tech note:
http://www.veritas.com/docs/100033434
For additional information on adding cloud storage configuration files, refer to the following tech note: