La replicación entre centros de datos de AlloyDB Omni te permite crear clústeres e instancias de bases de datos secundarios a partir de un clúster de base de datos principal para que los recursos estén disponibles en diferentes centros de datos en caso de una interrupción en el centro de datos principal. Estos clústeres de bases de datos secundarios funcionan como copias de los recursos de tu clúster de bases de datos principal.
Los conceptos clave de esta página incluyen los siguientes:
Clúster de base de datos principal. Es un clúster de base de datos de lectura y escritura en un solo centro de datos.
Clúster de base de datos secundario. Un clúster de base de datos de solo lectura en un centro de datos diferente del principal, que se replica del clúster de base de datos principal de forma asíncrona.
En caso de que falle un clúster de base de datos principal de AlloyDB Omni, puedes promover un clúster de base de datos secundario a un clúster de base de datos principal.
Beneficios
Entre los beneficios de la replicación entre centros de datos en AlloyDB Omni, se incluyen los siguientes:
Recuperación ante desastres: En caso de que el centro de datos del clúster de base de datos principal deje de estar disponible, puedes promover los recursos de AlloyDB Omni en otro centro de datos para atender las solicitudes.
Datos distribuidos geográficamente. Distribuir los datos geográficamente los acerca a ti y disminuye la latencia de lectura.
Balanceo de cargas geográfico: En caso de conexiones lentas o sobrecargadas en un centro de datos, puedes enrutar el tráfico a otro centro de datos.
Se mejoró el rendimiento de lectura. Esto hace que los recursos de AlloyDB Omni estén disponibles más cerca del centro de datos de tu aplicación.
Cambio Puedes realizar un cambio para probar la configuración de recuperación ante desastres o migrar tu carga de trabajo.
Cómo trabajar con la replicación entre centros de datos
Trabajar con la replicación entre centros de datos de AlloyDB Omni implica las siguientes tareas:
Promueve un clúster de base de datos secundaria.
Puedes leer los datos en un clúster de base de datos secundario, pero no puedes escribir en él hasta que lo promuevas a un clúster de base de datos principal.
Existen dos situaciones comunes en las que se asciende tu clúster de base de datos secundaria a un clúster de base de datos principal:
Migración del centro de datos. Realiza una migración planificada de los recursos de AlloyDB Omni desde su centro de datos principal a otro centro de datos.
Recuperación ante desastres: Activar rápidamente los recursos de AlloyDB Omni en un centro de datos secundario en caso de que los recursos del centro de datos principal dejen de estar disponibles Debido al retraso en la replicación, es posible que se pierdan algunos datos.
Si se promueve un clúster de base de datos secundario, se convierte en un clúster de base de datos independiente completamente funcional con capacidades de lectura y escritura. El clúster de base de datos promocionado ya no replica los datos del clúster de base de datos principal con el que estaba asociado antes.
Cambio.
El cambio te permite revertir los roles de tu clúster de base de datos principal y secundario. Puedes realizar un cambio para probar la configuración de recuperación ante desastres o migrar tu carga de trabajo. Cuando completes el cambio, se revertirá la dirección de replicación.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-03 (UTC)"],[[["\u003cp\u003eAlloyDB Omni cross-data-center replication enables the creation of secondary, read-only database clusters in different data centers, serving as copies of the primary cluster for improved availability and disaster recovery.\u003c/p\u003e\n"],["\u003cp\u003eThis setup provides benefits such as disaster recovery, geographically distributed data, geographic load balancing, and improved read performance by making data accessible in multiple locations.\u003c/p\u003e\n"],["\u003cp\u003eSecondary database clusters can be promoted to primary, read-write clusters in the event of a primary data center outage or for planned data center migrations.\u003c/p\u003e\n"],["\u003cp\u003eSwitchover is supported, which allows the reversal of the primary and secondary database cluster roles for testing disaster recovery setups or performing workload migrations.\u003c/p\u003e\n"],["\u003cp\u003eWorking with cross-data-center replication includes creating secondary database clusters, viewing secondary database clusters, promoting secondary database clusters, and switching over the roles of primary and secondary.\u003c/p\u003e\n"]]],[],null,["# About cross-data-center replication\n\nSelect a documentation version: Current (16.8.0)keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [16.8.0](/alloydb/omni/16.8.0/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [16.3.0](/alloydb/omni/16.3.0/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [15.12.0](/alloydb/omni/15.12.0/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [15.7.1](/alloydb/omni/15.7.1/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [15.7.0](/alloydb/omni/15.7.0/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [15.5.5](/alloydb/omni/15.5.5/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [15.5.4](/alloydb/omni/15.5.4/docs/cross-data-center-replication/about-cross-data-center-replication)\n- [15.5.2](/alloydb/omni/15.5.2/docs/cross-data-center-replication/about-cross-data-center-replication)\n\n\u003cbr /\u003e\n\nThis page provides an overview of AlloyDB Omni cross-data-center replication.\n\n\u003cbr /\u003e\n\nAlloyDB Omni cross-data-center replication lets you create secondary database\nclusters and instances from a primary database cluster to make the resources available in\ndifferent data centers, in the event of an outage in the primary data center. These\nsecondary database clusters function as copies of your primary database cluster resources.\n\nKey concepts in this page include the following:\n\n- **Primary database cluster.** A read-write database cluster in a single data center.\n- **Secondary database cluster.** A read-only database cluster in a different data center than the primary, that replicates from the primary database cluster asynchronously. In the event of a failure of an AlloyDB Omni primary database cluster, you can promote a secondary database cluster to a primary database cluster.\n\nBenefits\n--------\n\nThe benefits of cross-data-center replication on AlloyDB Omni include the\nfollowing:\n\n- **Disaster recovery.** In the event the primary database cluster's data center becomes\n unavailable, you can promote AlloyDB Omni resources in another data center\n to serve requests.\n\n- **Geographically distributed data.** Distributing the data geographically brings\n the data closer to you and decreases read latency.\n\n- **Geographic load balancing.** In the event of slow or overloaded connections\n in one data center, you can route traffic to another data center.\n\n- **Improved read performance.** It makes AlloyDB Omni resources\n available closer to your application's data center.\n\n- **Switchover.** You can perform a switchover for testing your disaster recovery setup or performing migration of your workload.\n\nHow to work with cross-data-center replication\n----------------------------------------------\n\nWorking with AlloyDB Omni cross-data-center replication involves the following tasks:\n\n- [**Create a secondary database cluster.**](/alloydb/omni/current/docs/cross-data-center-replication/work-with-cross-data-center-replication#secondary-db-cluster-instance)\n A secondary database cluster is a continuously updated copy of your AlloyDB Omni\n primary cluster.\n\n- [**View a secondary database cluster.**](/alloydb/omni/current/docs/cross-data-center-replication/work-with-cross-data-center-replication#view-secondary-cluster)\n After you create a secondary database cluster, you can view its status and replication status.\n\n- [**Promote a secondary database cluster.**](/alloydb/omni/current/docs/cross-data-center-replication/work-with-cross-data-center-replication#promote-secondary-cluster)\n You can read the data in a secondary database cluster but cannot write to it until you promote it to a primary database cluster.\n\n There are two common scenarios for promoting your secondary database cluster to a primary database\n cluster:\n - **Data center migration.** Perform a planned migration of the AlloyDB Omni\n resources from their primary data center to another data center.\n\n - **Disaster recovery.** Rapidly activate the AlloyDB Omni resources\n in a secondary data center in the event that the resources in the primary data center\n become unavailable. Due to replication lag, some data loss might occur.\n\n Promoting a secondary database cluster converts it to a standalone fully functional database cluster with read and write capabilities. The promoted database cluster no longer replicates the data from the primary database cluster it was formerly associated with.\n- [**Switchover.**](/alloydb/omni/current/docs/cross-data-center-replication/work-with-cross-data-center-replication#switchover-secondary)\n Switchover lets you reverse the roles of your primary and secondary database cluster. You can perform a switchover for testing your disaster recovery setup or performing migration of your workload. When you complete the switchover, the direction of replication is reversed.\n\nWhat's next\n-----------\n\n- [Work with cross-data-center replication](/alloydb/omni/current/docs/cross-data-center-replication/work-with-cross-data-center-replication)"]]