Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Web UI Cloud Administrator's Guide
  3. Recovering cloud assets
  4. Recovering PaaS assets
  5. Recovering RDS-based PaaS asset
NetBackup™ Web UI Cloud Administrator's Guide

Recovering RDS-based PaaS asset

You can restore the RDS-based PaaS assets from the Applications tab, under the Cloud workload.

To restore RDS-based PaaS assets:

  1. On the left, click Workloads > Cloud and click the Applications tab. Click the name of the asset that you want to recover.
  2. Click the Recovery points tab in the calendar, select the date for which you want to see the recovery points.

    The available recovery points are displayed on the right.

  3. Click Recover in the row of the image that you want to recover.
  4. Under Source databases, select the databases that you want to restore. Click Add database, in the Add database dialog, select the required databases, and click Select.
  5. (For Amazon RDS Oracle databases only) Enter the staging path in the AWS S3 bucket name field. Click Start recovery. The recovered database appears in the Instant access databases tab. Recovery is possible on self-managed instance EC2 or on-premises VM To complete the recovery of the asset, see the Knowledge base article:

    https://support.cohesity.com/s/article/article-100058945

    You can select a different S3 bucket to stage the restored data, than the one used during the backup. You can also select a S3 bucket at a different region.

  6. Enter a prefix to add to the restored databases, or use the default. This field must have a value.
  7. (Optional) In the Target instance field, the source instance of the asset is selected by default. To restore to an alternate instance, select the required instance.
  8. (Optional, for MySQL databases only.) Select Restore metadata to restore metadata such as views, triggers, store procedures, and so on.
  9. (Optional, for MySQL databases only.) For the target instance credentials for restore:
    • Select Use already associated credentials to use the credentials that are already associated with the instance, and click Start recovery.

    • Select Use different credentials to use a different set of credentials, either existing credentials or create a new one.

      See Add credentials to a database .

      (Optional) Select Make default credentials to set these credentials as default credentials for the asset.

    • Select a validation host to validate the provided credentials.

  10. Click Start recovery.

The Restore activity tab shows you the status.

These two restore workflows implicitly create an instant access mount share against the recovery point.

Feedback

Was this page helpful?
Previous

Recovering AWS DocumentDB and Neptune assets

Next

Recovering Azure-protected assets

Feedback

Was this page helpful?