You need to enable JavaScript to run this app.
Code Pipeline

Code Pipeline

Copy page
Download PDF
Multi-cloud disaster recovery
Dedicated line failover in multi-cloud disaster recovery
Copy page
Download PDF
Dedicated line failover in multi-cloud disaster recovery
Code Pipeline now offers disaster recovery pipeline templates to help you quickly implement service failover in disaster recovery scenarios and reduce the risk of business interruption. This article describes how to create and set up the Dual-Cloud Dual-Active Dedicated Line Failure Disaster Recovery Switchover pipeline.​
Introduction to scenarios​
This scenario simulates an active-active dual-cloud environment in which the dedicated line of fails. All traffic is switched to a third-party cloud using the Code Pipeline service.​
tip​
In dual-cloud active-active scenarios, after the dedicated line failure in is restored, refer to Dedicated line failure recovery in multi-cloud disaster recovery for the process of switching part of the traffic back to .​
Prerequisites​
  • Workloads for the dual-cloud, active-active business application have been created and deployed. For instructions on creating a workload, see Workload.​
  • Create a cloud scheduling GTM GTM controls changes in the direction of data traffic before and after a switch. For the GTM operation process, see GTM Cloud Scheduling Quick Start.​
Procedure​
Step 1: Create a pipeline​
  1. Log in to the Code Pipeline console.​
  1. In the left navigation bar, select workspace. On the workspace page, click the name of the desired workspace to access it.​
  1. Click Create pipeline. On the Select Pipeline templates page, select Disaster recovery > Active-active across two clouds—dedicated line failure disaster recovery switchover.​
4 Click confirm.​
Step 2: Expand an application​
After a failure occurs on the cross-cloud dedicated line, the application cannot access the third-party cloud database. Global traffic must be redirected to the third-party cloud, so the third-party cloud application needs to be expanded to handle the increased traffic. In this scenario, the number of replicas for the application workload in the third-party cloud is increased from 2 to 4.​
Step 3: Switch global traffic to the third-party cloud​
By disabling the service address of the dedicated connection, all traffic will be redirected to the third-party cloud.​
  1. In the GTM instance list, select the GTM instance that controls this traffic switch.​
  1. In Address Pool, select the address pool where the dedicated line service is located.​
  1. In address online mode, set the address of the third-party cloud dedicated connection to always enabled, and set the address of the dedicated connection to always disabled.​
Step 4: Verify the service recovery​
Use the following actions to set up the approval workflow for verifying the successful switching of the dedicated line. During pipeline execution, after verifying that the business application is running normally, click Pass in the pipeline to proceed to the next step.​
tip​
This step triggers the approval workflow for verifying the dedicated line switch. The actual verification actions must be performed manually by an instructor.​
  1. Select the approval method in Approval Method.​
  1. In Approver, select the personnel who need to verify dedicated line switching.​
What to do next​
​
Last updated: 2025.09.10 17:37:29