Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Velero is the most popular tool for backing up and restoring Kubernetes cluster resources and persistent volumes. However, there may be situations where you need to restore Velero backup data without using Velero itself. For example, if Velero is not installed and configured correctly, or if more fine-grained restore control is required. In this post, we will explore how to do this when either Restic or Kopia was used by Velero to store the persistent volume (PV) data.

It’s been about three months since the last CloudCasa feature release in April, and we are now approaching the Dog Days of summer. These, as you may know, are named for the heliacal rising of Sirius, the Dog Star, in this sultry season, though the term more often conjures images of dogs lazing in the hot summer sun. We have been doing no summer lazing here at CloudCasa, though! Since our April release, we have focused much of our development effort on performance and reliability improvements.

Velero is an open-source backup and recovery tool designed specifically for Kubernetes clusters. It provides a straightforward way to protect your Kubernetes resources, including persistent volumes, namespaces, and custom resources, by taking backups and restoring them in case of data loss or disaster recovery scenarios. In this blog you will learn the different use cases for Velero and the two ways to install Velero, using the Velero CLI and using a Helm chart.

A strong misconception abounds that managed providers are impervious to data loss. The truth, however, is that accidents can happen at any time, to any business. Finding a provider that takes data backup and protection seriously, therefore, is critical to the well-being of your business. Opti9—a leading provider of managed cloud solutions—is one company that is addressing this problem head-on.