Get Started
Configure CloudCasa in 4 Simple Steps
Go to the Setup tab and click Add New Cluster
After entering your cluster name and description, you will be given a kubectl command to run that will install a lightweight agent on the cluster. If you are installing via a Helm chart, make a note of the Cluster ID and follow the Helm chart instructions. Once installed, the agent will connect out and register itself with the CloudCasa service, completing the process.
Create a backup policy by clicking Add New in the policies list
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.
Go to the dashboard and click Define Backup
Enter the name for your backup and select your cluster. You can optionally choose what namespaces you want to protect, select resources by tag, and choose whether or not to snapshot your PVs. By default, everything will be protected. Finally, select the policy that will apply to this backup. If you create a backup with no policy defined, it will not run automatically but can be started manually on an ad hoc basis.
You’re done!
That’s all there is to it! Now you can sit back and relax, knowing that your cluster is protected.
Configure Amazon RDS in 4 Simple Steps
Log in to CloudCasa
Select the Protection tab and select Accounts. Then click Add New Account.
Next, click 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.
Go back to Cloud Casa UI, select Databases.
Click the “Define Backup” button in the upper right corner of the screen. The “Add new 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 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.
Select a Policy for your backup
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. For None, you can choose to enable the Run Now option to start an ad-hoc backup immediately.
Now click Confirm and your backup definition is done!
Resources
Kubernetes Restore Guide
We’ve put together this quick restore guide to help make the process as easy for you as possible
CloudCasa Datasheet
CloudCasa is a simple, scalable and cloud native backup service built for protecting Kubernetes
