Post-installation tasks

Once you have successfully installed CloudCasa, there are some additional tasks that you need to complete before performing backups.

Only users defined in auth.allowedUsers or auth.allowedUserGroups will initially be allowed to log in to CloudCasa. At initial login, each user is the administrator of their own organization. As administrator, they can invite other users to join their organization regardless of whether those users are listed in auth.allowedUsers or auth.allowedUserGroups.

In practice, if only one organization is needed in CloudCasa, you may only need to add one user to auth.allowedUsers at configuration time. After initial setup, that user can then log in and create invitations for whatever other users need access.

From this point, configuration is done by the organization administrator(s) on a per-organization basis.

First, you must configure object storage that will be used to store backup data. This can be done by going to Configuration => Storage and clicking on Add storage. CloudCasa supports adding any S3-compatible storage as well as Azure blob storage. For more details on adding storage, see https://docs.cloudcasa.io/help/mystorage.html.

After adding at least one objectstore, you can configure it as the organization default for all Kubernetes backups. This can be done in Configuration => Storage. Note that users will still be able to select different storage locations on a per-cluster or per-backup level if they wish. The organization default is used only if it isn’t overridden by a lower-level selection.

At this point, you are ready to add clusters and define policies and backups. Here are some useful pointers:

• To add and manage clusters: https://docs.cloudcasa.io/help/clusters.html

• To add and manage policies: https://docs.cloudcasa.io/help/configuration-policy.html

• To define cluster backups: https://docs.cloudcasa.io/help/protection-cluster-backup.html

• To define cluster restores: https://docs.cloudcasa.io/help/protection-cluster-restore.html

Note

While the online user guide applies to both the SaaS and Self-hosted versions of CloudCasa for the most part, there are some sections that apply only to the SaaS version (e.g. billing and payment related content).

Scheduling storage maintenance

CloudCasa runs storage maintenance tasks once a day by default. The exact time when these tasks run varies and is chosen automatically by the system. Since backups and storage maintenance cannot run simultaneously, it is ideal to schedule the storage maintenance when no backups are scheduled. This can be done by in Settings page. For details, please visit https://docs.cloudcasa.io/help/settings.html and check Advanced options => Storage maintenance scheduling policy (optional).

Catalog Backup

If you are using CloudCasa-installed MongoDB, you should configure the Catalog backup. For details, please see Catalog backup/restore.