One of our customers recently renewed **Veeam Backup & Replication (VBR)** in December, but is now evaluating a migration of their **58 VMware host** infrastructure to **OpenShift Virtualization (OCP-V)**. We know that to back up workloads on OCP-V, **Veeam requires Kasten K10**, however, **there is no direct conversion strategy** between VBR and Kasten, which poses a challenge in licensing continuity.
Veeam currently suggests purchasing **Kasten as a standalone solution**, without considering the prior investment in VBR. This opens the possibility for the customer to explore other solutions such as **Trilio, Veritas, or other backup vendors** with native integration into Kubernetes environments.
The key question is: **Is Veeam willing to sustain VBR without offering a transition path to Kasten, risking customer non-renewal? Or, on the contrary, should you design a strategy that allows you to ensure recurring business of between 42 and 58 nodes with Kasten?**
This case highlights the importance of a business strategy that allows customers to migrate without friction, ensuring continuity and loyalty in the use of Veeam solutions within their new infrastructure.
