This blog post explores the K10 data management platform by Kasten. This is particularly useful in disaster recovery scenarios and migration of applications as we will explore in the post below.

The purpose of this post is to share lessons learned and explore the backup DR with the K10 platform. This exercise is performed for a customer where I should propose strategies DR. One of the requirements is to have a setup area cross Kubernetes active-passive cluster along with the volume of data to replicate the data from source to destination in a regular rhythm.

This is the first part of a series that provides a platform to evaluate the Backup and DR. You can explore to know more about Kubernetes backup.

Some of the key evaluation criteria are:

  • Provision of continuous replication from the source application Kubernetes along with the data
  • Allowance for the snapshot volume to be consistent application and database
  • Inter-regional migration
  • This platform should be expanded
  • Ability to monitor backup and restore jobs. Preferably should allow the monitoring platform via Prometheus
  • Finally, the solution or the gear selection must be original API-centric and cloud itself

Image Source: Google

About K10

K10 platform truly original and installed on the cluster Kubernetes that need to be supported. The platform is installed as a group CRDS and controller by the graph helmet.


Applications represent a collection of resources such as configmaps, secret, service, and application workloads in a namespace that auto-discovered by K10. A policy can be associated with an application or a subset of resources in applications for backup/restore.


The policy allows defining actions to be taken when the policy is implemented. Measures can perform snapshots or import from a previous backup is exported. The frequency at which action must be taken, the retention period for backup resource selection are all defined in the policy. This policy also refers to the profile location

K10 Disaster Recovery

The K10 disaster recovery backup from K10 namespace and metadata are accompanied restore point for all applications to allow restoration of the platform K10 itself in case of disaster.