Automated Daily Backups
Last updated
Was this helpful?
Last updated
Was this helpful?
Cloudback's automated daily backup is a core feature designed to ensure your repositories and metadata are automatically backed up — without any manual intervention.
You can check if the repositories are automatically backed up by looking at the "Schedule" column in the repository list. If the column shows the schedule, the repository is being backed up automatically. If the column is empty, the repository is not being backed up automatically.
If you are using Card view of the dashboard, you can see the repository status in the card. If the backups are scheduled for the repository, you will see the Scheduled status. It means that Cloudback will automatically back up the repository.
Cloudback creates backups according to a schedule, saves them in a designated storage, and stores them according to your retention policy:
Backup Schedule: Set the time and frequency of backups. By default, backups are scheduled to run daily. The time of the backup is determined by the time zone you set during account configuration and can be changed in the account settings.
Storage Configuration: Choose where your backups are stored. Cloudback offers both Cloudback Managed Storages and Customer Managed Storages. By default, backups are stored in Cloudback Managed Storages.
Retention Policy: Define how long backups are stored. By default, backups are stored for 30 days.
If you prefer, you can customize the backup schedule, storage, and retention policy to better suit your needs.
You have full control over when backups occur. Whether you need backups to occur daily, weekly, or on a more complex schedule, you can adjust the timing through the user-friendly interface. For example, if your repositories are more active during business hours, you might schedule backups for early mornings or late nights to minimize interference.
You can change the backup schedule for individual repositories in the repository settings by selecting the desired schedule:
Backup Storage is where your backups are stored. Cloudback offers two types of storage options:
You can change the storage for individual repositories in the repository settings by selecting the desired storage:
The Retention Policy gives you control over how long your backups are stored. With predefined retention options ranging from 30 to 360 days, you can select the right duration based on your needs, ensuring optimal storage use.
You can modify retention policies for individual repositories by opening the repository settings and selecting the desired retention period:
As you set up automated backups, it’s important to manage the number of repositories included in your Cloudback plan. Under the Subscriptions menu, you’ll find all the necessary details:
Purchased: The total number of repositories your plan supports.
In Use: How many of those repositories are currently scheduled for backup.
Remaining: How many more repositories you can still schedule under your current plan.
This helps you track your repository usage and make informed decisions about whether you need to upgrade your plan or adjust your backups.
Cloudback's scheduling process is sensitive to the time zone you define. The time zone is set during the initial account configuration and affects all automated tasks. If your needs change, you can easily update the time zone through the Account Settings page, ensuring your backups run exactly when you expect.
This is particularly useful when coordinating across multiple teams or regions, as the flexibility to adjust time zones makes Cloudback adaptable to global workflows.
You can also update the schedule for multiple repositories at once using the , making it easy to manage backups across your organization.
Cloudback Managed Storages: Cloudback provides storage for your backups. By default, backups are stored in Cloudback Managed Storage. Learn more about .
Customer Managed Storages: You can use your own storage to store backups. You can configure your storage in the Storages page. Learn more about .
The storage can be updated for multiple repositories at once using the , making it easy to manage backups across your organization.
You can apply retention policies in bulk from multiple repositories using the .
