top of page
Search

The Cloud Isn’t the Risk. The No-DR Plan Is.

  • 5 days ago
  • 4 min read


Backup + DR for Huawei Cloud Container Engine (CCE) Kubernetes now available in RackWare SWIFT


Now available for production use (GA): RackWare SWIFT supports Huawei Cloud Container Engine (CCE) for Kubernetes backup + DR, with optional on‑demand DR cluster provisioning (so you don’t need a full standby cluster unless you want one).


Key takeaways:


  • SWIFT enables backup and disaster recovery for Huawei Cloud CCE – including stateful workloads.

  • Support spans all six common Huawei CCE storage types: EVS, SFS, SFS Turbo, and OBS.

  • Choose your DR economics: warm target cluster, or on-demand DR CCE provisioning during failover/drills.

  • The same workflow supports “move” scenarios too – controlled cutovers and modernization without re-platforming pain.


Executive summary


Huawei Cloud CCE is becoming a strategic Kubernetes platform in markets where sovereignty, locality, and ecosystem alignment matter. But many teams still lack a repeatable way to recover stateful applications cleanly when the cluster, storage, and dependencies must come back together under pressure. RackWare SWIFT closes that gap with a single, operator-friendly workflow for backup, DR, and migration-style portability on Huawei Cloud CCE. It also provides a clean path to move applications into Huawei Cloud CCE from other Kubernetes platforms (managed, enterprise, or on‑prem) using the same operational model.


Why CCE teams care right now


Modernizing onto Kubernetes is the easy part. Proving you can recover is the hard part. In a real incident, “we can redeploy” is not the same as “we can recover.” The difference is data, order, and repeatability.


The challenge: Kubernetes recovery has more moving parts than VMs


Stateful Kubernetes recovery is not just “re‑deploy the YAML.” When an incident hits, teams must restore application objects, persistent data, and the target environment in the right order – otherwise services come up partially, data becomes inconsistent, or dependencies fail silently.


Huawei Cloud CCE adds an additional real‑world variable: storage diversity. Different storage types and classes can behave differently across clusters and regions. The result is that many DR plans look good on paper, but aren’t proven until the day you least want surprises.


SWIFT addresses this by treating recovery as a single workflow: capture objects + data together, retain copies (including in OBS), and orchestrate restore and failover with repeatable drills. And for cost control, SWIFT can optionally provision the DR CCE cluster on‑demand during failover or drills - so you don’t have to maintain a full standby cluster unless you choose to.


The SWIFT approach on Huawei Cloud CCE


Modernization path: move workloads to Huawei Cloud CCE


Many teams adopt SWIFT first for resilience (backup and DR), and then use the same workflow to support modernization moves into Huawei Cloud CCE. That means you can lift and evolve applications into CCE from common Kubernetes platforms without rebuilding everything from scratch.


  • Move to Huawei CCE from managed Kubernetes: EKS, AKS, GKE, OKE.

  • Move from enterprise platforms: VMware Tanzu and OpenShift (cloud or on‑prem).

  • Use staged sync and controlled cutovers to test, validate, and switch over with confidence.


Figure 1. Reference architecture for migration into Huawei Cloud CCE (from other clouds or on‑prem).
Figure 1. Reference architecture for migration into Huawei Cloud CCE (from other clouds or on‑prem).

SWIFT treats recovery as an application workflow. It captures what you need to bring services back online and orchestrates the steps so recovery is repeatable, drillable, and measurable – without forcing application rewrites.


What you can do with SWIFT on Huawei Cloud


  • Discover and connect to Huawei CCE clusters and related registries.

  • Protect applications with backup and point-in-time recovery, with optional retention in Huawei Object Storage (OBS).

  • Set up DR for CCE workloads with orchestrated failover and controlled fallback.

  • Provision the DR CCE cluster dynamically during failover/drills (optional) to reduce always-on standby cost.

  • Use staged workflows to validate restores, run drills, and support controlled cutovers for migration-style moves.


Figure 2. Reference architecture for continuous protection: backup + DR on Huawei Cloud CCE (including dynamic DR cluster provisioning).
Figure 2. Reference architecture for continuous protection: backup + DR on Huawei Cloud CCE (including dynamic DR cluster provisioning).

Storage coverage: all Huawei CCE storage types


SWIFT supports protection and recovery across the six common storage types used in Huawei CCE environments:


  • EVS

  • SFS

  • SFS Turbo

  • OBS (Object Storage)


Common failure modes (what breaks in real incidents)


  • Relying on manifests alone and discovering too late that data consistency and ordering were never validated.

  • Assuming storage classes behave the same across clusters and regions without mapping and restore tests.

  • Treating “a standby cluster exists” as proof of readiness (without timed drills).

  • Having backups but no repeatable failover workflow – so RTO becomes a guess.


Where this lands immediately


  • Regulated industries (banks, telecom, public sector) standardizing on Huawei Cloud.

  • Platform teams running stateful services on CCE that must be recoverable, not just redeployable.

  • Organizations that want DR readiness without paying for idle clusters all year.

  • Modernization programs where migration, DR, and backup need to share a single operational model.


A practical way to start

  1. Choose a pilot namespace (one stateful app and one stateless app).

  2. Run a backup and validate a restore in a staged environment.

  3. Execute a timed DR drill and capture RTO/RPO targets for leadership.

  4. Decide your activation model: warm DR target or on-demand DR CCE provisioning.

  5. Expand by criticality: add more namespaces and tune retention policies (including OBS if needed).


Next step


If you’re running serious workloads on Huawei Cloud CCE, start with a pilot and run a timed drill. You’ll quickly see the difference between having a plan on paper and having a recovery workflow you can trust.



Appendix: Huawei CCE setup resources



 
 
 

Comments

bottom of page