Backup Service across clouds
The cloud-native backup service - AWS Backup, Azure Backup, Google Backup and DR - with a plan that is assigned to resources and a vault that refuses to lose them.
8 verified modules - all static-validated and publish-checked; live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| Alibaba Cloud | A WORM Backup Vault with Your Key, a Daily Policy, and the Instances Bound to It | static-validated |
| AWS | Backup Vault, Plans and Vault Lock | static-validated |
| Azure | Backups that Survive Whoever Gets Into the Vault | static-validated |
| Google Cloud | A Backup Vault with Enforced Retention and Resources that Follow It | static-validated |
| Huawei Cloud | A CBR Policy and a Multi-Zone Server Vault that Grows Before It Fills | static-validated |
| IBM Cloud | A Backup Policy that Selects by Tag, Backs Up Daily and Copies to a Second Region | static-validated |
| Oracle Cloud | A Fleet Backup Policy with Daily and Weekly Schedules, a Second Region, and Deletion Prevented | static-validated |
| Tencent Cloud | A Snapshot Schedule That Tells You What It Will Cost and What It Will Not Survive | static-validated |
How to choose
Every one of these is a vault plus a plan plus an assignment, and the common state is a plan with nothing assigned. Compare how resources are selected (a tag, an explicit list, a resource type), what the vault can refuse (deletion, shortening retention, the account owner), and whether a backup can be copied to another region or account.
When not to use
A backup that has never been restored is a hope. Retention that is immutable protects against the attacker; a restore drill protects against the backup itself being wrong.