CloudCasa is a powerful and easy-to-use Kubernetes and cloud database backup service for developers, DevOps and IT Ops teams. With CloudCasa, you don't have to be a storage or data protection expert to get started with backing up your cluster resource and their persistent data.
Just follow the simple steps below to get started with CloudCasa's Kubernetes and Amazon RDS backups.
The CloudCasa agent must be installed on every Kubernetes cluster that you want to protect. Installation and configuration is rapid and easy - just follow the steps below which include the ability to auto-discovery your clusters in your cloud accounts.
Point your favorite web browser to home.cloudcasa.io and create an account. No payment information is required for the Free service plan. Once you've signed in, you can invite other people to join your organization under Configuration/Users.
If some of your Kubernetes clusters are running in AWS, Azure, or GCP, we recommend adding your cloud accounts under Configuration/Cloud Accounts. This allows CloudCasa to auto-discover your EKS, AKS, and GKE clusters, back up EKS, AKS, and GKE cluster parameters, auto-create clusters on restore, and automatically back up non-CSI EBS volumes on EKS. For some configurations, it also gives you the option of auto-installing the agent.
If your clusters were auto-discovered, you'll just need to find them in the Clusters list under your cloud account in Configuration/Cloud Accounts and click on the install icon for each one. If not, you can add them manually by clicking Add cluster under Protection/Clusters Overview. Then enter your cluster name and description and click Register cluster. Either way, you will see a cluster ID and a kubectl command to run that will install a lightweight agent on the cluster. If you are installing via our Helm chart or via a partner marketplace instead, make a note of the Cluster ID and follow the instructions specific to your installation method. Once installed, the agent will connect and register itself with the CloudCasa service, completing the process.
A backup policy allows you to define when backups that use it will run, and for how long they will be retained. You can have multiple schedules with different retention times in one policy. For example, a policy may specify the creation of hourly backups that are retained for 7 days, and daily backups that are retained for 30 days. You can add or edit policies under Configuration/Policies. Add a new one by clicking the "Add policy" button.
Go to the dashboard and click Define Backup. Enter the name for your backup and select your cluster. Choose what namespaces to protect and/or select resources by tag. Choose whether to create local snapshots of your PVs or copy them to CloudCasa’s secure storage. By default, everything will be protected including PVs. Finally, select the policy to apply. If you create a backup with no policy, it will not run automatically but can be started manually on an ad hoc basis.
That's all there is to it! Now you can sit back and relax, knowing that your clusters are protected.
If you don't already have a CloudCasa account, you can create one now for free!
Select the Configuration tab and select Cloud Accounts. Then click Add Cloud Account and select Amazon Web Service. Then click Next and hit the Launch Stack button. This will open a browser tab that will prompt you to sign in to AWS, and will then launch a CloudFormation stack that will grant CloudCasa the access it needs. Be sure to log in as an administrator so that CloudFormation can run.
Do this for each of your AWS account containing RDS databases. After adding your accounts, any RDS databases in them will be auto-discovered and appear in the CloudCasa UI under Protection/Databases Overview.
Go to Protection/Databases Backups and click the “Define Backup” button in the upper right corner of the screen. The “Add backup” pane will open, and you will be able to select one or more databases to include in your new backup definition. You can also choose to select the databases to include using AWS tags. In this case, any databases tagged with the name/value pairs you enter at the time the job runs will be selected. Click “Next” once you have chosen databases to proceed to the next page. Here you can set a name for your backup and choose whether or not to have it copy to another region. Then click "Next" again.
If you are protecting a database that is part of a Kubernetes application, you may want to use the same backup policy that you use for the application’s namespace. You can also create a new policy, or select "None" if you want to initiate backups manually. When selecting "None", you can choose to enable the Run Now option to start an ad-hoc backup immediately.
This video will take you through all the following points and give you a clear idea of how CloudCasa Backup and Restore works.
CloudCasa is a powerful and easy to use Kubernetes ...