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. Protecting PaaS assets
  4. Limitation and considerations
  5. For cumulative incremental backups using Amazon RDS SQL
NetBackup™ Web UI Cloud Administrator's Guide

For cumulative incremental backups using Amazon RDS SQL

  • You can protect Amazon RDS SQL database assets with a NetBackup protection plan or policy. You can use both full and cumulative incremental backup schedules.

  • Backup and restore of TDE Certificates on RDS instances with Multi-AZ (Multi-Availability Zone) deployments is not supported directly on the RDS instance.

  • To backup TDE certificates, disable Multi-AZ on the instance temporarily, and enable it after the backup is complete.

  • To restore user TDE certificates, disable Multi-AZ on that instance temporarily, and enable it after the restore is complete.

  • You cannot disable the automated backups when Multi-AZ is enabled on the RDS instance.

  • Automated backups occur daily, during a user-configurable 30-minute window. These backups create more frequent requirements for full backups. A full backup runs at least once a day if the cumulative schedule comes after the automated backups.

  • You can restore a full backup to Multi-AZ instance in the recovery mode only.

  • Cumulative incremental backups can only be restored to an RDS instance in a single availability zone.

  • Whenever a cleanup of backup history is performed either by calling the sp_delete_backuphistory API or by the Amazon maintenance window, the subsequent backup falls back to a full backup.

  • When you perform a full backup of an Amazon RDS SQL Server asset using a different policy, the subsequent cumulative backup in the current policy is treated as full backups. This happens because the new full backup updates the backupset ID of the last full backup, causing the cumulative backup in the current policy to lose its reference point and run as a full backup instead.

Feedback

Was this page helpful?
Previous

For Azure, Amazon RDS, and Aurora MySQL

Next

For incremental backups using Amazon DynamoDB

Feedback

Was this page helpful?