Meta tags:

Headings (most frequently used words):

disaster, recovery, promote, replicas, for, regional, migration, and, dr, the, or, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, overview, advanced, verify, failover, criteria, read, replica, ensure, machine, type, is, appropriate, enable, high, availability, promoted, instance, recreate, additional, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
the (121), and (68), cloud (60), #instance (60), #replica (46), sql (46), connect (39), region (37), for (35), primary (32), with (29), from (29), using (29), use (28), manage (26), you (23), database (23), replicas (20), high (19), availability (19), recovery (19), overview (19), instances (18), that (18), about (17), disaster (17), configure (17), data (17), cross (16), create (16), read (15), mysql (15), promoted (14), promote (14), has (13), replication (13), google (12), can (12), upgrade (12), migration (11), private (10), quickstart (10), failover (9), access (9), import (9), engine (9), see (8), unavailable (8), your (8), regional (8), server (8), databases (8), set (8), external (8), thumb (7), its (7), policies (7), new (7), backups (7), choose (7), management (7), vector (7), managed (7), resources (6), information (6), more (6), are (6), newly (6), then (6), transactions (6), perform (6), storage (6), monitor (6), performance (6), export (6), service (6), iam (6), authentication (6), code (5), samples (5), all (5), other (5), this (5), becomes (5), become (5), have (5), not (5), usage (5), promoting (5), how (5), time (5), may (5), advanced (5), tools (5), issues (5), connection (5), certificates (5), settings (5), ssl (5), tls (5), encryption (5), view (5), embeddings (5), app (5), proxy (5), version (5), português (4), español (4), down (4), need (4), configuration (4), old (4), former (4), when (4), same (4), enable (4), ensure (4), monitoring (4), instructions (4), client (4), were (4), lost (4), lag (4), restore (4), another (4), migrate (4), compute (4), application (4), public (4), reconfigure (4), optimize (4), logs (4), query (4), language (4), build (4), best (4), practices (4), custom (4), auth (4), control (4), users (4), organization (4), major (4), maintenance (4), free (4), terms (3), system (3), status (3), understand (3), content (3), page (3), east1 (3), now (3), west1 (3), central1 (3), different (3), original (3), example (3), machine (3), memory (3), amount (3), following (3), received (3), before (3), became (3), which (3), seconds (3), committed (3), been (3), because (3), loss (3), enterprise (3), plus (3), edition (3), guides (3), observability (3), analytics (3), capacity (3), tables (3), troubleshoot (3), reduce (3), table (3), prevent (3), backup (3), open (3), auditing (3), disable (3), indexes (3), insights (3), mcp (3), queries (3), capture (3), audit (3), search (3), model (3), endpoint (3), reference (3), applications (3), files (3), standard (3), vpc (3), run (3), pooling (3), connectors (3), customer (3), tags (3), secure (3), place (3), console (3), trial (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), join (2), site (2), youtube (2), events (2), architecture (2), started (2), support (2), pricing (2), products (2), missing (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), license (2), send (2), feedback (2), name (2), note (2), again (2), additional (2), delete (2), recreate (2), any (2), consider (2), automatically (2), configuring (2), done (2), recommend (2), also (2), type (2), appropriate (2), cpu (2), than (2), handle (2), metrics (2), standalone (2), once (2), determine (2), criteria (2), verify (2), reflects (2), check (2), value (2), indicates (2), writes (2), outage (2), recent (2), steps (2), roles (2), designated (2), fail (2), over (2), promotion (2), update (2), clients (2), general (2), case (2), both (2), main (2), planned (2), operations (2), documentation (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), security (2), networking (2), industry (2), solutions (2), distributed (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), known (2), password (2), remove (2), authorized (2), networks (2), log (2), enabling (2), automated (2), number (2), cache (2), improve (2), assistance (2), agents (2), saved (2), generate (2), invoke (2), predictions (2), dump (2), point (2), option (2), back (2), file (2), replicate (2), pool (2), pools (2), kubernetes (2), flexible (2), phpmyadmin (2), authorize (2), services (2), write (2), keys (2), cmek (2), add (2), parameterized (2), views (2), studio (2), built (2), minor (2), network (2), updates (2), shrink (2), start (2), environment (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, cookies, privacy, tech, twitter, blog, engage, training, certification, center, getting, github, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, details, java, registered, trademark, oracle, affiliates, developers, apache, creative, commons, attribution, resulting, would, names, retains, regions, referenced, repeated, here, earlier, configured, way, intend, alternatively, workload, such, smaller, resize, match, load, detailed, could, writable, met, one, writeable, scenario, tab, pertaining, processed, ensures, exec_master_log_pos, relay_master_log_file, read_master_log_pos, master_log_file, first, far, behind, metric, just, window, during, showed, true, less, includes, successfully, but, simply, yet, applied, dashboard, asynchronous, occurs, attempted, some, replicated, whenever, show, many, possible, return, deployment, state, after, zero, switchover, since, switch, designate, replace, only, still, without, used, part, procedure, should, extended, period, involved, follow, those, verified, working, minimal, downtime, idea, wait, until, catches, direct, manually, intentionally, where, standby, failure, zonal, cases, involve, setting, difference, between, them, whether, unplanned, needed, continue, event, there, two, common, scenarios, describes, created, postgresql, save, categorize, based, preferences, stay, organized, collections, home, updating, orphan, diagnose, debug, error, messages, looker, user, rotate, broad, ranges, underprovisioned, overprovisioned, idle, temporary, increasing, retention, out, disk, definitions, increase, reliability, enforce, apply, recommendations, active, index, advisor, natural, querydata, conversational, securing, agent, interactions, remote, work, preview, filter, register, interact, models, llm, powered, langchain, embedding, workflow, online, integrate, vertex, generative, develop, cancel, parallel, csv, importing, exporting, deleted, enhanced, legacy, percona, xtrabackup, physical, large, replicating, autoscaling, outside, connections, functions, operator, dns, certificate, authority, across, multiple, vpcs, learn, brute, force, protection, controls, endpoints, side, attach, fine, grained, conditions, permissions, identity, predefined, secret, manager, secrets, residency, knowledge, catalog, gemini, execute, statements, api, character, collation, operational, guidelines, migrating, versions, troubleshooting, peering, allowlists, self, windows, connectivity, tests, locations, flags, supported, deletion, label, stop, restart, clone, edit, series, plan, prepare, local, computer, shell, get, key, features, editions, discover, skip,

