Considerations and Limitations

Consider the following limitations for Veeam Plug-in for Kasten:

Veeam Plug-in for Kasten does not support Kerberos for Kasten exports to Veeam backup repositories.
Veeam Plug-in for Kasten does not support IPv6.
Veeam Plug-in for Kasten does not synchronize Veeam Kasten retention (retire) sessions.
A Veeam Kasten instance can operate with only one backup server. If you add it to another backup server, you will not be able to perform any operations with this Veeam Kasten instance on the first backup server.
Veeam Plug-in for Kasten does not support Kasten exports to direct backup object storage repositories.
Veeam Plug-in for Kasten supports Kasten exports to scale-out backup repositories with the Data locality placement policy only. The Strict placement policy enforcement check box must also be selected. For more information, see the Backup File Placement for Performance Tier section in the Veeam Backup & Replication User Guide.
If an extent that contains a backup chain becomes unavailable, Kasten exports to the scale-out backup repository will fail. Veeam Backup & Replication does not automatically move backup chains to another extent.
If you delete Veeam Kasten policies created by the Veeam Kasten Multi-Cluster console on Kasten secondary servers, they will be recreated by the Veeam Kasten Multi-Cluster console.
Veeam Plug-in for Kasten does not support Kasten export from a Kasten instance that is not added to the Veeam Backup & Replication infrastructure.
Veeam Plug-in for Kasten is not supported in the Veeam Backup & Replication web UI.
If you work with Veeam Backup & Replication on Linux, you cannot use a domain user for location profiles in Veeam Kasten.