Veritas NetBackup™ Flex Scale Installation and Configuration Guide
- Preparing for NetBackup Flex Scale deployment
 - Configuring NetBackup Flex Scale
 - Upgrading NetBackup Flex Scale to 3.2
- About NetBackup Flex Scale upgrades and EEBs
 - NetBackup Flex Scale upgrade overview
 - About parallel upgrade and supported upgrade paths
 - Downloading the upgrade file
 - Uploading the upgrade file and performing an upgrade precheck
 - Performing pre-upgrade tasks
 - Performing an upgrade using GUI
 - Performing post-upgrade tasks
 - Collecting logs for an upgrade precheck failure
 
 - Upgrading NetBackup Flex Scale to 3.2.100
- About NetBackup Flex Scale upgrades and EEBs
 - NetBackup Flex Scale upgrade overview
 - Supported upgrade paths
 - Downloading the upgrade file
 - Uploading the upgrade file and performing an upgrade precheck
 - Performing pre-upgrade tasks
 - Performing an upgrade using GUI
 - Performing post-upgrade tasks
 - Collecting logs for an upgrade precheck failure
 
 - Upgrading the firmware in NetBackup Flex Scale cluster
 - Managing EEBs
 - Removing NetBackup Flex Scale
 - Appendix A. Installing NetBackup Flex Scale 3.2 from a USB drive
 - Appendix B. Installing NetBackup Flex Scale using a downloaded ISO file
 - Appendix C. Upgrading a NetBackup Flex Scale node
 
Considerations for upgrade when disaster recovery is configured
When disaster recovery is configured, both the primary and secondary sites are upgraded in parallel and you are required to start the upgrade from only one site.
Review the following guidelines before you upgrade:
Upgrade can be performed only when both the primary and secondary sites are up and nodes are in healthy state.
Download and upload the upgrade package to only one of the sites.
After the upgrade package is uploaded, before you start the upgrade, navigate to and click . This will sync the upgrade package to the secondary site and trigger pre-checks on both the sites automatically.
Upgrade can be triggered from any cluster and both clusters are upgraded simultaneously.
If the upgrade fails on any cluster for any reason, both the clusters are rolled back to the previous version.