How K10 Policy Works

In this article

    To move backups exported by K10 policies to Veeam backup repositories, a K10 cluster and a Veeam Backup & Replication server use Veeam Data Movers. Veeam Data Mover is a non-persistent runtime component that allows you to export application disks from the K10 cluster to backup repositories. When you start a K10 policy, the following Veeam Data Mover are created:

    • Source Veeam Data Mover — the Veeam Data Mover that runs in the Kanister Pod added to the K10 cluster.
    • Target Veeam Data Mover — the Veeam Data Mover that runs in the Veeam backup repository added to the Veeam Backup & Replication server.

    After the K10 policy is completed, Veeam Data Movers are removed from both the K10 and Veeam Backup & Replication infrastructure. For more information, see the Veeam Data Mover section in the Veeam Backup & Replication User Guide.

    When you launch a K10 policy, the following happens:

    1. K10 takes a snapshot of applications and uses these snapshots to make exports.
    2. K10 copies configuration files of applications to cloud storage of a public or private cloud provider.
    3. Source Veeam Data Mover retrieves application data, compresses and deduplicates it.
    4. Source Veeam Data Mover exports application data to the target Veeam Data Mover.
    5. Target Veeam Data Mover forwards exported application data to the Veeam backup repository in the Veeam proprietary format.