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
Additional steps required after restoring an AWS RDS database instance
The following steps are required after you restore an AWS RDS database instance snapshot. Even though the restore operation is successful, these manual steps are required so that the instance is available for normal use.
After restoring an AWS RDS database instance successfully, you have to manually check and reassign certain properties of the restored instance. This is required because even though the restore operation itself is successful, one or more instance properties are not restored completely. In some cases, NetBackup resets the property values to their default settings.
The following RDS database instance or cluster properties are not restored completely and will need modification:
VPC security groups value (AWS Management Console > RDS Database instance > Connectivity & security tab)
Deletion protection setting (AWS Management Console > RDS Database instance > Configuration tab)
Copy tags to snapshots setting (AWS Management Console > RDS Database instance > Maintenance & backups tab)
Perform the following steps:
- Verify that the RDS database instance snapshot restore is successful.
- Sign in to the AWS Management Console and from the top right corner, select the region in which you have restored the RDS instance.
- From the Services menu, under Database, click RDS.
- From the Dashboard menu on the left, click Databases.
- In the Databases panel, select the restored RDS database instance and then click Modify from the menu bar on the top right.
- On the Modify DB panel, check for the following properties and ensure that the attribute values match with those of the original instance:
Under Network & Security, verify that the Security group attribute has the correct security group name assigned.
Under Backup, verify that the Copy tags to snapshots option is set as per the original instance.
Under Deletion protection, verify that the Enable deletion protection option is set as per the original instance.
If required, verify all the other parameter values and set them as per your preference.
- Once you have modified the desired RDS instance properties, click Continue.
- Under Scheduling of modifications, choose an appropriate option depending on when you wish to apply the modifications to the instance and then click Modify DB instance.
- Verify the RDS instance properties and ensure that the changes have taken effect.