Cloudback Docs
HomePricingBlogContactSign In
  • Getting Started
    • What is Cloudback?
    • Installation Guide
    • First Backup Walkthrough
  • Managing Backups
    • Automated Daily Backups
    • Metadata Backups
    • One-Click Manual Backups
    • Setting Backup Schedules
    • Manage Backup Storage
    • Backup Retention Policy
    • Password-Protected Backups
    • Account Settings
    • Bulk Operations
    • Data Deduplication
    • Email Notifications
    • Instant Notifications
    • Archive Name Pattern
  • Data Restoration
    • Download Backups
    • Restore to GitHub
  • Automation
    • Terraform Provider
    • Operations API
  • Dashboard
    • Dashboard Overview
    • Card view
    • Table view
    • Repository Details
    • Backup Details and Metadata
    • Backup Status Badge
  • Storage Configuration
    • Cloudback Managed Storages
    • Customer Managed Storages
    • Replicating Backups
  • Supported Storages
    • Alibaba Cloud Object Storage Service
    • Amazon S3 Bucket via Access Key
    • Amazon S3 Bucket via Access Point
    • Amazon S3 Glacier
    • Amazon S3 Object Tagging
    • Google Cloud Storage Bucket
    • Microsoft Azure Blob Container
    • Microsoft OneDrive Business
    • Microsoft OneDrive Personal
    • OpenStack Swift
    • Wasabi Customer Managed Storage
  • Account and Billing Management
    • Payment Methods
    • GitHub Organizations
    • Invoiced Customers
  • Troubleshooting and Support
    • Known Issues
    • Contact us
  • Security Features
    • Access Review: Vanta Integration
    • Immutability: Amazon S3 Object Lock
    • Encryption: Password-Protected Archives
    • Traceability: Audit Log
  • Legal
    • Terms of Service
    • Privacy Policy
Powered by GitBook
LogoLogo

Learn more

  • Integrations
  • Blog

Explore

  • Roadmap
  • Changelog

Support

  • Contact Us
  • Status

Legal

  • Terms of Service
  • Privacy Policy

© 2025 Cloudback

On this page
  • Notification settings
  • Why can a backup fail?
  • 1. Storage issue
  • 2. GitHub account issue
  • 3. Cloudback issue
  • 4. GitHub outage
  • Learn More

Was this helpful?

  1. Managing Backups

Email Notifications

PreviousData DeduplicationNextInstant Notifications

Last updated 5 months ago

Was this helpful?

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.

Notification settings

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.

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. GitHub account issue: The Cloudback application does not have the necessary permissions to access the repository or the application is not installed.

  3. Cloudback issue: There is an issue with the Cloudback application.

  4. GitHub outage: GitHub 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

2. GitHub account issue

There can be two types of issues related to your GitHub account:

  • 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.

3. Cloudback issue

4. GitHub outage

Learn More

By default, all email notifications are sent to the of a GitHub account.

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

The installation of 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.

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 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 where you can check the operational status of the 'API Requests'.

primary email address
here
Cloudback App
contact us
GitHub Status
Instant Notifications
Customer Managed Storages
Notification email
Account notification email