For Incremental backups using GCP PostgreSQL

You can protect GCP Postgres SQL assets with NetBackup protection plan or policy.
Both full and differential incremental schedules are supported.
To enable logical decoding on Google Cloud SQL for PostgreSQL, configure the database flag cloudsql.logical_decoding. Do the following:
- Navigate to your Cloud SQL instance in the GCP console.
- Click Edit, and scroll to the Flags section.
- Add or modify the parameter cloudsql.logical_decoding flag.
- Save the changes and restart the instance. You must restart of the Cloud SQL instance for these changes to take effect.
Assign REPLICATION permissions to the backup user.
Replica server databases are 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>)