CRN: You also mentioned new integrations of Veeam with Red Hat. What‘s going on there?
Allan: [We previously] brought out Veeam backup for Nutanix AHV, its Acropolis hypervisor, which is a KVM variant. Now generally available at 2.1 of that product, it‘s been going very well within the Nutanix partner ecosystem. The reason I start with that is, AHV is based on KVM. We have some customers who are not using the Nutanix version of KVM. They’re using the Red Hat version. And so they said, ’Hey, can you bring us the same solution?’ And so we did. We took the solution that protects the Acropolis hypervisor and we built it for Red Hat Virtualization. So while it is a version 1 product, the ability to protect Red Hat Virtualization is really built on our learnings with AHV and the partnership with Red Hat. So for the past year, we’ve been working on introducing change block tracking into the kernel, and we’re taking advantage of that change block tracking in our data protection capability.
CRN: So the Linux kernel change block tracking was developed with specifically with Veeam?
Allan: Specifically with Veeam, and we‘ve been going back and forth. It’s actually one of the reasons why I say it’s coming up this summer as opposed to already here, because we’ve been helping them solve some of the issues in those kernel drivers. [It’s in] RHEL (Red Hat Enterprise Linux) 8.3 and, and RHV (Red Hat Virtualization) 4.6, but it’s basically solving some of those things specifically related to change block tracking so that it can scale to the size of our customers.