Replikasi lintas pusat data AlloyDB Omni memungkinkan Anda membuat cluster dan instance database sekunder dari cluster database utama untuk menyediakan resource di pusat data yang berbeda, jika terjadi gangguan di pusat data utama. Cluster database sekunder ini berfungsi sebagai salinan resource cluster database utama Anda.
Konsep utama di halaman ini meliputi:
Cluster database utama. Cluster database baca-tulis di satu pusat data.
Cluster database sekunder. Cluster database hanya baca di pusat data yang berbeda dengan cluster utama,
yang mereplikasi dari cluster database utama secara asinkron.
Jika terjadi kegagalan pada cluster database utama AlloyDB Omni, Anda dapat
mempromosikan cluster database sekunder menjadi cluster database utama.
Manfaat
Manfaat replikasi lintas pusat data di AlloyDB Omni mencakup hal-hal berikut:
Pemulihan dari bencana. Jika pusat data cluster database utama menjadi tidak tersedia, Anda dapat mempromosikan resource AlloyDB Omni di pusat data lain untuk melayani permintaan.
Data yang didistribusikan secara geografis. Mendistribusikan data secara geografis akan mendekatkan data kepada Anda dan mengurangi latensi baca.
Load balancing geografis. Jika terjadi koneksi yang lambat atau kelebihan beban di satu pusat data, Anda dapat merutekan traffic ke pusat data lain.
Peningkatan performa baca. Hal ini membuat resource AlloyDB Omni tersedia lebih dekat dengan pusat data aplikasi Anda.
Pengalihan. Anda dapat melakukan pengalihan untuk menguji penyiapan pemulihan dari bencana atau melakukan migrasi beban kerja.
Cara menggunakan replikasi lintas pusat data
Bekerja dengan replikasi lintas pusat data AlloyDB Omni melibatkan tugas-tugas berikut:
Mempromosikan cluster database sekunder.
Anda dapat membaca data di cluster database sekunder, tetapi tidak dapat menulis ke cluster tersebut hingga Anda mempromosikannya ke cluster database utama.
Ada dua skenario umum untuk mempromosikan cluster database sekunder Anda ke cluster database
primer:
Migrasi pusat data. Lakukan migrasi terencana resource AlloyDB Omni
dari pusat data utamanya ke pusat data lain.
Pemulihan dari bencana. Mengaktifkan resource AlloyDB Omni dengan cepat
di pusat data sekunder jika resource di pusat data utama
menjadi tidak tersedia. Karena jeda replikasi, beberapa data mungkin hilang.
Mempromosikan cluster database sekunder akan mengonversinya menjadi cluster database mandiri yang berfungsi penuh dengan kemampuan baca dan tulis. Cluster database yang dipromosikan tidak lagi mereplikasi data dari cluster database utama yang sebelumnya terkait.
Pengalihan.
Pengalihan memungkinkan Anda membalikkan peran cluster database primer dan sekunder. Anda dapat melakukan pengalihan untuk menguji penyiapan pemulihan dari bencana atau melakukan migrasi beban kerja. Saat Anda menyelesaikan pengalihan, arah replikasi akan dibalik.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-17 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)"]]
