Klik tugas migrasi yang mewakili migrasi yang ingin Anda promosikan. Halaman Detail tugas migrasi akan muncul.
Setelah fase dump penuh selesai dan tugas migrasi berada dalam fase
CDC, opsi untuk promosi akan tersedia.
Segera setelah bertransisi ke fase CDC, bergantung pada ukuran dump, mungkin ada penundaan replikasi yang lama karena instance tujuan AlloyDB untuk PostgreSQL mengejar perubahan yang terjadi selama proses dump dan pemuatan.
Tunggu sampai penundaan replikasi menurun secara signifikan, idealnya dalam
urutan menit atau detik. Penundaan replikasi tersedia untuk ditinjau di
halaman tugas migrasi.
Setelah penundaan replikasi minimum, Anda dapat memulai promosi.
Untuk menghindari kehilangan data, pastikan untuk:
Hentikan semua operasi tulis, skrip yang berjalan, dan koneksi klien ke database
sumber. Periode nonaktif dimulai di sini.
Tunggu hingga penundaan replikasi nol, yang berarti bahwa
tugas migrasi telah memproses semua perubahan yang belum selesai.
Di halaman Detail tugas migrasi, klik Promosikan.
Di jendela Promosikan tugas migrasi?, klik Promosikan.
Tugas migrasi berhenti membaca dari sumber dan substatusnya adalah
Promote in progress. Pada tahap ini, Anda tidak dapat menghentikan atau mengurungkan
proses promosi.
Instance tujuan dipromosikan menjadi instance utama yang dapat ditulis.
Status tugas migrasi adalah Completed.
Aplikasi kini dapat dihubungkan ke instance AlloyDB untuk PostgreSQL dan tugas migrasi dapat dihapus dengan aman.
Saat Anda mempromosikan tugas migrasi yang telah gagal atau dihentikan secara manual selama fase CDC, data di sumber dan
tujuan dapat menjadi tidak konsisten.
[[["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-09-05 UTC."],[[["\u003cp\u003ePromotion of an AlloyDB for PostgreSQL migration job converts the destination instance from a replica to a primary instance, disconnecting it from the source.\u003c/p\u003e\n"],["\u003cp\u003eThe promotion option becomes available after the full dump phase is completed and the migration is in the CDC phase, but it is ideal to wait until the replication delay is minimal.\u003c/p\u003e\n"],["\u003cp\u003eBefore promoting, all writes, scripts, and client connections to the source database must be stopped to prevent data loss.\u003c/p\u003e\n"],["\u003cp\u003eAfter the promotion process is initiated, it cannot be stopped or undone, and the destination instance becomes the primary writable instance.\u003c/p\u003e\n"],["\u003cp\u003ePromoting a failed or manually stopped migration during the CDC phase can result in data inconsistencies between the source and destination databases.\u003c/p\u003e\n"]]],[],null,["# Promote a migration\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/promote-migration \"View this page for the MySQL version of Database Migration Service.\") \\| [PostgreSQL](/database-migration/docs/postgres/promote-migration \"View this page for the PostgreSQL version of Database Migration Service.\") \\| PostgreSQL to AlloyDB\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nPromotion means that the destination AlloyDB for PostgreSQL instance is disconnected from\nthe source, and is promoted from a replica instance to a primary instance.\n\n\nFor continuous migrations, you can initiate the promotion process\nafter it's time to move reads and writes to the destination.\n\nTo promote a migration without loss of information, follow these steps:\n\n1. Go to the [Migration jobs](https://console.cloud.google.com/dbmigration/migrations) page.\n2. Click the migration job that represents the migration that you want to promote. The **Migration job details** page appears.\n\n3. After the full dump phase has completed and the migration job is in CDC phase, the option for promotion is available.\n4.\n Immediately after transitioning to the CDC phase, depending on the size of the dump, there may be a long replication delay because the AlloyDB for PostgreSQL destination instance catches up on changes that occurred during the dump and load.\n\n Wait for the replication delay to trend down significantly, ideally on the\n order of minutes or seconds. The replication delay is available for review on\n the migration job page.\n5. After the replication delay is at a minimum, you can initiate the promotion. To avoid data loss, make sure to:\n 1. **Stop all writes, running scripts, and client connections to the source\n database**. The downtime period begins here.\n 2. Wait until the replication delay is at zero, which means that the migration job has processed all outstanding changes.\n\n | You can promote a migration even if the replication delay isn't at zero. This can reduce the database downtime, but may affect the accuracy of the data in the destination.\n6. In the **Migration job details** page, click **Promote**.\n7. In the **Promote migration job?** window, click **Promote**.\n8. The migration job stops reading from the source and the substatus is `Promote in progress`. At this point, you cannot stop or undo the promotion process.\n9. The destination instance is promoted to a primary writeable instance. The migration job status is `Completed`.\n10. The application can now be connected to the AlloyDB for PostgreSQL instance and the migration job can be safely deleted.\n\nWhen you promote migration jobs that have failed or were manually stopped during CDC phase, data on the source and the\ndestination can be inconsistent."]]
