> Software > Databases > Google Cloud

Google Cloud SQL for PostgreSQL and AlloyDB

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

Note

  • The recommended maximum size for Google Cloud SQL for PostgreSQL and AlloyDB database is 2 TB. Daily backups are not supported for databases larger than 2 TB. For information about handling larger databases, see GCP Best practices.

  • Commvault supports pgvector extension for Google Cloud PostgreSQL and AlloyDB. The destination instance should also have pgvector extension in case of out-of-place restore.

To perform PostgreSQL cloud backups from replica, consider the following recommendation:

  1. For PostgreSQL master-replica configurations:

    1. Use the master node for backups to avoid potential conflicts with the recovery process on replicas, which might interfere with tools such as pg_dump. Configuring backups on the master node introduces some overhead, as the Commvault access node connects directly to the master database to perform pg_dump.

    2. If using a replica for backups, ensure to configure max_standby_archive_delay and max_standby_streaming_delay settings to allow sufficient time for the Commvault triggered pg_dump to complete without being canceled due to WAL replay conflicts. For more information, see PostgreSQL Hot Standby Conflicts.

  2. Schedule backups during off-peak or quiet hours

    • Schedule backups during off-peak or quiet hours to ensure faster execution and minimize the risk of connection interruptions or resource contention.

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.

×

Loading...