We discussed in previous blogs the need for data protection for Kubernetes and what’s different about CloudCasa. CloudCasa was designed to address the gap in data protection and disaster recovery that exists in all the leading Kubernetes distributions and managed cloud services. Further, another pain point that CloudCasa addresses is that your cloud-based applications may well be hybrid and multi-cloud applications that use both container-based storage and serverless databases. This is not unlike your on-premises applications that run in different server, virtualization, and storage infrastructures. CloudCasa was designed to support hybrid, distributed, multi-cluster, and multi-cloud environments.
One of our early beta users challenged us on why CloudCasa was needed when there is already backup for a Kubernetes cluster available in Azure. Indeed, Azure’s best practices guide for storage and backups in Azure Kubernetes Service states: Back up your data using an appropriate tool for your storage type, such as Velero or Azure Backup.
The Azure Backup service is a file and VM-level backup that is not container or cluster aware, so it is not suitable for recovering cluster configuration and application state. While Azure Backup does support all of Azure’s databases, CloudCasa will also support these and the serverless databases of other cloud services.
Velero is an open source, CLI-based tool that needs infrastructure to be provisioned and supported for it. Then you need to manually setup and configure it for each cluster you have, including the backup storage target for each cluster.
Top 10 Reasons for Using CloudCasa instead of Velero
10. Backups are Monitored: We monitor backup success rates across customers, debug your problems, and proactively inform you when you could do something to improve your success rates.