high availability

Related topics

• failover depends on high availability From the official documentation: “If high availability (HA) is available, trigger a failover.”
• high availability is part of Cloud SQL From the official documentation: “HA in Cloud SQL works by having two synchronized instances: a primary instance and a standby instance.”
• standby replica is part of high availability From the official documentation: “You can enable HA in your database cluster by directing the AlloyDB Omni Kubernetes Operator to create standby replicas of your primary database instance.”
• 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 Database Migration Service From the official documentation: “Gives Cloud Database Migration service account access to Cloud SQL resources.”
• 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 Cloud SQL From the official documentation: “Cloud SQL provides the following options to restore your instance using PITR:”
• read replica is part of Cloud SQL From the official documentation: “This page applies to replicas of a Cloud SQL instance.”
• Cloud Storage works with Database Migration Service From the official documentation: “Database Migration Service replicates data from SQL Server backup and transaction log files that you upload to a Cloud Storage bucket.”
• 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 part of Spanner From the official documentation: “Spanner point-in-time recovery (PITR) provides protection against accidental deletion or writes.”
• 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.”
• Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
• 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 Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
• Database Migration Service depends on Cloud Storage From the official documentation: “If you use file export and import to migrate, or use the Database Migration Service migration tool, you need to create a Cloud Storage bucket.”
• Database Migration Service depends on point-in-time recovery From the official documentation: “Your source Cloud SQL for SQL Server must have point-in-time recovery (PITR) enabled so that Database Migration Service can create transaction log backup files.”
• point-in-time recovery depends on Cloud Storage From the official documentation: “Must store the transaction logs used for PITR in Cloud Storage”
• 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.”