Skip to content

Update backup rationale with CloudSQL retained backups #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flashadmin merged 1 commit into from
Apr 15, 2026
Merged

Update backup rationale with CloudSQL retained backups #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,12 @@ and can ensure the correct IAM role bindings are in place for a successful expor

## Why

CloudSQL backups are tied to the instance — if the instance or GCP project
is deleted, the backups go with it. Exporting to a separate GCS bucket
(preferably in another project) provides additional data retention assurance.
~~CloudSQL backups are tied to the instance — if the instance or GCP project
is deleted, the backups go with it.~~ CloudSQL now supports
[retaining backups after instance deletion](https://docs.cloud.google.com/sql/docs/postgres/backup-recovery/manage-backups-deleted-instance),
but backups are still tied to the GCP project. Exporting to a GCS bucket
in a separate project provides additional data retention assurance and
better control over retention policies.

## Usage

Expand Down