Storage configuration has been rebuilt as its own screen. Unlike the rest of the Backup interface, this screen has gained behaviour as well as a new layout, so it is worth reading even if you have connected a bucket before.
What has changed
- Its own page. Retention period, backup frequency and file types are now collapsible sections on the storage configuration screen.
- A connection test is now 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.
Storage configuration is where you connect the storage bucket your backups are written to, and set the defaults that new policies inherit. Go to Backup > Storage configuration.
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.
- Choose Via email or Via a storage account key.
- Fill in the bucket details. Depending on what you chose, this is either a service account email or a JSON file upload.
- 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.
Testing the connection
Once the details are saved you are prompted to Test connection.
A bucket is not active until a connection test has been run. Until then it carries a Needs authentication badge on its card.
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.
Backup Rules
Storage configuration also holds the defaults that new backup policies inherit, 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
Important: changing a default here does not reach any policy whose retention is marked Custom. See Creating and editing a backup policy.
Editing a bucket
You can change bucket details directly on the form. Making a change brings up Update and Discard changes.
Note: any change to the connection details needs a new connection test and authorisation. An inline alert tells you when that is the case.
Disconnecting 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.
I changed retention here but a policy did not update
That policy's retention is marked Custom and no longer follows this default.
I cannot disconnect my bucket
It still holds CloudM backup data. Purge the data first. See Purge.