/alibabacloud-ecs-disaster-recovery-snapshot

name: alibabacloud-ecs-disaster-recovery-snapshot
description: |
  Alibaba Cloud ECS snapshot-based cross-AZ disaster recovery skill. Two scenarios:
  Scenario A (Full Instance Recovery): Recover ECS instance to a different AZ via snapshots —
  multi-disk uses snapshot consistency group for crash consistency, creates full custom image
  (system + data disks), launches new instance in target AZ; single-disk uses individual snapshot.
  Scenario B (Disk-Level Recovery): Snapshot specific disks from source instance,
  create new disks from snapshots, and attach them to an existing target instance.
  Triggers: cross-AZ disaster recovery, cross-zone backup, ECS snapshot recovery,
  snapshot backup, DR recovery, create instance from snapshot in another AZ,
  attach disk snapshot to another instance, create instance replica via snapshot.
  可用区灾备恢复、跨可用区备份、ECS 快照恢复、快照备份、灾备恢复、
  在另一个可用区从快照创建实例、把盘快照挂载到其他实例、用快照在另一个可用区创建实例副本、
  恢复这台机器到另一个可用区、跨实例磁盘备份。
  Note: This is "backup" not "migration" — the original instance remains untouched.

ECS Snapshot-Based Disaster Recovery Backup

This skill provides snapshot-based disaster recovery **backup** for ECS instances. The original instance and all its resources remain untouched — this is a **backup operation, not a migration**. It supports two scenarios:

• **Scenario A — Full Instance Backup**: Backs up an entire ECS instance to a different availability

zone. **Multi-disk** (system + ≥1 data disk): uses **snapshot consistency group** (CreateSnapshotGroup) for cross-disk consistency, then creates a **full image** (system + data disks) — run-instances directly from the image, data disks auto-restored. **Single-disk** (system only): uses individual snapshot (create-snapshot) + system-disk-only image. Use when: AZ failure, datacenter backup, full instance cloning.

• **Scenario B — Disk-Level Backup**: Takes a snapshot of specific disk(s) from a source instance,

creates new disk(s) from the snapshot, and attaches them to an existing target instance. Use when: back up specific data disk to another instance, cross-instance disk backup, or attach source disk data to an existing DR instance.

Scenario Detection

At the start of the workflow, determine which scenario applies based on the user's intent:

| User Intent | Scenario | | ---------------------------------------------------------------------------------- | ----------- | | "back up this instance to another AZ" / "create a DR instance" | **A** | | "snapshot a disk and attach to another instance" / "mount disk to target instance" | **B** | | Ambiguous — ask the user to clarify | Ask |

Once the scenario is determined, follow the corresponding workflow below.

Prerequisites

> **Pre-check: Aliyun CLI >= 3.3.3 required** > > 1. Run `aliyun version` to check if CLI is installed and its version. > 2. If CLI is **not installed** (command not found): inform the user and ask whether to install it. > Only after user confirmation, download the installer with `curl -fsSL --connect-timeout 10 --max-time 60 https://aliyuncli.alicdn.com/setup.sh -o /tmp/aliyun_cli_setup.sh`, > then run `bash /tmp/aliyun_cli_setup.sh` to execute the downloaded script. > 3. If CLI is installed but **version < 3.3.3**: inform the user of the current version and the minimum requirement, > then ask whether to upgrade. Only after user confirmation, run the upgrade command. > 4. If CLI is installed and **version >= 3.3.3**: proceed directly, no action needed. > > **IMPORTANT: Do NOT upgrade Aliyun CLI without explicit user confirmation. Only prompt for upgrade when the version check fails.**

> **Pre-check: Aliyun CLI plugin update required** > [MUST] run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation. > [MUST] run `aliyun plugin update` to ensure that any existing plugins on your local machine are always up-to-date.

> **Pre-check: Alibaba Cloud Credentials Required** > > **Security Rules:** > > - **NEVER** read, echo, or print AK/SK values (e.g., `echo $ALIBABA_CLOUD_ACCESS_KEY_ID` is FORBIDDEN) > - **NEVER** ask the user to input AK/SK directly in the conversation or command line > - **NEVER** use `aliyun configure set` with literal credential values > - **NEVER** export or set AK/SK as environment variables in commands (e.g. `export ALIBABA_CLOUD_ACCESS_KEY_ID=...` is FORBIDDEN). Always use `aliyun` CLI directly — it uses local credentials automatically. > - **ONLY** use `aliyun configure list` to check credential status > > ```bash > aliyun configure list > ``` > > Check the output for a valid profile (AK, STS, or OAuth identity). > > **If no valid profile exists, STOP here.** > > 1. Obtain credentials from [Alibaba Cloud Console](https://ram.console.aliyun.com/manage/ak) > 2. Configure credentials **outside of this session** (via `aliyun configure` in terminal or environment variables in shell profile) > 3. Return and re-run after `aliyun configure list` shows a valid profile

CLI Command Standards

> **[MUST]** All CLI commands MUST follow these standards to avoid parameter errors.

| Rule | Correct | Incorrect | | --------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------- | | **Command name** | `describe-instances` (kebab-case) | `DescribeInstances` (PascalCase) | | **User agent** | Always include `--user-agent AlibabaCloud-Agent-Skills/alibabacloud-ecs-disaster-recovery-snapshot/{session-id}` | Missing user-agent or session-id | | **Region parameter** | Use `--biz-region-i