Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
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, CloudPoint 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.