Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Questo documento descrive come eseguire il failover e il failback dei dischi con replica asincrona.
In caso di interruzione del servizio nella regione principale, è tua responsabilità identificare l'interruzione ed eseguire il failover con riavvio del workload utilizzando i dischi secondari nella regione secondaria. La replica asincrona non offre il monitoraggio delle interruzioni. Puoi identificare un'interruzione utilizzando metriche RPO, controlli di integrità, metriche specifiche dell'applicazione e contattando l'assistenza clienti Google Cloud.
A seguito di un failover dalla regione principale a quella secondaria, la regione secondaria agisce ora come regione principale.
Una volta risolta l'interruzione o l'emergenza, puoi avviare il failback per iniziare la replica dalla regione secondaria originale (la regione che agisce ora come principale) alla regione principale originale. Facoltativamente, puoi ripetere il processo per spostare nuovamente il workload nella regione principale originale. Il trasferimento del workload nella regione principale originale non è strettamente necessario, ma può essere eseguito in base ai requisiti di disaster recovery, come la località o le risorse disponibili.
Quando rilevi che si è verificato un disastro, avvia il failover alla regione secondaria. Un failover sposta il workload dalla regione principale alla regione secondaria. Dopo il failover, il disco secondario agisce da disco primario e la regione secondaria agisce come regione principale.
Puoi eseguire il failover di un disco singolo o di tutti i dischi di un gruppo di coerenza.
Disco singolo
Per eseguire il failover di un disco singolo, segui questi passaggi:
Dopo aver risolto un'emergenza, avvia un failback alla regione principale originale. Un failback configura e avvia la replica dal disco che agisce come primario a un nuovo disco secondario nella regione che agisce come secondaria.
Puoi eseguire il failback di un disco singolo o di tutti i dischi di un gruppo di coerenza.
Disco singolo
Per eseguire il failback di un disco singolo, segui questi passaggi:
Crea un disco secondario nella regione che agisce come secondaria. La regione che agisce come secondaria è la regione principale originale.
Avvia la replica dal disco che agisce come primario al nuovo disco secondario.
(Facoltativo) Sposta il workload dalla regione che agisce come principale alla regione principale originale seguendo questi passaggi:
Attendi il completamento della replica iniziale. La replica iniziale è completata quando la metrica disk/async_replication/time_since_last_replication è disponibile in Cloud Monitoring.
Se non visualizzi la metrica RPO in Cloud Explorer, significa che la replica iniziale non è completata.
Consigliato: per evitare la perdita di dati, pianifica un tempo di inattività per il workload e porta offline il workload.
(Facoltativo) Sposta il workload dalla regione che agisce come principale alla regione principale originale seguendo questi passaggi:
Attendi il completamento della replica iniziale. La replica iniziale è completata quando la metrica RPO è disponibile.
Se non visualizzi la metrica RPO in Cloud Explorer, significa che la replica iniziale non è completata.
Consigliato: per evitare la perdita di dati, pianifica un tempo di inattività per il workload e porta offline il workload.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-03 UTC."],[[["\u003cp\u003ePersistent Disk Asynchronous Replication (PD Async Replication) allows for failover to a secondary region in case of an outage in the primary region, though it does not offer outage monitoring.\u003c/p\u003e\n"],["\u003cp\u003eFailover involves stopping replication, creating or using VMs in the secondary region, and attaching the secondary disks to these VMs, making the secondary region the new acting primary region.\u003c/p\u003e\n"],["\u003cp\u003eFailback can be initiated after an outage is resolved, establishing replication from the acting primary region back to the original primary region, with the option to move the workload back to the original primary region.\u003c/p\u003e\n"],["\u003cp\u003eFailover and failback can be performed on either single disks or entire consistency groups, with specific steps for each scenario including creating and attaching disks.\u003c/p\u003e\n"],["\u003cp\u003eWhen failing back, there is an optional step to move the workload back to the original region, which includes waiting for initial replication to complete and temporarily stopping the workload to prevent data loss.\u003c/p\u003e\n"]]],[],null,["# Failover and failback asynchronous disks\n\n*** ** * ** ***\n\nThis document describes how to failover and failback Asynchronous Replication\ndisks.\n\nIn the event of an outage in the primary region, it is your responsibility\nto identify the outage and failover restart your workload using the secondary\ndisks, in the secondary region. Asynchronous Replication doesn't offer outage\nmonitoring. You can identify an outage using\n[RPO metrics](/compute/docs/disks/async-pd/performance#monitor_rpo),\n[health checks](/load-balancing/docs/health-check-concepts),\napplication-specific metrics, and by contacting Cloud Customer Care.\n\nFollowing a failover from the primary region to the secondary region, the\nsecondary region becomes the acting primary region.\n\nAfter the outage or disaster gets resolved, you can initiate failback to start\nreplication from the original secondary region (the acting primary region) to\nthe original primary region. You can optionally repeat the process to move the\nworkload back to the original primary region. Moving the workload back to the\noriginal primary region isn't strictly necessary, but can be done based on\ndisaster recovery requirements, such as locality or available resources.\n\nTo learn more about failover and failback, see\n[About Asynchronous Replication](/compute/docs/disks/async-pd/about#failover_and_failback).\n\nFailover to the secondary region\n--------------------------------\n\nWhen you identify that a disaster has occurred, initiate failover to the\nsecondary region. A failover moves the workload from the primary region to the\nsecondary region. After the failover, the secondary disk is the acting primary\ndisk and the secondary region is the action primary region.\n\nYou can failover a single disk, or all disks in a consistency group. \n\n### Single disk\n\nTo failover a single disk, do the following:\n\n1. [Stop disk replication](/compute/docs/disks/async-pd/manage-replication#stop_replication_for_a_single_disk).\n2. If you don't already have a VM in the same region as the secondary disk, [create one](/compute/docs/instances/create-start-instance).\n3. Attach the secondary disk to the VM:\n\n - For secondary boot disks, [update the boot disk for the VM](/compute/docs/disks/detach-reattach-boot-disk#update_a_boot_disk_for_an_instance).\n - For secondary data disks, [add the disk to the VM](/compute/docs/disks/add-persistent-disk#create_disk).\n\n The secondary disk is now the workload's acting primary disk and the\n secondary region is the acting primary region.\n\n### Consistency group\n\nTo failover a consistency group, do the following:\n\n1. [Stop consistency group replication](/compute/docs/disks/async-pd/manage-replication#stop_replication_for_a_consistency_group).\n2. If you don't already have VMs in the same region as the secondary disks, [create them](/compute/docs/instances/create-start-instance).\n3. Attach the secondary disks to the VMs:\n\n - For secondary boot disks, [update the boot disk for the VM](/compute/docs/disks/detach-reattach-boot-disk#update_a_boot_disk_for_an_instance).\n - For secondary data disks, [add the disk to the VM](/compute/docs/disks/add-persistent-disk#create_disk).\n\nFailback to the original primary region\n---------------------------------------\n\nAfter a disaster has resolved, initiate a failback to the original primary\nregion. A failback configures and starts replication from the acting primary\ndisk to a new secondary disk in the acting secondary region.\n\nYou can failback a single disk, or all disks in a consistency group. \n\n### Single disk\n\nTo failback a single disk, do the following:\n\n1. [Create a secondary disk](/compute/docs/disks/async-pd/configure#create_a_secondary_disk) in the acting secondary region. The acting secondary region is the original primary region.\n2. [Start replication](/compute/docs/disks/async-pd/manage-replication#start_replication) from the acting primary disk to the new secondary disk.\n3. Optional: Move the workload from the acting primary region to the\n original primary region by doing the following:\n\n 1. Wait for the initial replication to complete. The initial replication is complete when the [`disk/async_replication/time_since_last_replication` metric](/compute/docs/disks/async-pd/performance#monitor_rpo) is available in Cloud Monitoring. If you don't see the RPO metric in Cloud Explorer, that means the initial replication isn't complete.\n 2. Recommended: To avoid data loss, schedule downtime for the workload and bring the workload offline.\n 3. [Stop replication](/compute/docs/disks/async-pd/manage-replication#stop_replication_for_a_single_disk).\n 4. Attach the secondary disk to a VM:\n\n - For secondary boot disks, [update the boot disk for the VM](/compute/docs/disks/detach-reattach-boot-disk#update_a_boot_disk_for_an_instance).\n - For secondary data disks, [add the disk to the VM](/compute/docs/disks/add-persistent-disk#create_disk).\n\n The secondary disk is now the workload's primary disk in the original\n primary region.\n 5. Reconfigure replication in the original primary region by doing the\n following:\n\n 1. [Create a new secondary disk](/compute/docs/disks/async-pd/configure#create_a_secondary_disk) in the original secondary region.\n 2. [Start replication](/compute/docs/disks/async-pd/manage-replication#start_replication) from the primary disk to the new secondary disk.\n\n### Consistency group\n\nTo failback a consistency group, do the following:\n\n1. [Create a new consistency group in the acting primary region](/compute/docs/disks/async-pd/manage-consistency-groups#create_a_consistency_group). The acting primary region is the original secondary region.\n2. [Add the acting primary disks to the consistency group](/compute/docs/disks/async-pd/manage-consistency-groups#add_a_disk_to_a_consistency_group)\n3. [Create secondary disks](/compute/docs/disks/async-pd/configure#create_a_secondary_disk) in the acting secondary region that reference the acting primary disks.\n4. [Start replication](/compute/docs/disks/async-pd/manage-replication#start_replication).\n5. Optional: Move the workload from the acting primary region to the\n original primary region by doing the following:\n\n 1. Wait for the initial replication to complete. The initial replication is complete when the [RPO metric is available.](/compute/docs/disks/review-disk-metrics#performance_metrics). If you don't see the RPO metric in Cloud Explorer, that means the initial replication isn't complete.\n 2. Recommended: To avoid data loss, schedule downtime for the workload and bring the workload offline.\n 3. [Stop replication](/compute/docs/disks/async-pd/manage-replication#stop_replication_for_a_consistency_group).\n 4. Attach the secondary disk to VMs:\n\n - For secondary boot disks, [update the boot disk for the VM](/compute/docs/disks/detach-reattach-boot-disk#update_a_boot_disk_for_an_instance).\n - For secondary data disks, [add the disk to the VM](/compute/docs/disks/add-persistent-disk#create_disk).\n\n The secondary disks are now the workload's primary disks in the\n original primary region.\n 5. Reconfigure replication in the original primary region by doing the\n following:\n\n 1. [Add the primary disks to the original consistency group](/compute/docs/disks/async-pd/manage-consistency-groups#add_a_disk_to_a_consistency_group).\n 2. [Create new secondary disks](/compute/docs/disks/async-pd/configure#create_a_secondary_disk) in the original secondary region.\n 3. [Start replication](/compute/docs/disks/async-pd/manage-replication#start_replication).\n\nWhat's next\n-----------\n\n- Learn how to [monitor Asynchronous Replication performance](/compute/docs/disks/async-pd/performance)."]]
