Google Cloud SQL for PostgreSQL and AlloyDB

You can use the Commvault software to back up and restore Google Cloud SQL Cluster for PostgreSQL.

Backups

Backups You Can Perform

• Full backups

When You Can Perform Backups

• On a schedule: The server plan that you assign manages scheduled backups

• On demand: You can perform on-demand backups at any time

Data You Can Back Up

• PostgreSQL user databases

  Note

  The following databases are not backed up:

  • Google Cloud PostgreSQL database - clousqladmin, template0, template1

Restores

Backups You Can Use for Restores

• The most recent backup: For example, restore the most recent backup to its original location

• A backup from a specific date: For example, restore data to a point in time before it became unusable

• Backups from a date range: For example, restore data that was accidentally deleted

Destinations You Can Restore To

• In-place: Restore data to the location that it was backed up from

• Out-of-place PostgreSQL restore: Restore data to the following destinations:

  • Cross-cloud: You can restore PostgreSQL databases from one cloud platform (such as Amazon Web Services and Google Cloud Platform) to a different cloud platform. The source computer and destination computer must have the same operating system.

  • An instance in the same platform or a different platform (such as Alibaba Cloud, Amazon Web Services, Azure, and Google Cloud Platform) across regions

  • An on-premises instance

• Out-of-place AlloyDB restore: Only supports restoring to a different AlloyDB instance.

  Note

  Out of place database-level restores from AlloyDB to non-AlloyDB destination engines are not supported because the following AlloyDB-specific extensions cannot be created on the target destination: google_columnar_engine, google_db_advisor, and hypopg. However, table-level out-of-place restores are possible when only user-created tables, views, or other elements are selected.