How Kasten Policy Works

To move backups exported by Kasten policies to Veeam backup repositories, a Kasten 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 Kasten cluster to backup repositories. When you start a Kasten policy, the following Veeam Data Movers are created:

• Source Veeam Data Mover — the Veeam Data Mover that runs in the Kanister Pod added to the Kasten 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 Kasten policy is completed, Veeam Data Movers are removed from both the Kasten and Veeam Backup & Replication infrastructure. For more information, see the Veeam Data Mover Service section in the Veeam Backup & Replication User Guide.

When you launch a Kasten policy, the following happens:

1. Kasten takes a snapshot of applications and uses these snapshots to make exports.
2. Kasten copies configuration files of applications to the 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.