Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- About the deployment approach
- Deciding where to run CloudPoint
- About deploying CloudPoint in the cloud
- Meeting system requirements
- CloudPoint host sizing recommendations
- Creating an instance or preparing the physical host to install CloudPoint
- Installing Docker
- Creating and mounting a volume to store CloudPoint data
- Verifying that specific ports are open on the instance or physical host
- Deploying CloudPoint using the Docker image
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- NetApp plug-in configuration notes
- Nutanix Files plug-in configuration notes
- Dell EMC Unity array plug-in configuration parameters
- Pure Storage FlashArray plug-in configuration notes
- HPE RMC plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- How to configure the CloudPoint storage array plug-ins?
- CloudPoint application agents and plug-ins
- Microsoft SQL plug-in configuration notes
- Oracle plug-in configuration notes
- MongoDB plug-in configuration notes
- About the installation and configuration process
- Preparing to install the Linux-based agent
- Preparing to install the Windows-based agent
- Downloading and installing the CloudPoint agent
- Registering the Linux-based agent
- Registering the Windows-based agent
- Configuring the CloudPoint application plug-in
- Configuring VSS to store shadow copies on the originating drive
- Creating a NetBackup protection plan for cloud assets
- Subscribing cloud assets to a NetBackup protection plan
- About snapshot restore
- Restore requirements and limitations for Microsoft SQL Server
- Restore requirements and limitations for Oracle
- Restore requirements and limitations for MongoDB
- Steps required before restoring SQL AG databases
- Recovering a SQL database to the same location
- Recovering a SQL database to an alternate location
- Additional steps required after a SQL Server snapshot restore
- Additional steps required after restoring SQL AG databases
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Additional steps required after a MongoDB snapshot restore
- Additional steps required after an Oracle snapshot restore
- Additional steps required after restoring an AWS RDS database instance
- Protecting assets with CloudPoint's agentless feature
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
Disaster recovery when DR package is lost or passphrase is lost
This issue may occur if the DR package is lost or the passphrase is lost.
In case of Catalog backup, 2 backup packages are created:
DR package which contains all the certs
Catalog package which contains the data base
The DR package contains the NetBackup UUID certs and Catalog DB also has the UUID. When you perform disaster recovery using the DR package followed by catalog recovery, both the UUID cert and the UUID are restored. This allows NetBackup to communicate with CloudPoint since the UUID is not changed.
However if the DR package is lost or the Passphrase is lost the DR operation cannot be completed. You can only recover the catalog without DR package after you reinstall NetBackup. In this case, a new UUID is created for NetBackup which is not recognised by CloudPoint. The one-to-one mapping of NetBackup and CloudPoint is lost.
Workaround:
To resolve this issue, you must update the new NBU UUID and Version Number after NetBackup master is created.
The NetBackup administrator must be logged on to the NetBackup Web Management Service to perform this task. Use the following command to log on:
/usr/openv/netbackup/bin/bpnbat -login -loginType WEB
Execute the following command on the master server to get the NBU UUID:
/usr/openv/netbackup/bin/admincmd/nbhostmgmt -list -host < Master Server host name > | grep "Host ID"
Execute the following command to get the Version Number:
/usr/openv/netbackup/bin/admincmd/bpgetconfig -g <Master Server host name> -L
After you get the NBU UUID and Version number, execute the following command on the CloudPoint host to update the mapping:
/cloudpoint/scripts/cp_update_nbuuid.sh -i <NBU UUID> -v <Version Number>