Veeam · Software · YoctoIT tech page

Kasten

Kubernetes-native backup: container applications protected as wholes — namespaces, volumes and configuration together.

FOCUS · THE CONTAINERS' BACKUPThe K8s application is namespace+volumes+config: it's protected whole, not in pieces
Request the Free Assessment Learn more
YoctoIT material for clients and partners · Veeam, Kasten, Coveware and the other products mentioned are trademarks of Veeam Software.
01 · What it is

Kasten by Veeam, made clear.

Traditional backups don't understand Kubernetes: the application is a set of objects (deployments, secrets, PVCs) that lives in the cluster. Kasten K10 was born there: it discovers the apps by itself, copies them WHOLE (data + configuration), restores them even onto other clusters — and with the house's immutability and ransomware detection.

K8s-native
it runs in the cluster, it understands the apps: the backup that speaks YAML
App-aware
namespaces, CRDs and volumes together: the whole application, not scattered files
Cross-cluster
the restore onto another cluster: DR and migrations in the same move
Kasten by Veeam
OFFICIAL VEEAM BRANDING · KASTEN
CONSOLE REALE · KASTEN K10 DASHBOARD · FONTE: VEEAM KASTEN DOCS
REAL CONSOLE · KASTEN K10 DASHBOARD · SOURCE: VEEAM KASTEN DOCS
02 · How to use it well

The things that make the difference.

Inside the cluster

The apps: deployments, PVCs, configthe unit that counts
Discovery
Backup policies
Blueprints (DB-aware)
finds · protects · consistent
K10 · in the clusterthe operator at work
Immutable object storagethe armored destination
The backup that understands Kubernetes

Policies per namespace

The production apps protected by label: the new app is born already covered.

Application consistency

The blueprints for PostgreSQL, Mongo and the stateful apps: the consistent snapshot, not a random file.

DR between clusters

The restore onto an alternative OpenShift/AKS/GKE: the container world's plan B.

GitOps + backup

The code in the repo AND the state in the backups: the two restores you both need.

03 · In depth

Kubernetes: the backup that understands the apps

Kasten K10 protects the Kubernetes applications as wholes: namespaces, resources, PVs and data together (application-centric, not volume-centric); the blueprints handle the databases with quiesce hooks, the policies protect by label (the new app is already covered), the immutability on object storage and the encryption defend the copies, the disaster recovery recreates the app on another cluster (even another distro: from EKS to OpenShift); the multi-tenant UI delegates to the teams.

  • Application-centric — the whole app (resources+data), not loose disks: the consistent restore
  • Blueprint — hooks for PostgreSQL, MySQL, Mongo: the database quiesces and restarts
  • Policy per label — declarative protection: the new namespace is already inside
  • Cross-cluster/distro — the restore onto a different cluster: DR and migration together
  • Immutabilità — object lock on the K8s copies: the ransomware doesn't get in
  • Multi-tenant — each team its own perimeter: governed self-service
04 · Numbers and lifecycle

The numbers that matter.

100%
of the app restored: resources, config and data together
label
the protection that follows the deploy
multi
distros: EKS, AKS, GKE, OpenShift, Tanzu
GitOps
policy as code: the backup declared with the rest
The stateful on K8s has arrived: the backup too — blueprints, policies and DR set up by us.
05 · Use cases

Where it really pays off.

OpenShift & K8s in production

The stateful apps, protected where they live.

Cluster migrations

Upgrades and moves with a safety net.

Multi-cluster & multi-cloud

A single protection policy, everywhere.

Containers too have data that doesn't come back by itself: Kasten protects them — we manage it in the cluster.