Promosi berarti instance Cloud SQL tujuan terputus dari
sumber, dan dipromosikan dari instance replika ke instance utama.
Untuk migrasi berkelanjutan, Anda dapat memulai proses promosi
setelah tiba waktunya untuk memindahkan operasi baca dan tulis ke tujuan.
Untuk migrasi satu kali, instance Cloud SQL siap segera setelah proses dump dan pemuatan selesai,
dan promosi yang dipanggil pengguna tidak diperlukan.
Untuk mempromosikan migrasi tanpa kehilangan informasi, ikuti langkah-langkah berikut:
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 replika yang lama karena instance tujuan Cloud SQL 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.
(Opsional) Untuk sumber yang menggunakan ekstensi pg_cron:
Ekstensi pg_cron (atau setelan cron apa pun yang terkait dengan ekstensi)
tidak dimigrasikan oleh Database Migration Service, tetapi didukung di
tujuan Cloud SQL untuk PostgreSQL. Jika menggunakan ekstensi pg_cron di database sumber, Anda dapat menginstalnya ulang di instance tujuan.
Aplikasi kini dapat terhubung ke instance Cloud SQL dan tugas migrasi dapat dihapus dengan aman.
Tugas migrasi yang telah gagal atau dihentikan secara manual selama fase CDC dapat
dipromosikan, tetapi hal ini dapat berarti adanya kesenjangan antara data di sumber dan
tujuan.
[[["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 a migration job turns the destination Cloud SQL instance from a replica into a primary instance, disconnecting it from the source.\u003c/p\u003e\n"],["\u003cp\u003eFor continuous migrations, promotion should be initiated after the decision to switch reads and writes to the destination has been made, while one-time migrations are ready after the dump and load process completes.\u003c/p\u003e\n"],["\u003cp\u003eBefore promoting, it's crucial to stop all writes and connections to the source database and wait for the replication delay to reach zero to avoid data loss.\u003c/p\u003e\n"],["\u003cp\u003eThe promotion process can be initiated in the Migration job details page by clicking "Promote," and once started, it cannot be stopped or reversed.\u003c/p\u003e\n"],["\u003cp\u003eIf the \u003ccode\u003epg_cron\u003c/code\u003e extension is used in the source database, it is not migrated by Database Migration Service, but can be reinstalled on the destination instance after promotion.\u003c/p\u003e\n"]]],[],null,["# Promote a migration\n\n\u003cbr /\u003e\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 \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/promote-migration \"View this page for the PostgreSQL to AlloyDB version of Database Migration Service.\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nPromotion means that the destination Cloud SQL 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.\nFor one-time migrations, the Cloud SQL instance is ready as soon as the dump and load is complete, and user-invoked promotion isn't required.\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. Immediately after transitioning to the CDC phase, depending on the size of the dump, there may be a long replication delay because the Cloud SQL destination instance catches up on changes that occurred during the dump and\n 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. (Optional) **For sources that use the `pg_cron` extension** : The [`pg_cron`](/sql/docs/postgres/extensions#pg_cron) extension (or any `cron` settings associated with the extension) isn't migrated by Database Migration Service, but it is supported in Cloud SQL for PostgreSQL destinations. If you use the `pg_cron` extension in your source databases, you can re-install it on your destination instance.\n11. The application can now be connected to the Cloud SQL instance and the migration job can be safely deleted.\n\nMigration jobs that have failed or were manually stopped during CDC phase can be promoted, but this may mean a gap between the data on the source and the destination."]]
