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
  3. NetBackup™ Web UI Cloud Administrator's Guide
  5. Protecting PaaS assets
  7. Limitation and considerations
  9. For Incremental backups with Amazon RDS PostgreSQL and Amazon Aurora PostgreSQL
NetBackup™ Web UI Cloud Administrator's Guide

For Incremental backups with Amazon RDS PostgreSQL and Amazon Aurora PostgreSQL

  • You can protect Amazon RDS PostgreSQL and Amazon Aurora PostgreSQL assets with NetBackup protection plan or policy.

  • Both full and differential incremental schedules are supported.

  • To enable logical decoding in Amazon RDS PostgreSQL and Aurora PostgreSQL, configure the rds.logical_replication server parameter to 1, in the custom DB parameter group.

    Do the following in the AWS console:

    • Create a custom DB parameter group (for RDS) or custom DB cluster parameter group (for Aurora).

    • Set the rds.logical_replication server parameter to 1.

    • Associate the parameter group with your database instance or cluster.

    • Restart the writer instance to apply changes.

    • Verify settings using SQL: SHOW wal_level.

  • Replica server databases are not supported for full and incremental backup.

  • Databases having Large objects are not supported for incremental backup.

  • Incremental backups are not supported with the bytea_output server parameter having the value: escape.

  • Incremental backups are not supported, if:

    • If the backup user is non-admin.

    • The tables of other users do not have a primary key.

  • After restoring an incremental backup, the last value of the sequence may not be consistent.

  • Before renaming a database, follow these steps:

    • Note down the name OS the replication slot created for the database that you want to rename.

    • Select the slot_name form pg_replication_slots, where: database = <database name that needs to be renamed>

    • Drop the replication slot after renaming the database: SELECT pg_drop_replication_slot(<replication slot name>)

Feedback

Was this page helpful?
Previous

For Incremental backups using GCP PostgreSQL

Next

For Azure SQL and SQL Managed Instance

Feedback

Was this page helpful?