Email Notifications
Last updated
Last updated
Email notifications are a great way to keep track of your backup status. Cloudback emails you notification in case the backup fails. If something goes wrong and a backup process fails, we will email you notification. We send a daily notification at 22:00 UTC with all failed automatic backups in the last 24 hours.
Once a backup has failed, our 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 email notifications are only enabled for automatic backups. Cloudback does not send email notifications for manual on-demand backups.
By default, all email notifications are sent to the primary email address of a GitHub account.
However, the email address for failed backup notifications can be changed in the Notification Settings page:
To change the email address, enter the new email address and click on the Save button to save the changes.
A backup can fail for various reasons. The most common reasons are:
Storage issue: The storage is not available or the Cloudback application does not have the necessary permissions to write to the storage.
GitHub account issue: The Cloudback application does not have the necessary permissions to access the repository or the application is not installed.
Cloudback issue: There is an issue with the Cloudback application.
GitHub outage: GitHub is not available.
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
In order to troubleshoot a storage issue, please verify your storage settings using the Storages page. Learn more about setting up and managing storage here.
There can be two types of issues related to your GitHub account:
The installation of Cloudback App may be suspended or uninstalled from your account. If the app is uninstalled, Cloudback will not be able to access your data, so the backup will fail.
The repository may be deleted or inaccessible to the Cloudback App.
Your GitHub account may be locked or suspended. This is rare, but does happen. Please check if your account is accessible.
Sometimes the backup software itself can fail. This happens and our 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.
GitHub itself can go offline. This sometimes happens and can take a few hours. Cloudback will try to back up 6 times in 6 hours. If nothing works, a backup will fail. There is a page GitHub Status where you can check the operational status of the 'API Requests'.
