Catalogic Software Makes New Feature Set Available for CloudCasa
CIOREVIEW >> Backup >>

Catalogic Software Makes New Feature Set Available for CloudCasa

By CIOReview | Wednesday, October 6, 2021

With the availability of new feature set for CloudCasa, enterprises can ensure that their cloud data is safe while the data storage cost is optimal.

FREMONT, CA: Catalogic Software has made a new feature set available for CloudCasa, the company's cloud-native backup-as-a-service platform. CloudCasa now backs up Kubernetes persistent volumes to cloud storage, including Amazon Elastic Block Storage (EBS) persistent volumes. It's available as part of a new subscription model based on capacity.

DevOps and IT teams can now be confident that their enterprise cloud data is safe and secure while also ensuring that they are not paying twice for storage to protect their Kubernetes applications, thanks to CloudCasa.

“CloudCasa is a simple yet complete data protection solution that supports Kubernetes applications and popular cloud-native services. It's easy to use thanks to CloudCasas friendly SaaS subscription model and its free options and availability in popular marketplaces,” said Enrico Signoretti, Senior Data Storage Analyst, GigaOm. “At the same time, CloudCasa simplifies data management, helping enterprises protect data no matter where your applications are today or will be tomorrow.”

Catalogics' CloudCasa is scalable data protection and disaster recovery service for cloud-native applications that protects and secures Kubernetes. It works with all of the most popular Kubernetes distributions, as well as managed services and cloud database providers.

“With the general availability of persistent volume backups for CloudCasa, we are excited to introduce a capacity-based subscription pricing that is simple and intuitive because it is based on how much data is being protected,” said Sathya Sankaran, COO of Catalogic Software. “Other Kubernetes backup products charge based on internal constructs such as worker nodes or clusters in addition to requiring users to bring their own backup storage. These models are unfair to the early adopters of Kubernetes who are charged based on the scalability of their application rather than on the amount of stateful or persistent data. Were happy to change the paradigm today.”