Customer Managed Storages
Last updated
Was this helpful?
Last updated
Was this helpful?
Cloudback allows you to store backup archives in your own storage, ensuring no copies are retained by us. Essentially, Cloudback creates a backup of your repository, transfers the archive to your designated storage, and then permanently deletes the archive from Cloudback's servers. This process guarantees that there are no copies of data on Cloudback servers.
Also, we offer our in-build storages named according to the storage geographic region: Cloudback US, Cloudback EU, Cloudback UK, Cloudback Sidney, and Cloudback Singapore.
You can find the list of all storages in the Storages page. The list contains all storages that you have created in Cloudback. You can see the storage name and the storage provider for each storage. You can use the Edit button to change the storage settings or the Delete button to remove the storage from Cloudback. Please note that you can't delete the storage if it is used by any repository.
The Storages page displays all registered storage options, including both built-in and customer-managed storages. To add your own storage, click on the + Add a new storage button. It initiates a storage setup wizard to assist you through the registration process.
You can create multiple custom storages in Cloudback and use them for storing backups of different repositories from different GitHub accounts. You can also use the same storage for storing backups of multiple repositories.
Each storage has a set of settings that you can configure:
Storage name - a name of the storage that will be displayed in the Cloudback dashboard. Try using a descriptive name that will help you to identify the storage later.
Storage provider - a storage provider that you want to use for storing backups. Currently, Cloudback supports a variety of storage providers, you can check the full list here.
Deduplication type - a deduplication type that you want to use for storing backups. For more details, please refer to the Deduplication documentation.
Archive type - an archive type that you want to use for storing backups, allowing you to enable or disable the password protection for your backups. For more details, please refer to the Password-Protected Archives documentation.
Archive name pattern - a pattern that will be used to name the archives stored in the storage. For more details, please refer to the Archive Name Pattern documentation.
You can change the storage for a particular repository in the Repository Details page. Also, you can assign it to multiple repositories through the Bulk Operations.
Cloudback supports a variety of storage providers. Please follow the link below to find additional details about particular storage:
Responding to user requests, we have integrated support for OpenStack Swift and Microsoft OneDrive. If you need support for another storage solution, please contact us or submit a feature request. We are open to considering the implementation of new storage options based on user needs.
We upload password-protected ZIP archives. The encryption password is securely stored on our end, safeguarded by multiple layers of security. In the unlikely event of unauthorized access to the storage, the intruder would only find encrypted archives, rendering them unable to access the contents of the archive.
