Feature Update December 2025

We understand that people may be looking forward to some downtime at the end of the year (or perhaps some lucky people are already on their vacation) but we, at CloudCasa, are not yet ready to take a break. On top of everything we added this year (Backup to NFS, File-level restore for VMs, Recovery point resource browser, and Restores to existing PVCs to name just a few), we decided to release few more features before welcoming 2026.

Happy New Year!

Compression

It is now possible to enable compression for the backups in CloudCasa. Similar to backup storage configuration, this can be done in three places.

  • In Configuration => Settings to apply the change globally.

  • In cluster Edit => Advanced options to enable for a given cluster

  • In Advanced options while defining a backup

In each case, compression can be enabled and a specific scheme can be selected. The default is “Balanced” which tries to balance resource usage and compression ratio. Using other options, you can optimize for speed, memory, or for compression ratio.

Do note that enabling compression uses more resources on the cluster.

SMB

CloudCasa introduced support for NFS storage as backup target in a previous release. In this release, we extend that support to SMB protocol. Just like for NFS, you can create a SMB storage resource in Configuration => Storage => File Storage.

In addition, it is now possible to customize the configuration of the pod that CloudCasa starts, whenever backup and other operations need to be run to NFS and SMB storage. This can be done by going to:

Edit => Advanced Options => Customize gateway parameters

click on Help to see detailed instructions.

Job activity changes

Several changes have been made to the backup job activity to help users easily track what’s going on with a job. The changes include the following.

  • You will now see PVC progress directly in the job activity as they are going through snapshot, mount, and copy phases.

  • We now explicitly show mover pod information as they start running and backing up PVCs. In case of errors when mover pod fails to come up (such as PVC mount errors), you can clearly correlate the errors to the movers. It is also possible to download mover pod spec. This will help in checking the exact way in which PVCs are being mounted. In addition, we can also check if any admission controllers are adding any thing to the mover pod spec or otherwise modifying it.

  • Finally, the multiple “PV Details” tabs are consolidated into a single tab with all different phases of the PVC (snapshot, mount, and copy) being displayed in a single table now.

We hope that the changes help in tracking job progress and also in troubleshooting any errors. Please let us know if you have any feedback in this regard.

Miscellaneous

  • Some S3 providers may require old “V2” signature to be used to sign S3 API requests. So CloudCasa now allows the signature to be selected while creating or editing objectstore resources. This can be done in Advanced options => S3 signature version. In most cases, you can leave this field at its default value.

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 using the support chat feature, or by sending email to support@cloudcasa.io.