Feature Update April 2026

It’s been a little over three months since our last CloudCasa feature update in December. A cold and snowy winter has finally given way to spring here in New Jersey, but we were very busy through that long winter, and now it’s time for us to start releasing some of what we were working on! We’ve introduced a number of improvements to CloudCasa with this update, some visible to users and others not. Stay tuned, because another update with even more new features will be coming soon!

Policy pause and resume

Previously, backup and replication job scheduling could be paused/resumed at the individual job level, but now we have added the ability to pause/resume jobs at the policy level as well. Pausing a policy will pause scheduling of all backup and replication jobs that use that policy. Pause and resume policies by going to the Configuration/Policies page and selecting Actions/Pause or Actions/Resume for a policy. If a policy is suspended, an indication is shown in the Policies list and also for any jobs that use it.

Audit log (Preview)

With this release, we have introduced a preview of user-level audit logging with the new Configuration/Audit logs page.

You can now review and optionally download records of all successful create, update, and delete requests made for all CloudCasa resources in your organization. Currently these are in the form of CloudCasa REST API requests. Each audit log record contains a timestamp and the user or API key that issued the request along with other request details. Records can be sorted or filtered on any field.

You can also download audit logs in JSON or CSV formats by clicking the “Download” button in the upper right of the page. This will open a dialog where you can choose the format and time range for the download.

In future updates, audit records will be enhanced with additional fields to provide a more traditional audit log user experience.

Note that audit logs are only visible to users with the ADMIN role or users with a custom role that has the new “Audit Logs.View” permission.

VMs tab added for restore job activity view

Restore jobs now have a VMs tab in their Activity details view, which contains details of any VMs being restored. This makes is more convenient to see what is going on with restores of KubeVirt VMs. Previously, only backup jobs showed separate VM details.

Persistent data mover index cache

An option is now available to enable persistent caching of index data by the CloudCasa agent’s data mover, using dynamically created PVCs.

At the beginning of a backup, the CloudCasa agent data mover pod downloads index data from the target storage into temporary local storage before then loading it into memory. By default, this data is lost when the data mover terminates. Keeping the data around can, in certain cases, speed up backups and reduce network traffic.

Persistent cache is disabled by default, but can be enabled on a per-namespace basis. To configure it, you need to select a storage class which will be used to create the cache PVCs dynamically. The cache size can then be configured for each namespace separately. This can be done under Advanced options/Configure data mover cache in the Edit Cluster page. For each configured namespace, the data mover will then create a PVC using the selected storage class, and use it for persistent index data caching.

Enabling persistent caching is not necessary in most cases, but it can help to improve backup performance in certain specific scenarios, particularly when backing up PVCs containing a large number of files that change frequently.

Condense operations for private object stores now run in separate agent pod

Previously, maintenance (i.e. condense) operations on private object stores ran directly in the CloudCasa agent. With this change, these operations now run in a separate pod that is created for this purpose. The pod name will be of the form “kubemover-condense-<JOBID>”. The advantage is that requests and limits for storage maintenance operations (especially memory) can now be configured independently of the rest of the agent.

Requests and limits for the condense pod can be set using the agent resource configuration mechanism, in the section “data-mover”.

Red Hat OpenShift Operator

A certified OpenShift operator is now available to install and manage the CloudCasa agent on Red Hat OpenShift. See our CloudCasa page in the Red Hat Ecosystem Catalog. Previously, the CloudCasa agent was certified on OpenShift, but only Helm installation was available.

Nutanix NKP application catalog

As a result of our partnership with Nutanix, the CloudCasa agent is now certified with NKP and available for installation from the Nutanix NKP application catalog. You will see “CloudCasa Agent” listed in the Nutanix Kommander console Applications tab. Just click Enable and follow the documentation!

Miscellaneous

  • Detailed application hook errors are now shown in Activity Log tab of the job Activity details view. This should make identifying and debugging app hook issues significantly easier.

  • A “No guest agent found” warning is now indicated under Errors & Warnings if the QEMU guest agent is not found when backing up a KubeVirt VM. While running the QEMU guest agent on your VMs is not required to back them up, it is recommended, as it provides VM filesystem quiescing. Now you’ll have an easy way to see which, if any, of your VMs the guest agent was not running on.

  • Previously, namespace labels and annotations for pre-existing namespaces were not updated on restore, even if the overwrite option was selected. This is now fixed.

Kubernetes agent updates

In this update we’ve again made several changes to our Kubernetes agent to add features, improve performance, and fix bugs. Some new product features will not work with older versions of the agent. However, manual updates shouldn’t normally be necessary because of the automatic agent update feature. If you have automatic updates disabled for any of your agents, you should update them manually as soon as possible.

Notes

With some browsers you may need to restart, hit Control-F5, and/or clear the cache to make sure you have the latest version of the CloudCasa web app when first logging in after the update. You can also try selectively removing cookies and site data for cloudcasa.io if you encounter any odd behavior.

As always, we want to hear your feedback on new features! You can contact us by sending email to support@cloudcasa.io.