alibaba-resilience-bcdr-review
Review 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.
Install
npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-resilience-bcdr-review
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Alibaba Cloud Resilience BCDR Review
Purpose
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.
When to use
Use this skill for:
- reviewing RDS High-Availability Edition and PolarDB Global Database Network failover designs
- assessing ACK multi-zone and cross-region container resilience
- auditing HBR (Hybrid Backup Recovery) backup coverage and cross-region vault placement
- evaluating ECS disaster recovery cross-region replication and AMI snapshot strategies
- analyzing RTO/RPO targets against documented and tested recovery evidence
- identifying runbook gaps and DR drill history
Lean operating rules
- 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.
- Separate confirmed facts from inference. If a capability was not verified by evidence, label it explicitly.
- RTO/RPO targets without evidence of a tested recovery are aspirational claims — challenge them and ask for the last DR drill date and outcome.
- Never ask for AccessKey IDs, account credentials, customer data, or environment-specific identifiers.
- Challenge vague DR claims, same-region backup vaults, undocumented failover procedures, and unverified recovery automation.
Key resilience and BCDR guidance
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
References
Load these only when needed:
- Workflow and output contract — use when executing the full BCDR review or formatting the final assessment output.
- Official sources — use when grounding Alibaba Cloud service behavior or product feature claims.
Response minimum
Return, at minimum:
- the workload criticality classification and stated RTO/RPO targets,
- the current HA architecture assessment with evidence labeling,
- cross-region and cross-zone redundancy gaps,
- HBR backup coverage and cross-region vault verification,
- recovery test evidence (last drill date, scope, result),
- runbook completeness and owner assignment,
- prioritized BCDR improvement recommendations.
Files (vanguard-frontier-agentic)
-
references
-
official-sources.md 1.4 KB
# Official sources Use this reference only when you need source grounding for Alibaba Cloud resilience and BCDR service behavior or the detailed source list. ## Alibaba Cloud documentation Use these as starting points, not as proof of the user's live Alibaba Cloud state: - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/disaster-recovery-solution - https://www.alibabacloud.com/help/en/polardb/polardb-for-mysql/global-database-network - https://www.alibabacloud.com/help/en/ack/ack-managed-and-ack-dedicated/user-guide/overview-of-disaster-recovery-for-ack-clusters - https://www.alibabacloud.com/help/en/hybrid-backup-recovery/latest/what-is-hbr - https://www.alibabacloud.com/help/en/server-load-balancer/latest/what-is-global-traffic-manager - https://www.alibabacloud.com/help/en/ecs/user-guide/create-a-custom-image - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/read-only-apsaradb-rds-for-mysql-instances ## Grounding rule Official documentation explains Alibaba Cloud service behavior and feature availability. It does not prove the user's current account, region, quota, resource configuration, or operational state. Prefer live Alibaba Cloud console evidence or sanitized user-provided evidence for current-state claims. RTO/RPO targets stated in documentation reflect product capability ceilings — not the user's actual achieved recovery time. -
workflow-and-output.md 2.6 KB
# Workflow and output contract Use this reference only when performing a full BCDR review or production-readiness assessment. ## Review domains Check these areas before giving a recommendation: - Workload criticality classification (mission-critical, business-critical, standard) - Stated RTO/RPO targets and evidence of tested recovery against those targets - HA architecture: RDS HA Edition, PolarDB GDN, ACK multi-zone, ECS cross-region - HBR backup coverage: vault region, backup frequency, application-consistent snapshot policy - Cross-region redundancy: separate ACK clusters, GSLB/GTM routing, DR region readiness - Runbook completeness: documented failover steps, owner assignment, last tested date ## Safe workflow 1. **Frame requirements** - Workload name and criticality classification: - Stated RTO target: - Stated RPO target: - Regions in use (primary and DR): - Last DR drill date and outcome: 2. **Collect evidence** - Prefer live console or aliyun CLI evidence if available. - Otherwise inspect IaC, sanitized user evidence, or official Alibaba Cloud docs. - Label each finding as `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`. 3. **Stress-test the design** - What happens if the primary region becomes unavailable? - What single points of failure exist in the HA design? - Are HBR vaults in a separate region? - Is there evidence of a successful failover test? - What runbook steps are missing or unowned? 4. **Recommend the smallest safe next step** - Prioritize by risk: untested recovery > missing cross-region vault > no GSLB > aspirational RTO claims. - If the safest action is to schedule a DR drill, say that plainly. ## Output contract Return this structure: ```markdown # Alibaba Cloud BCDR Review: <workload scope> ## Executive summary - BCDR posture verdict: - Evidence level: - Critical gaps: ## Workload profile - Criticality: - RTO target (stated): - RPO target (stated): - Primary region: - DR region: ## HA architecture assessment | Component | Current configuration | HA classification | Gaps | |---|---|---|---| ## HBR backup coverage - Vault region: - Backup frequency: - Application-consistent snapshots: - Cross-region vault confirmed: ## Recovery test evidence - Last DR drill date: - Scope tested: - Outcome: - Gaps identified during drill: ## Runbook completeness - Failover steps documented: - Owner assigned: - Last reviewed date: ## Prioritized BCDR improvements 1. <improvement> — priority: <critical/high/medium>, effort: <low/medium/high> ## Open questions 1. <question> — owner: <owner>, impact: <impact if unresolved> ```
-
-
metadata.json 1.5 KB
{ "id": "alibaba-resilience-bcdr-review", "name": "Alibaba Cloud Resilience BCDR Review", "type": "skill", "provider": "alibaba", "harnesses": [ "codex", "claude-code", "cursor", "gemini", "kiro", "other" ], "summary": "Review 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.", "source_type": "original", "official_docs": [ "https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/disaster-recovery-solution", "https://www.alibabacloud.com/help/en/polardb/polardb-for-mysql/global-database-network", "https://www.alibabacloud.com/help/en/ack/ack-managed-and-ack-dedicated/user-guide/overview-of-disaster-recovery-for-ack-clusters", "https://www.alibabacloud.com/help/en/hybrid-backup-recovery/latest/what-is-hbr", "https://www.alibabacloud.com/help/en/server-load-balancer/latest/what-is-global-traffic-manager" ], "security_notes": "HBR backup vaults in the same region as production provide no DR value for region-level failures — require cross-region vault configuration. PolarDB Global Database Network write routing to primary means regional primary failure requires manual failover promotion — confirm this is documented in runbooks.", "last_verified": "2026-05-09", "path": "skills/alibaba/alibaba-resilience-bcdr-review", "author": "github: VincentChuWaiChow", "version": "0.1.0" } -
SKILL.md 3.9 KB
--- name: alibaba-resilience-bcdr-review description: Review 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. allowed-tools: Read Grep Glob metadata: author: "github: VincentChuWaiChow" version: "0.1.0" updated: "2026-05-09" category: resilience --- # Alibaba Cloud Resilience BCDR Review ## Purpose 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. ## When to use Use this skill for: - reviewing RDS High-Availability Edition and PolarDB Global Database Network failover designs - assessing ACK multi-zone and cross-region container resilience - auditing HBR (Hybrid Backup Recovery) backup coverage and cross-region vault placement - evaluating ECS disaster recovery cross-region replication and AMI snapshot strategies - analyzing RTO/RPO targets against documented and tested recovery evidence - identifying runbook gaps and DR drill history ## Lean operating rules - 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. - Separate confirmed facts from inference. If a capability was not verified by evidence, label it explicitly. - RTO/RPO targets without evidence of a tested recovery are aspirational claims — challenge them and ask for the last DR drill date and outcome. - Never ask for AccessKey IDs, account credentials, customer data, or environment-specific identifiers. - Challenge vague DR claims, same-region backup vaults, undocumented failover procedures, and unverified recovery automation. ## Key resilience and BCDR guidance - **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. - **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. - **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). - **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. - **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. - **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. ## References Load these only when needed: - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full BCDR review or formatting the final assessment output. - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or product feature claims. ## Response minimum Return, at minimum: - the workload criticality classification and stated RTO/RPO targets, - the current HA architecture assessment with evidence labeling, - cross-region and cross-zone redundancy gaps, - HBR backup coverage and cross-region vault verification, - recovery test evidence (last drill date, scope, result), - runbook completeness and owner assignment, - prioritized BCDR improvement recommendations.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.