At this year’s VeeamON, the backup software maker announced a real blow: Veeam will support Red Hat Virtualization (RHV) in the future. Experience has shown that Veeam has always been very careful and conservative when it comes to linking its flagship product Backup & Replication to other hypervisors. VMware was there from the start and Hyper-V was added later. With Nutanix AHV, you took more time – and with the Citrix hypervisor, the decision was taken back then completely against it. A fourth hypervisor is only added now with RHV.

Veeam showed some technical details at the conference. RHV virtual machines must be able to be backed up without an agent and reside in well-known Veeam repositories. Michael Cade also referred to in an interview with iX to Nutanix AHV, where a KVM variant is also used, as is the case with Red Hat’s RHV. RHV’s biggest challenge, according to Cade, would have been developing its own Changed Block Tracking (CBT) pilot, because unlike AHV – where one was provided by the manufacturer – RHV hasn’t had one yet.

CBT technology can significantly shorten the save window because only changed blocks need to be saved. Experience has shown that deep integration into the respective hypervisor technologies is necessary – and if all does not work perfectly well, real disasters threaten. Many admins can tell you a thing or two about this, especially in the early stages of VMware. In this regard, it is quite remarkable that Veeam wants to install CBT technology for RHV from scratch.

Kubernetes is currently ubiquitous not only among hypervisor manufacturers, it is also used in the backup arena. Veeam had nothing of its own in its portfolio so far, which is why Kasten was incorporated for US $ 150 million in October 2020. Their K10 software for data backups and disaster recovery Kubernetes has since completed the Veeam product line.

On April 28 of this year, version 4.0 was released with ransomware protection. Kasten argues here that there are many attack scenarios threatening container systems in particular. You might need to manage open source packages from various sources when building containerized applications. Additionally, Kubernetes itself also needs security updates. Inadequate rights settings can still occur when deploying applications, and rights extensions are also possible when running the application. In this regard, version 4 gives you the option of backing up to S3 data storage with object lock technology.

For the future, we are currently working on the possibility of storing K10 backups in familiar Veeam repositories, explained Michael Cade. Integration into the Veeam GUI is also planned. The familiar K10 web GUI wouldn’t disappear from the scene. Customers who wish to continue working with him could of course do so, Cade explains. In another conference (“Next-Generation IT”), Cade then gave a first look at the next beta version. There you could see in the Veeam GUI that the K10 box had stored its backups in a Veeam repository and could also save them in the familiar VBK format.

Disclaimer: This article is generated from the feed and is not edited by our team.

Leave a Reply

Your email address will not be published.