Melakukan rollback resource yang dimigrasikan ke Load Balancer Aplikasi klasik
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan cara melakukan rollback resource yang dimigrasikan dari infrastruktur Load Balancer Aplikasi eksternal global ke infrastruktur Load Balancer Aplikasi klasik.
Gunakan urutan berikut untuk melakukan rollback resource yang dimigrasikan dalam waktu 90 hari setelah mengubah skema load balancing-nya:
Kembalikan aturan penerusan.
Kembalikan bucket backend.
Kembalikan semua layanan backend yang terpasang ke aturan penerusan.
Untuk melakukan rollback layanan backend ke skema load balancing EXTERNAL, Anda harus
melakukan rollback aturan penerusan terlebih dahulu.
Untuk mengikuti dokumen ini, Anda harus memiliki izin untuk mengelola komponen load balancer. Pastikan Anda memiliki peran Compute Network Admin (roles/compute.networkAdmin).
Untuk informasi lebih lanjut, lihat halaman berikut:
Untuk mengirim beberapa traffic jaringan Load Balancer Aplikasi klasik ke bucket backend, ubah status migrasi bucket backend menjadi TEST_BY_PERCENTAGE dan tetapkan persentasenya.
Anda dapat memeriksa metrik load balancer untuk memverifikasi bahwa keseluruhan keseimbangan permintaan cocok dengan kecepatan rollback yang dikonfigurasi.
Ubah status migrasi bucket backend menjadi PREPARE.
Di panel Kelola migrasi, untuk Perubahan status, pilih Uji
semua traffic. Artinya, semua permintaan masih dikirim ke
infrastruktur Load Balancer Aplikasi eksternal global.
Klik Simpan.
Tunggu beberapa saat (setidaknya enam menit) hingga resource dimigrasikan. Kolom Status berubah menjadi
Menguji semua traffic dan Aktivitas skema menjadi EXTERNAL: 0%
EXTERNAL_MANAGED: 100%.
Klik Kelola migrasi lagi.
Di panel Kelola migrasi, untuk Perubahan status, pilih Uji
berdasarkan persentase.
Untuk Testing percentage, masukkan 90. Artinya, 90 persen permintaan terus diarahkan ke infrastruktur Load Balancer Aplikasi eksternal global dan 10 persen permintaan lainnya akan diarahkan ke infrastruktur Load Balancer Aplikasi klasik untuk pengujian.
Klik Simpan.
Tunggu beberapa saat (setidaknya enam menit) hingga resource
siap. Kolom Status berubah menjadi Pengujian menurut %, Rasio
migrasi menjadi 90%, dan Aktivitas skema akan menjadi EXTERNAL: 10%
EXTERNAL_MANAGED: 90%.
Setelah siap, resource akan mengirimkan 90% permintaan ke infrastruktur Load Balancer Aplikasi eksternal global dan 10% permintaan ke infrastruktur Load Balancer Aplikasi klasik.
Uji load balancer untuk memastikan bahwa permintaan ditayangkan seperti yang diharapkan.
Masukkan http://IP_ADDRESS di kolom URL browser web. Anda akan melihat pesan Page served
from: lb-backend-example-xxxx.
Anda dapat mengulangi langkah-langkah ini untuk secara bertahap mengurangi persentase traffic yang dikirim ke infrastruktur Load Balancer Aplikasi eksternal global.
Proses rollback layanan backend selesai saat Anda mengirim semua traffic ke Load Balancer Aplikasi klasik. Kolom Status akan menjadi
Pengujian menurut %, Rasio migrasi ditetapkan ke 0%, dan Aktivitas
skema akan menjadi EXTERNAL: 100% EXTERNAL_MANAGED: 0%.
gcloud
Ubah skema layanan backend menjadi EXTERNAL dan status
migrasi menjadi TEST_ALL_TRAFFIC.
Untuk mengirim beberapa traffic jaringan Load Balancer Aplikasi klasik ke
layanan backend, ubah status migrasi layanan backend menjadi
TEST_BY_PERCENTAGE dan tetapkan persentasenya.
Anda dapat memeriksa metrik load balancer untuk memverifikasi bahwa keseluruhan keseimbangan permintaan cocok dengan kecepatan rollback yang dikonfigurasi.
Ubah status migrasi layanan backend menjadi PREPARE.
[[["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-18 UTC."],[],[],null,["# Roll back migrated resources to classic Application Load Balancer\n\nThis document describes how to roll back the [migrated\nresources](/load-balancing/docs/https/migrate-from-classic-global) from the\nglobal external Application Load Balancer infrastructure to the classic Application Load Balancer\ninfrastructure.\n\nUse the following order to roll back a migrated resource within 90 days of\nchanging its load balancing scheme:\n\n1. Roll back the forwarding rule.\n2. Roll back the backend buckets.\n3. Roll back all the backend services attached to the forwarding rule.\n\nTo roll back a backend service to the `EXTERNAL` load balancing scheme, you must\nfirst roll back the forwarding rule.\n\nBefore you begin\n----------------\n\nBefore you roll back migrated resources, make sure that you've [migrated the\nclassic Application Load Balancer resources to the global external Application Load Balancer\ninfrastructure](/load-balancing/docs/https/migrate-from-classic-global) and\nchanged their load balancing schemes to `EXTERNAL_MANAGED`. Remember, only\nresources that were migrated to the `EXTERNAL_MANAGED` scheme from the\n`EXTERNAL` scheme in the last 90 days can be rolled back.\n\nYou must also remove any [advanced traffic management\nfeatures](/load-balancing/docs/https/traffic-management-global) configured on\nthe resources before you start the rollback process.\n\n### Permissions\n\nTo follow this document, you must have permissions to manage load balancer\ncomponents. Make sure you have the [Compute Network Admin\nrole](/compute/docs/access/iam#compute.networkAdmin)\n(`roles/compute.networkAdmin`).\n\nFor more information, see the following pages:\n\n- [Roles and permissions](/load-balancing/docs/access-control)\n- [IAM Conditions for forwarding rules](/load-balancing/docs/access-control/iam-conditions)\n\nRoll back the forwarding rule\n-----------------------------\n\n### Console\n\nTo roll back forwarding rules, use the gcloud CLI.\n\n### gcloud\n\n1. Change the load balancing scheme of the forwarding rule from\n `EXTERNAL_MANAGED` to `EXTERNAL`.\n\n If a backend bucket is attached to the forwarding rule, skip this step and\n [roll back the backend bucket](#roll-back-backend-bucket). \n\n ```\n gcloud compute forwarding-rules update web-map-http-forwarding-rule \\\n --load-balancing-scheme=EXTERNAL \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n2. Optional: Check the logs of the forwarding rule. You see the load\n balancing scheme has changed to `EXTERNAL`.\n\nRoll back the backend bucket\n----------------------------\n\n### Console\n\nTo roll back backend buckets, use the gcloud CLI.\n\n### gcloud\n\n1. Change the scheme of the backend bucket to `EXTERNAL` and the migration\n state to `TEST_ALL_TRAFFIC`.\n\n ```\n gcloud compute forwarding-rules update web-map-http-forwarding-rule \\\n --load-balancing-scheme=EXTERNAL \\\n --external-managed-backend-bucket-migration-state=TEST_ALL_TRAFFIC \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n2. To send some classic Application Load Balancer network traffic to\n the backend bucket, change the migration state of the backend bucket to\n `TEST_BY_PERCENTAGE` and set the percentage.\n\n ```\n gcloud compute forwarding-rules update web-map-http-forwarding-rule \\\n --external-managed-backend-bucket-migration-state=TEST_BY_PERCENTAGE \\\n --external-managed-backend-bucket-migration-testing-percentage=10 \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n\n You can check the [load balancer's\n metrics](/load-balancing/docs/https/https-logging-monitoring#monitoring_metrics)\n to verify that the overall balance of requests matches your configured\n rollback rate.\n3. Change the migration state of the backend bucket to `PREPARE`.\n\n ```\n gcloud compute forwarding-rules update web-map-http-forwarding-rule \\\n --external-managed-backend-bucket-migration-state=PREPARE \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n4. Change the migration state of the backend bucket to its pre-migration state.\n\n ```\n gcloud compute forwarding-rules update web-map-http-forwarding-rule \\\n --clear-external-managed-backend-bucket-migration-state \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n\nRoll back the backend service\n-----------------------------\n\n### Console\n\n**Send traffic to the classic Application Load Balancer infrastructure**\n\n1. In the **Backend services** section, for **`web-backend-service`** , verify the following, and click **Revert** .\n - **Status** : **Migrated**\n - **Migration rate** : **100%**\n - **Scheme activity** : **EXTERNAL: 0% EXTERNAL_MANAGED: 100%**\n2. In the **Manage migration** pane, for **Status change** , select **Test\n all traffic**. This means that all requests are still sent to the global external Application Load Balancer infrastructure.\n3. Click **Save** .\n Wait for some time (at least six minutes) for the\n resource to be migrated. The **Status** column changes to\n **Testing all traffic** and **Scheme activity** to **EXTERNAL: 0%\n EXTERNAL_MANAGED: 100%**.\n\n4. Click **Manage migration** again.\n\n5. In the **Manage migration** pane, for **Status change** , select **Test\n by percentage**.\n\n6. For **Testing percentage** , enter `90`. This means that 90 percent of\n requests continue to go to the global external Application Load Balancer infrastructure\n and the remaining 10 percent of requests will go to the\n classic Application Load Balancer infrastructure for testing.\n\n7. Click **Save**.\n\n Wait for some time (at least six minutes) for the resource to be\n ready. The **Status** column changes to **Testing by %** , **Migration\n rate** to **90%** , and **Scheme activity** will be **EXTERNAL: 10%\n EXTERNAL_MANAGED: 90%**.\n\n After the resource is ready, it sends 90% of requests to the\n global external Application Load Balancer infrastructure and 10% of requests to\n the classic Application Load Balancer infrastructure.\n8. Test the load balancer to ensure that requests are being served as\n expected.\n\n Enter `http://`\u003cvar translate=\"no\"\u003eIP_ADDRESS\u003c/var\u003e in the\n address bar of the web browser. You should see the `Page served\n from: lb-backend-example-xxxx` message.\n9. You can repeat these steps to progressively decrease the percentage of\n traffic sent to the global external Application Load Balancer infrastructure.\n\n The backend service rollback process is complete when you are sending all\n traffic to the classic Application Load Balancer. The **Status** column will be\n **Testing by %** , **Migration rate** set to **0%** , and **Scheme\n activity** will be **EXTERNAL: 100% EXTERNAL_MANAGED: 0%**.\n\n### gcloud\n\n1. Change the scheme of the backend service to `EXTERNAL` and the migration\n state to `TEST_ALL_TRAFFIC`.\n\n ```\n gcloud compute backend-services update web-backend-service \\\n --load-balancing-scheme=EXTERNAL \\\n --external-managed-migration-state=TEST_ALL_TRAFFIC \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n2. To send some classic Application Load Balancer network traffic to\n the backend service, change the migration state of the backend service to\n `TEST_BY_PERCENTAGE` and set the percentage.\n\n ```\n gcloud compute backend-services update web-backend-service \\\n --external-managed-migration-state=TEST_BY_PERCENTAGE \\\n --external-managed-migration-testing-percentage=10 \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n\n You can check the [load balancer's\n metrics](/load-balancing/docs/https/https-logging-monitoring#monitoring_metrics)\n to verify that the overall balance of requests matches your configured\n rollback rate.\n3. Change the migration state of the backend service to `PREPARE`.\n\n ```\n gcloud compute backend-services update web-backend-service \\\n --external-managed-migration-state=PREPARE \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n4. Change the migration state of the backend service to its pre-migration state.\n\n ```\n gcloud compute backend-services update web-backend-service \\\n --clear-external-managed-migration-state \\\n --global\n ```\n\n Wait for some time (at least six minutes).\n5. After rolling back the backend service, check its log. You see the load\n balancing scheme has changed to `EXTERNAL`."]]
