Microsoft Azure Blob Container
Configure Microsoft Azure Blob Container as a secure, scalable storage solution for your GitHub repository backups in Cloudback using Shared Access Signatures.
Last updated
Was this helpful?
Configure Microsoft Azure Blob Container as a secure, scalable storage solution for your GitHub repository backups in Cloudback using Shared Access Signatures.
Last updated
Was this helpful?
One of the ways to back up a GitHub repository using customer managed storage is to use your own Azure Container. Azure Blob Storage is Microsoft's object storage solution for the cloud. Blob storage is optimized for storing massive amounts of unstructured data, therefore it can be used as a storage for GitHub repository backups created by Cloudback.
This page describes how to set up your own Azure Blob Container as a customer managed storage for Cloudback backups of your GitHub repositories. To be able to use your Azure Blob Container as customer managed storage, you need to have an existing Azure storage or create a new one. Also, you should create a new shared access signature for that storage.
Azure Blob storage is Microsoft's object storage solution for the cloud that is optimized for storing massive amounts of unstructured data. Unstructured data is data that doesn't adhere to a particular data model or definition, such as text or binary data. Azure Storage is a Microsoft-managed service that provides highly available, secure, durable, and scalable cloud storage.
To set up Microsoft Azure Blob Container as a storage for your backups, follow the steps below.
Type a storage name in the Storage name field. Use a name that will help you identify this storage in the future.
Select Microsoft Azure Blob Containers from a Storage Provider dropdown:
Choose the settings for the storage:
Deduplication type - enable or disable data deduplication. For more details, please refer to the Deduplication documentation
Archive type - enable or disable archive password protection. For more details, please refer to the Password-Protected Backups documentation
Archive name pattern - configure the archive name pattern, which is used to generate the name of the backup archive. For more details, please refer to the Archive Name Pattern documentation
To upload backups to Azure Blob Storage, you need to have a container. You can find more information on how to create a container in the Azure Blob Storage documentation. If you already have a container, you can skip this step.
The Shared Access Signature (SAS) is a URI that grants restricted access rights to Azure Storage resources. You can create a new SAS in the Azure Portal using the instructions provided in the Azure documentation. When creating a new SAS, make sure to grant the following permissions:
Create and Read
Write - this permission is required by Azure for multipart uploads of large archives
Delete - this permission is required by Cloudback to delete old backups by retention policy. Grant this permission for the retention policy to work correctly.
In the Step 3 field, provide the Blob SAS URL of the SAS created in the previous step. The SAS URL is required so Cloudback can upload backups to the correct container.
Open the Cloudback Dashboard
Navigate to the Storages page by clicking on the Storages link in the left-side navigation pane
Click on the + New storage button:
Click on Save button to save the new storage. You can also use a Test button to check if the storage is configured correctly. After saving the storage, you can use it for storing backups of your repositories.
All storage settings can be changed later in the Storages page. To edit the storage settings, click on the Edit button next to the storage you want to edit.
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.
