Email Notifications

Email notifications are a great way to keep track of your backup status. Cloudback emails you a notification in case a backup fails. Email notifications work across all supported platforms. Cloudback sends a daily notification at 22:00 UTC with all failed automatic backups in the last 24 hours.

Once a backup has failed, the Cloudback support team will also be notified. If the problem is not related to storage, the team will start investigating as soon as possible and notify you of the results via email.

Please note that backup failure notifications are only enabled for automatic backups. Cloudback does not send them for manual on-demand backups.

Notification settings

By default, all email notifications are sent to the email address associated with your account in Cloudback's identity system.

However, the email addresses for failed backup notifications can be changed in the Notification Settings page:

To change the recipients, enter the email addresses and click on the Save button to save the changes. Separate the addresses with commas to notify several people. The field holds up to 1024 characters.

To check the settings before a real backup fails, click on the Send test email button. Cloudback sends a sample notification to the addresses in the field, with a [TEST] prefix in the subject. If the field is empty, the test is sent to the address a real notification would use.

Restore notifications

Cloudback also emails you when a restore finishes, both when it succeeds and when it fails. The email names the source backup and the restore target, and a failed restore includes the error message.

Restore notifications go to the same addresses as failed backup notifications, so the Notification Settings page controls both.

Why can a backup fail?

A backup can fail for various reasons. The most common reasons are:

1. Storage issue: The storage is not available or the Cloudback application does not have the necessary permissions to write to the storage.
2. Platform account issue: The Cloudback application does not have the necessary permissions to access your data or the application is not installed.
3. Cloudback issue: There is an issue with the Cloudback application.
4. Platform outage: The platform is not available.

1. Storage issue

The issue related to storage is the most frequent cause of backup failures. Usually, Cloudback loses access to your storage and is unable to upload an archive. Below are typical situations:

• An access token or shared signature has expired
• Storage configuration has been changed, but Cloudback config was not updated
• Storage provider went offline

To troubleshoot a storage issue, please verify your storage settings using the Storages page. Learn more about setting up and managing storage here.

2. Platform account issue

The platform integration may be suspended, uninstalled, or have insufficient permissions. Verify that:

• The Cloudback application is still installed and authorized for your account
• The repository or workspace is accessible and has not been deleted
• Your platform account is not locked or suspended

3. Cloudback issue

Sometimes the backup software itself can fail. This happens and the Cloudback support team is responsible for restoring the backup, analyzing the cause and making any necessary changes to prevent this from happening in the future. Please contact us if you believe this is the case.

4. Platform outage

The platform itself can go offline. Cloudback automatically retries failed backups for transient errors such as rate limits and timeouts. If all retry attempts fail, the backup is marked as failed.

Learn More

• Instant Notifications
• Customer Managed Storages