high availability

Related topics

• high availability is part of Cloud SQL From the official documentation: “You can configure a Cloud SQL instance for high availability by using the Google Cloud console, [gcloud CLI](/sdk/gcloud), or the API.”
• Cloud SQL configures high availability From the official documentation: “If you want your instance to be replicated between zones synchronously, then [configure it for high availability](/sql/docs/mysql/high-availability).”
• high availability depends on automated backups From the official documentation: “Check the instance to see if automatic backups and binary logs are enabled. These are required for high availability instances.”
• high availability configures Cloud SQL From the official documentation: “If you want your instance to be replicated between zones synchronously, then [configure it for high availability](/sql/docs/postgres/high-availability).”
• high availability depends on point-in-time recovery From the official documentation: “Check the instance to see if automatic backups and point-in-time recovery are enabled. These are required for high availability instances.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• point-in-time recovery is part of Spanner From the official documentation: “Spanner point-in-time recovery (PITR) provides protection against accidental deletion or writes.”
• automated backups is part of Cloud SQL From the official documentation: “You can take on-demand, automated, or final backups for your Cloud SQL instances.”
• automated backups is an alternative to on-demand backups From the official documentation: “There are two database backup methods for Cloud SQL for PostgreSQL: on-demand and automated.”
• Cloud SQL is an alternative to Spanner From the official documentation: “If a workload requires transaction processing with strong relational consistencies, [Spanner](/spanner/docs/overview) or [Cloud SQL](/sql/docs) can be better alternatives.”
• Cloud Storage works with point-in-time recovery From the official documentation: “For data retention needs beyond 14 weeks, you can use PITR to create an export of your entire database and save this data in Cloud Storage indefinitely.”
• point-in-time recovery is an alternative to read replica From the official documentation: “You can recover a standalone instance from a zonal outage manually by performing either point-in-time-recovery or by promoting a read replica to become the standalone instance.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL is an alternative to Firestore From the official documentation: “If you're interested in evaluating how the performance of your on-premises databases compares to [Cloud SQL](/sql), [Spanner](/spanner), [Firestore](/firestore), or [Bigtable](/bigtable), you could implement a PoC where the same business logic uses different databases.”
• Cloud Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
• on-demand backups is part of Cloud SQL From the official documentation: “You can take on-demand, automated, or final backups for your Cloud SQL instances.”
• point-in-time recovery depends on automated backups From the official documentation: “In addition, Cloud SQL for PostgreSQL lets you restore a PostgreSQL database to a specific [point in time](/sql/docs/postgres/backup-recovery/pitr) as long as point-in-time recovery is turned on and the automated backup option is enabled.”
• point-in-time recovery is part of Cloud SQL From the official documentation: “Cloud SQL provides the following options to restore your instance using PITR:”
• point-in-time recovery depends on Cloud Storage From the official documentation: “Must store the transaction logs used for PITR in Cloud Storage”
• point-in-time recovery is part of Firestore From the official documentation: “After you enable PITR, Firestore starts retaining PITR data.”
• read replica is part of Cloud SQL From the official documentation: “This page applies to replicas of a Cloud SQL instance.”
• read replica depends on point-in-time recovery From the official documentation: “Additionally, the point-in-time recovery option, which uses write-ahead logs, is also required for creating a read replica.”