기본 리전에 중단이 발생하면 사용자가 중단을 식별하고 보조 리전에 있는 보도 디스크를 사용하여 장애 조치하고 워크로드를 다시 시작해야 합니다. 비동기 복제는 중단 모니터링을 제공하지 않습니다. RPO 측정항목, 상태 점검, 애플리케이션 특정 측정항목을 사용하고 Cloud Customer Care 연락을 통해 중단을 식별할 수 있습니다.
기본 리전에서 보조 리전으로 장애 조치를 수행한 후에는 보조 리전이 기본 리전으로 작동합니다.
중단 또는 재해가 해결된 다음에는 원래 보조 리전(작동 중인 기본 리전)에서 원래 기본 리전으로 복제를 시작하도록 장애 복구를 시작할 수 있습니다. 선택적으로 이 프로세스를 반복하여 워크로드를 다시 처음 기본 리전으로 이동할 수 있습니다. 엄밀히 말해서 워크로드를 원래 기본 리전으로 다시 이동할 필요는 없지만 지역성 또는 사용 가능한 리소스와 같은 재해 복구 요구사항에 따라 이를 수행할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-19(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,["*** ** * ** ***\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\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\nSingle 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\nConsistency 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\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\nSingle 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\nConsistency 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- Learn how to [monitor Asynchronous Replication performance](/compute/docs/disks/async-pd/performance)."]]
