Persistent application data
Inventory PVC and manifest dependencies together.
KUBERNETES
Containers are temporary.
Your data stays.
Identify application resources, persistent data and restore order together. Start with a compatibility assessment for your Kubernetes distribution.
STEP-BY-STEP GUIDES
From installation to recovery.
01
02
Kubernetes Backup Guide
Prepare EraBackup Kubernetes agent policies, PVC/Pod selection and node/control-plane methods for your distribution; plan catalog and isolated restore acceptance together.
Open guide02Kubernetes Restore Guide
Inspect Kubernetes catalog records, PVC targets and control-plane recovery limits separately; verify source/namespace mapping and application acceptance.
Open guideUSE CASES
Start with your needs.
Distribution assessment
Identify an appropriate data path for the Kubernetes and CSI versions.
Application recovery
Validate the target namespace, access and external dependencies.
DEFINE YOUR SCENARIO
Define the application unit
A workload is more than a Pod. Inventory Deployment/StatefulSet, Service, ConfigMap and PVC dependencies per application to clarify restore order. Address Secrets and external services separately.
Storage prerequisites for persistent data
Assess CSI snapshot availability, snapshot controller, VolumeSnapshotClass, storage driver and volume mode together. Snapshots and repository copies serve different purposes; recovery to target storage also belongs in the plan.
Validate your distribution
Existing EraBackup Kubernetes-based workflows are primarily documented for OpenShift. For other distributions, we assess APIs, access, storage and real restore scenarios rather than assume equivalent coverage.
Platform technical reference: Kubernetes Volume Snapshots
COMMON QUESTIONS
Start with
the right questions.
Is every Kubernetes distribution supported out of the box?
We do not make a distribution-wide or version-independent support commitment. The applicable scope follows a technical assessment of the distribution, CSI and selected workload.
Is backing up manifests enough?
Persistent volumes, databases, Secrets and external dependencies also need a plan. Complete the scope with a restore test that verifies the target application works.
START WITH YOUR INFRASTRUCTURE
Kubernetes — let’s discuss your needs.
Share your workloads and recovery objectives. Let’s define the technical scope together.
