Feature Update September 2026

Since our last release in July when we announced storage replication based DR feature, we have been hard at work as you can tell from the big list of features in this release. Without further ado, here are the list of features we released in this update.

MCP Server

We are introducing CloudCasa MCP server with this release that should make many AI aficionados happy. They can now use their favorite AI tool to query the status of CloudCasa jobs as well as many other CloudCasa operations. The MCP server invokes the CloudCasa APIs on your behalf and authenticates with a CloudCasa API key. Note that the MCP server currently supports read operations only.

For more details, see MCP Server.

PowerStore DR

In July, CloudCasa introduced industry-first Disaster Recovery orchestration for Kubernetes workloads (including containers and VMs) using the replication features of the underlying storage. This allowed customers to keep their current storage investments and get very powerful DR feature with very low RPO/RTO guarantees. In the initial release, we introduced support for HPE Alletra storage. As part of this effort, we implemented a DR framework that makes extending DR support to other storage providers a relatively easy process.

Using that framework, we are now adding Dell PowerStore family of storage to our line up of supported DR storage providers.

CBT

It is no secret that in last few years, Kubernetes has become a go-to platform for not just containers but for VMs as well, thanks to KubeVirt. In version 1.8, KubeVirt has introduced support for incremental backups with Changed Block Tracking (CBT). The feature utilizes QEMU’s and libvirt backup capabilities and is storage agnostic. This version of KubeVirt is available in OpenShift versions starting from 4.22 and needs to be explicitly enabled.

Starting with this release, CloudCasa is announcing “Preview” support for CBT backups.

For more details, see Changed Block Tracking.

VM Tab

Continuing the theme of VMs, CloudCasa now provides a first-class management of VM backups by adding a dedicated “VMs” page. On this page, you will find a complete list of VMs from all your registered clusters showing information such as running state of the VM and status of the guest agent. You can click on the VM name that takes you to a VM page where backups and restores can be defined for that VM.

You will find that the VM page looks very similar to the cluster page as we tried to elevate VMs to equal footing with the clusters.

New Filestore implementation

CloudCasa has supported NFS/SMB as backup target for almost an year now. While it worked well in most scenarios, we have seen some cases where it can be improved. So we have re-worked the implementation making it much more robust. In addition, the new implementation uses less resources making it viable at the edge as well. Finally, users do not need to make any changes to their existing configuration. The new method automatically kicks in.

Restore modifiers

Resource modifiers is a powerful restore feature where users can specify transformations on the resources as they are restored. This comes handy when you want to change PVC size or access mode for example. But the feature required hand-crafting YAML specification and we all know that it is non-trivial to do that, however great the documentation is.

Starting with this release, we are simplifying the process of creating resource modifiers by providing a wizard in the UI for this purpose. To access the wizard, click on “Edit” and select the option “Guided YAML Editor” after enabling restore modifiers in restore definition. You can then follow the prompts and add required information. There is also an option to start with a template which should take care of commonly used resource modifiers. To access templates, click on “Edit” and select “Templates”.

Note that Resource modifiers are available only with CloudCasa premium (paid) service plans.

Miscellaneous

  • In “VM Details” tab of backups, UI now shows related resource information for each VM, including pods, PVCs.

  • Some third party S3 providers do not support data integrity checks supported by S3 protocol. For adding storage from such providers, CloudCasa now shows an option Perform data integrity checks under advanced options. It is enabled by default but you may need to disable it for some providers.