The Storage page allows you to define, view, and edit storage targets for backups and mirgration/replication jobs. From the menu bar, go to Configuration/Storage.

For CloudCasa Pro backups, it is only necessary to define storage endpoints here if you wish to use user-supplied storage.

For CloudCasa Velero Management, at least one separate storage location must be defined for each cluster running Velero.

Migration and replication jobs can use storage defined here as transient storage.

Two tabs are available on the Storage page, Backup storage and Snapshot storage. The Backup storage tab lists user-defined object storage for both CloudCasa Pro and Velero backups. The Snapshot storage tab is used only for Velero backups, and lists Velero VolumeSnapshotLocations (VSLs).

Storage for CloudCasa Pro backups

You have a choice of where to send backup data with CloudCasa Pro backups. You can use CloudCasa’s secure cloud storage, 100 GB/month of which is included for free in all service plans, or you can use your own object storage. If you wish to use your own object storage, you must define the endpoints for it here. Note that configuring storage here is not required to use CloudCasa Pro backups.

CloudCasa supports most types of object storage that are compatible with the Amazon S3 API or Microsoft Azure Blob storage as user-supplied storage.

For CloudCasa Pro backups, storage locations are global and can be shared across multiple clusters. Many clusters can back up to the same storage and CloudCasa automatically handles separation of data among these clusters.

A global “Default storage” location for your organization can be set at the top of the page. The default is inherited by all clusters and backup jobs unless overridden. Note that a change in Storage target for a backup will trigger a full backup the next time backup are run.

Storage for Velero backups

For Velero backups, two types of storage locations can be defined. BackupStorageLocations (BSLs) are object storage endpoints used for storing backup data. VolumeSnapshotLocations (VSLs) are locations used for storing snapshot data. All BSLs defined in your environment are displayed under the Backup Storage tab. All VSLs are likewise displayed under the Snapshot Storage tab.

Velero requires that a separate BSL for each cluster must be created. Sharing the same BSL across multiple clusters can lead to data loss. You can use the same S3 bucket for different BSLs provided you set up a unique prefix for each cluster during configuration. CloudCasa for Velero will automatically detect duplicate BSLs and alert users about potential data loss.

Note that Velero continually verifies and validates BSLs and sets the “Available” state to “No” if it detects access or connectivity issues. This availability status is reflected in the Status column. Validation Frequency is 1 minute by default.

CloudCasa for Velero supports most types of object storage that are compatible with the Amazon S3 API or Microsoft Azure Blob storage as BSLs. S3 Storage from AWS, Azure and GCP have been explicitly tested and certified, but it is reasonably safe to assume that if your BSL works with Velero, it will work with CloudCasa for Velero.

Adding storage for CloudCasa Pro backups

  1. In the Storage page, select the Backup storage tab and click Add storage +.

  2. Select CloudCasa as the Storage Type. You must specify the following fields:

    Is your storage isolated/restricted from Internet access?

    Choose Yes if your storage is not reachable via the public Internet.

    Proxy cluster

    If the storage is marked as isolated, you must choose a cluster with an active CloudCasa agent which will be responsible for performing management operations on the storage. The storage must be reachable from this cluster.

    You can also optionally add a proxy cluster for non-isolated storage if you wish for maintenance operations to be run from a local cluster, but this should not normally be necessary. By default, service operations will be run from CloudCasa’s cloud infrastructure.

    Disable TLS certificate validation

    It is recommended to not enable this setting. Enabling it allows connections to the storage endpoint even if the server certificate is self-signed or expired, or if the domain name does not match the host.

  3. Click Next.

  4. In the Provider step, choose the Provier Type using the following options:

    Amazon S3 storage

    Take the following steps to register Amazon S3 or S3-compatible object storage with CloudCasa:

    Bucket name

    Enter the bucket name of the S3 storage.


    Enter the regional endpoint URL of the S3 storage. It usually is of the format “https:://”. E.g:,,


    Enter the region under which the Amazon S3 bucket is created. ( This is not applicable for non-AWS buckets )

    Access key

    Enter the access key of the S3 storage.

    Secret key

    Enter the secret key of the S3 storage.

    Azure Storage

    Take the following steps to register a Microsoft Azure Blob storage endpoint with CloudCasa:

    For required permissions see Permissions required for accessing Azure Blob Storage.

    Resource Group Name

    Enter the resource group name that will be used to hold all resources for the storage.

    Storage Account Name

    Enter the name of the storage account created under the same resource group.

    Subscription ID

    Enter the subscription ID of the Microsoft Azure plan that you have purchased.


    Enter the region name associated with the resource group.

    Tenant ID

    Enter the tenant ID associated with the Microsoft Azure subscription.

    Client ID

    Enter the unique Client (Application) ID assigned by Microsoft Azure when the application was registered.

    Client Secret

    Enter a valid client secret of the Service Principal.

  5. Click Next

  6. In the Summary step, you will see a summary of the above, and will need to define:


    Display name for the Storage location.

  7. Click Save.

