CloudOps Orchestration Service:Batch clone ECS instances across zones

Overview

A zone is an independent power-and-network partition within a region. For example, China (Qingdao) includes Zone B and Zone C. Deploying across multiple zones improves availability and fault tolerance. For cross-zone failover, load balancing, or data backup, CloudOps Orchestration Service (OOS) lets you batch-clone instances to different zones.

Use cases

Cross-zone cloning supports the following use cases:

1. Failover: Clone an instance to another zone when an exception or error occurs to ensure high availability and business continuity.

2. Load balancing: Distribute workloads across zones by cloning instances, reducing access pressure and improving stability and performance.

3. Data backup and restoration: Clone instances to other zones as backups. If data is lost or damaged in one zone, restore it from the clone in another zone.

4. Application extension: Scale out by cloning instances to additional zones as demand grows.

5. Performance testing and optimization: Clone instances to other zones to test and verify consistent performance across zones without affecting production workloads.

Procedure

1. Log on to the OOS console.

2. In the left-side navigation pane, choose Automated O&M > Public Templates.

3. Search for CloneInstancesAcrossAZ and click Create Execution.

4. On the Create page, configure basic information and click Next Step: Parameter Settings.

5. In the Parameter Settings step, configure the parameters.

6. Select source instances by using one of the available methods: Manually Select Instances, Specify Instance Tags, Specify Resource Group, Upload CSV File, Select All, or Specify Inventory Conditions. Click Next Step: OK.

7. Click Create.

8. View the execution results.