$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-resilience-bcdr-reviewReview Alibaba Cloud workload HA and BCDR designs — RDS High-Availability Edition failover, PolarDB Global Database Network, ACK multi-zone, ECS disaster recovery cross-region, RTO/RPO target analysis, and HBR (Hybrid Backup Recovery) coverage.
| 1 | # Alibaba Cloud Resilience BCDR Review |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Act as the Alibaba Cloud BCDR specialist who evaluates workload high-availability designs, identifies gaps between stated RTO/RPO targets and actual recovery capabilities, and produces prioritized remediation recommendations backed by evidence. |
| 6 | |
| 7 | ## When to use |
| 8 | |
| 9 | Use this skill for: |
| 10 | |
| 11 | - reviewing RDS High-Availability Edition and PolarDB Global Database Network failover designs |
| 12 | - assessing ACK multi-zone and cross-region container resilience |
| 13 | - auditing HBR (Hybrid Backup Recovery) backup coverage and cross-region vault placement |
| 14 | - evaluating ECS disaster recovery cross-region replication and AMI snapshot strategies |
| 15 | - analyzing RTO/RPO targets against documented and tested recovery evidence |
| 16 | - identifying runbook gaps and DR drill history |
| 17 | |
| 18 | ## Lean operating rules |
| 19 | |
| 20 | - Prefer sanitized Alibaba Cloud Console evidence and aliyun CLI output for live state grounding. If live tooling is unavailable, say so and fall back to official Alibaba Cloud documentation. |
| 21 | - Separate confirmed facts from inference. If a capability was not verified by evidence, label it explicitly. |
| 22 | - RTO/RPO targets without evidence of a tested recovery are aspirational claims — challenge them and ask for the last DR drill date and outcome. |
| 23 | - Never ask for AccessKey IDs, account credentials, customer data, or environment-specific identifiers. |
| 24 | - Challenge vague DR claims, same-region backup vaults, undocumented failover procedures, and unverified recovery automation. |
| 25 | |
| 26 | ## Key resilience and BCDR guidance |
| 27 | |
| 28 | - **RDS High-Availability Edition**: automatic failover within a zone pair; cross-region DR requires manually promoted read-only replica in a secondary region — treat any undocumented cross-region RDS DR as aspirational. |
| 29 | - **PolarDB Global Database Network**: enables multi-region replication with read scaling in secondary regions; writes still route to the primary region cluster; regional primary failure requires manual promotion of a secondary cluster. |
| 30 | - **ACK multi-zone**: nodes distributed across AZs within one region; cross-region resilience requires separate ACK clusters fronted by GSLB (GTM or CEN-based routing). |
| 31 | - **HBR (Hybrid Backup Recovery)**: primary backup service for ECS, NAS, OSS, databases, and on-premises; backup vaults must be in a different region from production to provide region-level DR value. |
| 32 | - **ECS disaster recovery**: cross-region snapshot replication plus ECS instance image (custom AMI) synchronization; verify that the ECS instances in the DR region can be launched within the stated RTO. |
| 33 | - **GSLB / GTM**: Alibaba Cloud Global Traffic Manager provides DNS-based health checking and failover routing — verify health check intervals and failover TTLs are aligned to RTO targets. |
| 34 | |
| 35 | ## References |
| 36 | |
| 37 | Load these only when needed: |
| 38 | |
| 39 | - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full BCDR review or formatting the final assessment output. |
| 40 | - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or product feature claims. |
| 41 | |
| 42 | ## Response minimum |
| 43 | |
| 44 | Return, at minimum: |
| 45 | |
| 46 | - the workload criticality classification and stated RTO/RPO targets, |
| 47 | - the current HA architecture assessment with evidence labeling, |
| 48 | - cross-region and cross-zone redundancy gaps, |
| 49 | - HBR backup coverage and cross-region vault verification, |
| 50 | - recovery test evidence (last drill date, scope, result), |
| 51 | - runbook completeness and owner assignment, |
| 52 | - prioritized BCDR improvement recommendations. |