Creating an Azure-backed backingstore

Create an Azure-backed backing store using the MCG command-line interface or a YAML file to add storage resources.

Before you begin, ensure the following:

Fusion Data Foundation Platform is running.
Download the MCG command-line interface for easier management.
```
subscription-manager repos --enable=rh-odf-4-for-rhel-8-x86_64-rpms
```
```
yum install mcg
```
Note: Specify the appropriate architecture for enabling the repositories using the subscription manager. In case of IBM Z infrastructure, use the following command:
```
subscription-manager repos --enable=rh-odf-4-for-rhel-8-s390x-rpms
```
Alternatively, you can install the MCG package from the RPMs found at Download Red Hat OpenShift Data Foundation page.

Note: Choose the correct Product Variant according to your architecture.

Create an Azure-backed backingstore using MCG command-line interface

From the MCG command-line interface, run the following command:

noobaa backingstore create azure-blob <backingstore_name> --account-key=<AZURE ACCOUNT KEY> --account-name=<AZURE ACCOUNT NAME> --target-blob-container <blob container name>

backingstore_name

The name of the backingstore.

AZURE ACCOUNT KEY and AZURE ACCOUNT NAME

An AZURE account key and account name you created for this purpose.

blob container name

An existing Azure blob container name. This argument indicates to MCG about the bucket to use as a target bucket for its backingstore, and subsequently, data storage and administration.

Example output:

INFO[0001] ✅ Exists: NooBaa "noobaa"
INFO[0002] ✅ Created: BackingStore "azure-resource"
INFO[0002] ✅ Created: Secret "backing-store-secret-azure-resource"

Create an Azure-backed backingstore using a YAML file

Create a secret with the credentials:
```
apiVersion: v1
kind: Secret
metadata:
  name: <backingstore-secret-name>
type: Opaque
data:
  AccountName: <AZURE ACCOUNT NAME ENCODED IN BASE64>
  AccountKey: <AZURE ACCOUNT KEY ENCODED IN BASE64>
```
AZURE ACCOUNT NAME ENCODED IN BASE64 and AZURE ACCOUNT KEY ENCODED IN BASE64

Supply and encode your own Azure Account Name and Account Key using Base64, and use the results in place of these attributes respectively.

backingstore-secret-name

A unique name of backingstore secret.
Apply the following YAML for a specific backingstore:
```
apiVersion: noobaa.io/v1alpha1
kind: BackingStore
metadata:
  finalizers:
  - noobaa.io/finalizer
  labels:
    app: noobaa
  name: bs
  namespace: openshift-storage
spec:
  azureBlob:
    secret:
      name: <backingstore-secret-name>
      namespace: openshift-storage
    targetBlobContainer: <blob-container-name>
  type: azure-blob
```
blob-container-name

An existing Azure blob container name. This argument indicates to the MCG about the bucket to use as a target bucket for its backingstore, and subsequently, data storage and administration.

backingstore-secret-name

The name of the backingstore secret created in Creating a new backing store.