Step 1: Log in to the BDRCloud console. Navigate to the Infrastructure-> Object Storage and click on the ‘Create New Object Storage Repository’ button.
Step 2: Enter the following details:
For the Repository Type, choose S3 Compatible
In the Repository Name field, specify a name for the new object storage repository
Enter the Service Endpoint (Example - s3.us-west-002.backblazeb2.com ), which will enable connectivity to the Backblaze Cloud Storage account from the BDRCloud Server
Specify the Data Center (DC) Region
Step 3: From the Credentials drop-down list, select user credentials to access your Backblaze storage account if you already have added the credentials. Otherwise, click the Add New Credential button which opens a dialog box.
Specify a credential name to identify your credential record, and provide the Secret Key and Access Key of your Backblaze Cloud Storage Account
Note: In your Backblaze account, navigate to App Keys under the Account tab and click on Add a new Application Key to find the KeyID which will be the Access Key, and the applicationKey which will be your secret key both of which will be S3 compatible.
Step 4: From the Bucket Name drop-down list, select a bucket. Make sure that the bucket where you want to store your backup data is created in advance.
In your Backblaze account, navigate to Buckets under the B2 Cloud Storage tab and click on Create a Bucket to create a new bucket.
Step 5: Choose a cache location to store backup data temporarily before uploading it to the Backblaze Cloud Storage. Local drives and Network drives added to the BDRCloud Server will be shown in the dropdown list which can be selected as Cache Location.
Step 6: Once all the fields are configured, click the ‘Create’ button and the Backblaze cloud will be added as a Backup Repository.
Cache Location "It is the folder path for storing backup data temporarily before it is uploaded to the target Object Storage Repository. Ensure you add and select the network drive you plan to use
Note : If the drives added in BDRCloud console for Cache location are different / inaccessible to any BDRCloud agent then you can update the new drive which are accessible to the agents, Edit the backup Job or while configuring the backup job under Action click the Storage Icon update the new drive and save the backup configuration
Related Articles
Quick Start Guide for oVirt Backup & Recovery
About oVirt Backup & Recovery BDRShield provides agentless, image-level backups for oVirt virtual machines, leveraging Changed Block Tracking (CBT) for efficient incremental backups and supporting automated scheduling. Backup data is secured with ...
Quick Start Guide for AWS Backup & Recovery
About AWS Backup & Recovery BDRShield offers backups for AWS EC2 instances, utilizing native snapshots for efficient backup and recovery. It supports incremental backups to optimize storage and bandwidth usage, with secure storage options across ...
Quick Start Guide for PostgreSQL Backup &Recovery
About PostgreSQL Backup & Recovery BDRShield provides comprehensive backup solutions for PostgreSQL databases. Automated backup scheduling ensures regular backups without disrupting database operations, while granular recovery allows for restoring ...
Quick Start Guide for MySQL Backup & Recovery
About MySQL Backup BDRShield offers a robust solution for safeguarding MySQL databases with automated incremental backups, secure storage, and granular recovery capabilities. Backups can be stored locally, remotely, or in the cloud, all centrally ...
Quick Start Guide for KVM Backup & Recovery
About KVM Backup & Replication BDRShield provides a robust and reliable solution for protecting KVM-based virtual environments. It supports full and incremental backups, flexible scheduling, offsite replication, and centralized management. Whether ...