Text of the page (random words):
ersion in place troubleshooting in place major version upgrade to mysql 8 0 known issues in mysql 8 0 minor versions upgrade the database major version by migrating data upgrade the database minor version use best practices general best practices operational guidelines databases create and manage databases update the character set and collation for a database execute sql statements using the cloud sql data api users about mysql users cloud sql built in database authentication manage users with built in authentication cloud sql studio manage your data using cloud sql studio write sql with gemini assistance manage your resources using knowledge catalog secure and control access overview about access control data residency overview use secret manager to handle secrets in cloud sql parameterized secure views overview use parameterized secure views organization policies cloud sql organization policies add predefined organization policies add custom organization policies identity and access management iam iam authentication roles and permissions use iam conditions configure instances for iam database authentication manage users with iam database authentication log in using iam database authentication fine grained access control with tags access control with google cloud tags attach and manage tags on cloud sql instances use encryption about client side encryption about customer managed encryption keys cmek use customer managed encryption keys cmek use cloud sql regional endpoints configure vpc service controls use cloud sql brute force protection connect choose how to connect to cloud sql authorize with authorized networks connect to an instance using public ip configure public ip connect to an instance using private ip learn about using private ip configure private ip configure private services access connect to an instance using a write endpoint private service connect overview connect to an instance using private service connect configure both private services access and private service connect connect to your instance across multiple vpcs connect using ssl tls certificates authorize with ssl tls certificates configure ssl tls certificates manage ssl tls certificates use a customer managed certificate authority ca set up a custom dns name connect using cloud sql language connectors cloud sql language connectors overview connect using the cloud sql language connectors connect using the cloud sql auth proxy about the cloud sql auth proxy connect using the cloud sql auth proxy connect using cloud sql proxy operator use managed connection pooling managed connection pooling overview configure managed connection pooling connect from applications connect using a mysql client connect from cloud run connect from cloud functions connect from app engine standard use phpmyadmin on app engine use phpmyadmin on cloud run connect from app engine flexible connect from compute engine connect from kubernetes engine connect from cloud build manage database connections connect from other mysql tools connect to an instance from outside its vpc replicate about replication in cloud sql create and manage replicas create read replicas manage read replicas create and manage indexes on read replicas promote replicas for regional migration or disaster recovery replication lag create and manage read pools about read pools create a read pool read pool autoscaling configure external replicas replicate from an external server about replicating from an external server configure cloud sql and the external server for replication use a managed import to set up replication from external databases use a dump file to set up replication from external databases use a custom import to set up replication from large external databases migrate data about data migration in cloud sql migrate from a percona xtrabackup physical file migrate from cloud sql to an external server availability and disaster recovery dr availability in cloud sql about high availability ha enable and disable high availability ha legacy configuration for high availability ha about disaster recovery dr use advanced disaster recovery dr back up and restore back up an instance cloud sql backups overview choose your backup option manage standard backups manage enhanced backups manage backups for deleted instances view audit logs for automated backups restore an instance overview restore an instance using a backup configure point in time recovery perform point in time recovery import and export best practices for importing and exporting data export and import using sql dump files export and import using csv files export and import files in parallel cancel the import and export of data check the status of import and export operations develop build generative ai applications using cloud sql integrate cloud sql with vertex ai invoke online predictions understand an example of an embedding workflow build llm powered applications using langchain interact with custom models using model endpoint management overview register a model generate embeddings invoke predictions model endpoint management reference vector search vector search enable and disable vector embeddings generate and manage vector embeddings create and manage vector indexes search and filter with vector embeddings work with vector embeddings preview use cloud sql for mysql with agents use the cloud sql remote mcp server best practices for securing agent interactions with mcp use saved queries overview create and manage saved queries build data agents with conversational analytics query database in natural language with querydata monitor and optimize about database observability monitor and troubleshoot with ai assistance audit audit logs mysql database auditing use mysql database auditing performance capture overview configure performance capture view performance capture logs query performance use query insights use index advisor monitor active queries system performance monitor instances view instance logs use system insights monitor cloud sql using the database insights mcp server apply recommendations create indexes or reconfigure join settings disable public ip enable database auditing enforce ssl tls encryption improve instance reliability by enabling high availability improve performance with enterprise plus increase the table open cache manage open tables and open table definitions manage high number of tables monitor disk availability optimize high cpu usage optimize high memory usage optimize instances with high number of out of memory events prevent data loss by enabling automated backups prevent data loss by increasing backup retention reconfigure connection settings reconfigure log settings reconfigure temporary table settings reduce idle cloud sql instances reduce overprovisioned cloud sql instances reduce underprovisioned cloud sql instances remove authorized networks remove broad public ip ranges rotate server certificates set instance password policies set user password policies use looker with cloud sql troubleshoot known issues troubleshoot error messages debug connection issues diagnose issues orphan tables issues updating storage capacity ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation databases cloud sql mysql guides send feedback promote replicas for regional migration or disaster recovery stay organized with collections save and categorize content based on your preferences mysql postgresql sql server this page describes how to use and promote cross region read replicas replicas created in a different region from that of the primary for regional migration or disaster recovery overview there are two common scenarios for promoting cross region replicas regional migration perform a planned migration of a database to a different region disaster recovery fail over a database to another region in the event that the primary s region becomes unavailable both use cases involve setting up cross region replication and then promoting the replica the main difference between them is whether the promotion of the replica is planned in the case of regional migration or unplanned a failover to the replica s region is needed to continue operations because the primary has become unavailable note promoting a replica is done manually and intentionally it is not the same as high availability where a standby instance which is not a replica automatically becomes the primary in case of a failure or zonal outage regional migration you can use a cross region replica to migrate your database to another region with minimal downtime the general idea is to create a replica in another region wait until replication catches up promote it and then direct clients to the newly promoted instance the steps involved in promotion are the same as for promoting an in region replica follow those instructions to ensure that the newly promoted instance has all of the transactions that were committed to the original primary instance once you have promoted the replica and verified that the newly promoted instance is working update all database clients to connect to the new instance disaster recovery dr cross region replicas can be used as part of a disaster recovery procedure you can promote a cross region replica to fail over to another region should the primary instance s region become unavailable for an extended period of time for more information about disaster recovery see about disaster recovery in cloud sql advanced disaster recovery dr if you are using cloud sql enterprise plus edition then you can designate a cross region read replica as a disaster recovery replica dr replica for advanced disaster recovery dr with advanced dr you perform a replica failover to replace the primary instance with the designated dr replica the old primary instance becomes a replica of the promoted dr replica you can only perform replica failover to the designated dr replica you can still promote other read replicas without failover to return your deployment to the original state after the replica failover with zero data loss you can perform a switchover since the old primary instance is a replica of the new primary instance you can switch roles again to restore the old primary instance for more information see advanced disaster recovery dr verify failover criteria because replication is asynchronous when a region outage occurs and a failover is attempted some recent transactions that were committed to the primary may be lost not replicated to the replica whenever a primary instance becomes unavailable the following steps show 1 how to determine the amount of data if any that may have been lost in the cross region failover and 2 how to ensure that the promoted replica reflects as many recent writes as possible first check the replication lag value for the replica instance in the monitoring dashboard which indicates how far in seconds the replica is behind its primary the value of this metric at the time just before the primary became unavailable indicates the window of time during which transactions committed to the primary may have been lost for example if the replication lag showed 5 seconds then the replica may be missing writes to the primary from the 5 seconds before the primary became unavailable the true amount of data lost may be less than this because replication lag also includes transactions that were successfully received by the replica but simply have not yet been applied then connect to the replica instance with a mysql client by following the instructions in the replication status page see the mysql client tab see the instructions pertaining to the master_log_file read_master_log_pos relay_master_log_file and exec_master_log_pos metrics verify that the replica has processed all the transactions it has received from the primary this ensures that when promoted the replica reflects all transactions that were received before the primary became unavailable promote a read replica once you determine that the failover criteria are met you can promote one of the replicas to a writeable standalone instance consider the following scenario region a us central1 has a high availability primary instance db a 0 region b us west1 has a high availability cross region replica db b 1 of db a 0 region c us east1 has a cross region replica db c 1 of db a 0 you could choose to promote db b 1 in region b to become a standalone writable instance see promoting a replica for detailed instructions ensure the machine type is appropriate ensure that the machine type of the newly promoted instance is appropriate for its workload by monitoring metrics on the instance such as cpu and memory usage if the newly promoted instance is smaller than its former primary instance we recommend that you resize the promoted instance to match its former primary so that it can handle the same amount of load enable high availability for the promoted instance for a disaster recovery configuration we recommend that you configure the replica that you intend to promote as a high availability replica alternatively configure the newly promoted instance as high availability if you choose not to configure the read replica with high availability you can also configure the instance with high availability if and when you promote it when promoted read replicas are automatically configured with backups configuring a read replica for high availability is done the same way as for a primary instance for more information see configuring the instance for high availability recreate additional replicas if you promote a replica to become a primary instance you need to recreate any other replicas of the former primary instance for example consider the configuration referenced earlier and repeated here region a us central1 has a high availability primary instance db a 0 region b us west1 has a cross region replica db b 1 of db a 0 region c us east1 has a cross region replica db c 1 of db a 0 if the primary instance db a 0 becomes unavailable you can promote the replica in region b to become the primary to again have additional replicas in regions a and c delete the old instances the former primary instance in a and the replica in c and create new read replicas from the new primary instance in b note you need to use different names for the new replicas the promoted replica retains its original name the resulting configuration would be region a us central1 now has a cross region replica db a 1 region b us west1 now has the primary instance db b 1 region c us east1 now has a new cross region replica db c 2 send feedback except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 licen...