Adding Velero Backup Storage Locations

  1. On the Configuration/Storage page, select the Backup storage tab and click Add Storage +.

  2. Select “Velero” as the Storage Type. You must specify the following fields:


    Name of the Cluster the BSL is configured in.


    Read/Write implies the BSL is configured for backup and recovery on a cluster. ReadOnly implies the BSL is mapped for recovery purposes alone on a cluster. If CloudCasa for Velero identifies identical BSLs mapped in more than one cluster as Read/Write, it will alert users about potential data loss.


    Velero allows you to set a BSL as the default storage for backups. If multiple BSLs are defined as default in the same cluster, Velero random rotates among these default storage options. Default BSL can be overridden by the Backup Specifications.

    Bucket Name

    Name of the S3 Bucket


    A Prefix is set when the same bucket is shared across multiple clusters. The BucketName+Prefix combination for BSLs must be unique, unless a BSL is being mapped in ReadOnly AccessMode.

  3. In the Provider step, you choose Provier Type using the following options:

    Amazon S3 or S3 Compatible Storage

    You can add S3 Storage Endpoint through two authentication methods: AWS IAM Roles for Service Accounts(IRSA) and AWS credentials that are AccessKey/SecretKey based. IRSA method is recommended for better auditability and role management, but AccessKey/SecretKey method is supported by most object storage vendors. See the Spec for AWS BSLs.

    Azure Blob Storage

    You can add Azure Blob Storage as a backup target through two authentication methods: Azure Service Principal and Azure Storage Account Access Key. The Service Principal method is recommended for better auditability and role management. If using Access Key, it is recommended to rotate and regenerate keys regularly manually or through a Key Vault. See the Detailed Spec for Azure BSLs.

    • For both methods, you will need: Resource Group Name and Storage Account Name

    • For Service Principal authentication, you will also need: Subscription ID, Tenant ID, Client ID, Client Secret

    Google Cloud Storage

    You can add Google Cloud Storage (GCS) or GCS-compatible storage through two authentication methods: Google Service Account Key and Google Workload Identity. Google Workload identity is the recommended method. Detailed Spec for Google BSL is available here.

    • For both authentication methods, you will need: Google Access ID

    • For the Google Service Account Key method, you will need: Type, Project ID, Private Key, Client Email, Client ID, Auth URI, Token URI, Auth Provider X509 Certificate URL, Client X509 Cert URL. You can import a JSON file with these values if performing this action repeatedly for each cluster.

    • For the Google Workload Identity method, you will need: Kubernetes Service Account Namespace, Kubernetes Service Account Name, Service Account.

  4. In the Summary step, you see some selected options and you can add additional properties by editing Yaml in the upper right corner.


    You must assign a name for the storage.

Adding Velero Volume Snapshot Locations

A volume snapshot location is a location in which volume snapshots created by Velero backups can be stored. Velero can be configured to take snapshots of volumes from multiple providers. Velero also allows you to configure multiple possible VolumeSnapshotLocation per provider, although you can only select one location per provider at backup time.

In the Storage page, select the Snapshot Storage tab and click Add storage +. You must specify the following:


Name of the Cluster the VSL should be configured in.

Provider Type

Available options are AWS/S3 Storage, Azure Blob Storage and GCP/GCS Storage. For each storage type, different options are presented to configure the VSL.


In order to configure your VSL in AWS, you must select the Region you want to store the snapshots in, VSL Profile Name (e.g. Default), and credentials through Access/Secret Key or IRSA. See the Spec for AWS VSLs.

Azure VSL:

In order to configure your VSL in Azure, you must provide the Resource Group Name, Subscription ID, and the details for Authentication either through Azure Service Principal or Azure Storage Account Access Key. Azure supports selection of snapshot type (Full or Incremental). Full snapshot is the default. See the Spec for Azure VSLs.


In order to configure your VSL in GCP, you must provide the Region and Project Name. See the Spec for GCP VSLs.