Backup storage configuration

Storage configuration is where you connect the storage buckets your backups are written to, and set the backup rules for each bucket. Go to Backup > Storage configuration.

What has changed

In Backup V1.17

• More than one bucket. Connect several buckets, each in its own region. For example, keep EU users' backups in an EU bucket and US users' backups in a US bucket.
• Your existing bucket stays the default. Policies keep using it until you point them at another bucket.
• The bucket is chosen on the policy. Each user and shared drive policy says which bucket its backups go to.
• Backup rules for each bucket. Each bucket has its own retention, frequency and file type rules.
• Test one bucket or all of them. If a connection fails, an alert tells you which bucket.
• Edit or remove a bucket from Storage configuration.
• Saving a bucket shows the saved bucket, rather than opening a blank form.

In Backup V1.16

• Its own page. Retention period, backup frequency and file types are collapsible sections on the storage configuration screen.
• A connection test is required. A bucket is not active until you have run one. Until then it carries a Needs authentication badge on its card.
• Editing connection details needs a fresh test. Change anything about the connection and you are prompted to authorise it again, with an inline alert explaining why.
• Validation on save. Bucket name casing, service account email format, JSON file format and description length are checked as you save, rather than failing later.
• Disconnecting is protected. A bucket can normally only be disconnected once all CloudM data has been purged from it. If data remains, you get an alert rather than a silent failure.
• A guided empty state when no bucket is set up, prompting you to connect one by email or by storage account key.

Using more than one bucket

Each bucket you connect is listed in Storage configuration. Your first bucket is the default.

• A policy sends its backups to the bucket chosen on that policy. See Creating and editing a backup policy.
• Data already backed up stays in the bucket it was written to.
• Restoration and purge read the bucket from the backup itself, so you do not need to know where an item is stored.

To make another bucket the default, open it and turn on Default storage bucket. Any new backup policies will use this bucket by default.

Connecting a storage bucket

If you have not set one up yet, you will see an empty state prompting you to add a bucket, either via email or via a storage account key.

1. Choose Via email or Via a storage account key.
2. Fill in the bucket details. Depending on what you chose, this is either a service account email or a JSON file upload.
3. Select Save bucket.

Basic validation runs as you save. Bucket names must be lowercase, the service account email must be correctly formatted, the JSON file must be valid, and the short description must be under 100 characters.

Adding another bucket

Select Add storage bucket at the top of Storage configuration, then follow the same steps as for your first bucket. Each bucket appears in the Buckets list with its region and connection status.

You do not enter the region. It is set in Google Cloud when the bucket is created. CloudM supports US and EU regions only.

The new bucket's details and connection test work the same way as for your first bucket.

Testing the connection

Once the details are saved you are prompted to Test connection.

While the test runs, the inputs are disabled.

• If it succeeds, the bucket status changes to Connected and a re-test connection option appears.
• If it fails, an inline error explains the problem and what to do, alongside a notification.

You can test one bucket or all of your buckets. If a connection fails, the alert tells you which bucket.

To test every bucket at once, select Test all above the Buckets list.

Backup rules

Each bucket has its own backup rules, in collapsible sections:

• Retention period
• Backup frequency
• Enable backup window
• Enable include or exclude files

Expand a section to change it.

Retention period

Backup frequency

Backup scope

Enable include or exclude files

Editing a bucket

You can change bucket details directly on the form. Making a change brings up Update and Discard changes.

Setting a bucket inactive

Open the bucket and select Set as inactive. Your existing backup data stays in the bucket and can still be restored, but no new data is saved there.

Removing a bucket

A storage bucket can normally only be disconnected once all data has been purged.

If you try to disconnect while CloudM backup data is still in it, you will see an alert explaining why it cannot be removed. Where the bucket holds no CloudM data, you are asked to confirm.

Common questions

My bucket says Needs authentication

The details are saved but the connection test has not been run. Select Test connection.

The connection test failed and I cannot tell why

The test reports pass or fail. A mistyped bucket name, a permissions problem and an unreachable bucket can look the same, so check the bucket name, then the service account permissions, then whether the bucket exists. If you have several buckets, the alert tells you which one failed.

I changed retention here but a policy did not update

That policy's retention is marked Custom and no longer follows this default.

Which bucket do my existing policies use?

Your existing bucket, which stays as the default. Nothing changes until you set up another bucket and choose it on a policy.

Do I need to know which bucket a backup is in to restore it?

No. Restoration and purge read the bucket from the backup itself.

I cannot disconnect my bucket

It still holds CloudM backup data. Purge the data first. See Purge.