Customer Managed Storages
Cloudback allows you to store a backup archive in your own storage, leaving no copies to us. That is. Cloudback backs up a repository into an archive, sends the archive to your storage, and wipes the archive from Cloudback’s disk leaving no chance to recover any data from the Cloudback servers.
Also, we offer our
in-build storages named according to the storage location:
Cloudback Sidney, and
Register your storage
In order to tell Cloudback to store backups into your own storage, please use the
+ New storage button in the settings of the repository card. The button opens a simple wizard that guides you through the registration process. Please refer to a particular storage page to learn about specific steps.
Please note, that you could apply recently registered storage to all your repositories using the
Bulk Operations menu.
Please follow the link below to find additional details about particular storage:
- Cloudback in-build storage
- Microsoft Azure Blob Storage
- Microsoft OneDrive Personal
- Microsoft OneDrive For Business
- Amazon S3 Bucket via Access Point
- Amazon S3 Bucket via Access Key
- Amazon S3 Glacier
- Google Cloud Storage Bucket
- Alibaba Cloud Object Storage Service
- OpenStack Swift Container via S3 API
- Wasabi Bucket (S3 API)
Need another storage?
We added support of OpenStack Swift and Microsoft OneDrive within a feature request of our users. Contact us or create a feature request and we will consider implementing your storage.
What we upload to the storage?
We upload password-protected zip archives. The password is encrypted and stored at our side. The password is well protected behind several security layers. If someone breaks into any storage he will get useless encrypted archives and no chance to access archive content.