More Details of OperationalDB Snapshots with HBase

[#1]

Hello everyone,

during the snapshot for an operational database, we had issues regarding the storage address/location. We were only able to place the snapshot in the same Azure storage container as the HBase service. Otherwise, we got errors for insufficient rights. 
Are there any official docs helping in this topic?
Can Hadoop be modified to allow the use of a different container for storing these snapshots?
or how can we give HBase the right to access different storage locations or different storage container?

But then, what backups are stored in the default location? Only the cluster backups?


Regards


(Our Post leading to these questions: https://community.cloudera.com/t5/Support-Questions/HBase-Snapshotting-Failed-because-of-Failure-to-...)

[#2]

1. Cloudera Operational Database backup guide:
https://docs.cloudera.com/operational-database/cloud/managing-database/topics/cod-backing-up-table.h...
https://docs.cloudera.com/cdp-public-cloud/cloud/requirements-azure/topics/mc-az-minimal-setup-for-c...

HBase snapshot export also covered in Runtime HBase backup docs.

2. Default backup location: Mainly stores cluster-level backups (Data Lake, FreeIPA, logs/telemetry). Not HBase table data.
3. Different container for manual backups: Use --snapshot-location abfss://othercontainer@account.dfs.core.windows.net/path in snapshot/export command. No direct Hadoop config edit needed in CDP Public Cloud.
4. Give HBase rights

Assign Storage Blob Delegator role to HBase Managed Identity (at Storage Account level).
Grant Storage Blob Data Owner/Contributor on target container.
Set POSIX ACLs (Execute + Read/Write) on root and target path via Storage Explorer.
Verify IDBroker mapping for HBase user.

Test access with hdfs dfs -ls on target path.
Enable "Allow trusted Microsoft services" if option available. @MintberryCrunch