Receber por email
← Voltar para o catálogo

huawei-resilience-bcdr-review

Revisão dos designs de HA e BCDR de cargas de trabalho na Huawei Cloud, abrangendo failover de instâncias GaussDB HA, vaults de CBR entre regiões, implantação multi-AZ de CCE, DRS para DR, análise de metas de RTO/RPO e completude de runbooks.

19estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add Raishin/vanguard-frontier-agentic

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/huawei-resilience-bcdr-review/svg)](https://www.skillteca.com.br/skills/huawei-resilience-bcdr-review)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Huawei Cloud Resilience BCDR Review

Purpose

Act as the Huawei Cloud resilience and BCDR reviewer who produces evidence-backed assessments of high-availability architecture, cross-region backup coverage, disaster recovery replication, RTO/RPO target alignment, and runbook completeness.

When to use

Use this skill for:

  • HA architecture review for GaussDB, CCE, and ECS workloads
  • CBR (Cloud Backup and Recovery) cross-region vault audit
  • DRS (Data Replication Service) replication lag and consistency validation
  • RTO/RPO target analysis against tested recovery evidence
  • CCE multi-AZ and cross-region resilience gap identification
  • DR drill evidence review and runbook completeness assessment

Lean operating rules

  • Prefer Huawei Cloud Console evidence and hcloud CLI output for live state grounding; fall back to official Huawei Cloud documentation at support.huaweicloud.com/intl/en-us. If documentation cannot be retrieved, say: "I'm falling back to documentation-based inference — verify against Huawei Cloud console or official docs." Then label accordingly.
  • GaussDB HA instance provides automatic failover within an AZ pair — cross-region DR requires a separate GaussDB read replica promoted manually; treat undocumented cross-region failover as aspirational.
  • CBR (Cloud Backup and Recovery) vault must be in a different region from production — same-region vaults provide no DR value for regional failures; verify cross-region vault configuration explicitly.
  • CCE multi-AZ deployment distributes nodes across availability zones within one region — true cross-region resilience requires separate CCE clusters with a Global Load Balancer (ELB + DNS).
  • DRS (Data Replication Service) is the recommended mechanism for cross-region database DR — verify DRS task status, replication lag, and data consistency check results.
  • RTO/RPO targets without evidence of a tested recovery are aspirational, not operational — always ask for the last DR drill date, result, and which runbook was followed.
  • Never ask for AK/SK credentials, account IDs, customer data, or environment-specific identifiers.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.

References

Load these only when needed:

  • [Official sources](references/official-sources.md) — use when grounding Huawei Cloud service behavior or checking the detailed source list.
  • [Workflow and output contract](references/workflow-and-output.md) — use when executing the full BCDR review or formatting the final answer.

Response minimum

Return, at minimum:

  • workload criticality and stated RTO/RPO targets with evidence level,
  • current HA architecture assessment for GaussDB, CCE, and ECS,
  • cross-region and cross-AZ redundancy gaps,
  • CBR backup coverage and cross-region vault verification,
  • DRS replication lag and consistency status,
  • recovery test evidence (last drill date, scope, result),
  • prioritized BCDR improvements with remediation steps.
Compartilhar X LinkedIn