Every repository in Cloudback has its own Settings card: whether backups are scheduled, when the next one runs, which schedule and storage it uses, and how long its backups are kept.
1
terraform apply, and your GitHub, GitLab, Azure DevOps, and Linear backup definitions are set.
With the Cloudback Terraform provider, schedule, storage location, and retention policy live in the same repo as the rest of your infrastructure.
#Terraform #IaC
15
Four ways to get your data back with Cloudback: download to your own machine, restore a single backup to any supported platform, bulk restore many repositories, or restore across platforms.
#DisasterRecovery #DevOps
1
12
Cloudback shows deduplication per repository: backups processed, backups deduplicated, total size, and space saved - from Last Week to Last Year, with a donut and a bar chart.
#DevOps #CloudStorage
5
In Cloudback's repository list, the State column shows whether each repo is backed up automatically: Scheduled or Not scheduled. Filter by Not scheduled to find any gaps, then fix them one repo at a time or in bulk with Bulk Operations. #DevOps
1
Cloudback's Operations API reads a backup definition with one request and updates its schedule, storage and retention with another. The request shape is the same for GitHub, GitLab, Azure DevOps and Linear, authenticated with an X-API-Key header.
13
A finished status doesn't tell you what's inside a Linear backup.
Cloudback's Workspace Details page lists exact counts: teams, projects, issues, comments, cycles, documents, labels, users, attachments, embedded files.
#Linear
3
Cloudback for Azure DevOps is on the Azure Marketplace, so repository backup goes on your existing Azure bill.
Pick a plan by repo count: $10 per 10/month, $75 per 100, $500 per 1000. Stack units to cover more.
#AzureDevOps
24








