About MintberryCrunch

MintberryCrunch · ‎02-09-2026

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-aquire-SAS/td-p/413360)

MintberryCrunch · ‎01-30-2026

This Error refers to Hadoop ACLs The Azure ACL and RBAC was correctly assigned. The snapshot location must reside within the same directory as the HBase directory. The HBase user seems to have only access to this directory. For example, we used something like the following path: > abfss://storagefs@mystorageaccount.dfs.core.windows.net/cod-ouiftSmthLikeThis/hbase/.hbase-snapshot This confusion was caused by the default backup location set to the logs container during the environment creation. Follow-up questions: 1. Where is an official documentation or guidelines location addressing this topic? 2. What backups are stored in the default location? Only the cluster backups? 3. How can the Hadoop configuration be modified to allow the use of a different container for storing manual backups? 4. How can we give HBase the rights to access different storage locations?

MintberryCrunch · ‎01-26-2026

Hello 9een, thank you for your reply! 1. How do I find out which role is used by the HBase Service? I used this guide to assign the roles ( https://docs.cloudera.com/cdp-public-cloud/cloud/requirements-azure/topics/mc-az-minimal-setup-for-… ) 2. I assigned all identities all permissions to get something to work, because I was not sure which Managed Identity is responsible. 3. In my Azure Storage Account there is no specific "Allow trusted Microsoft services to access this storage Account" setting. But "Microsoft networking Routing" Routing preference is set. "Public network Access" is "Enabled form all networks". 4. All Sticky Bits are disabled on all path. Regards.

MintberryCrunch · ‎01-21-2026

Hello, <in a Public Cloud Environment in the Operational Database with Azure: Snapshots were failing. The HBase-Service Command Tab showes that it occurs while copying a snapshot to another directory because it could not acquire a SAS token. (*) Usually those errors are related to missing rights on Managed Identities. - But we double-checked all Azure Managed Identity IAMs and RBACs. Sometimes the SAS-Token Failure is related to Kerberos which is disabled./> What could have gone wrong? (*): Client.RangerRESTClient: ===>> RangerRESTClient.init() : Since mKeyStoreType is NULL, setting System default. [mKeyStoreType=jks] Exception in thread "main" Failed to acquire a SAS token for get-acl on / due to org.apache.hadoop.security.AccessControlException: Permission denied. at org.apache.hadoop.fs.azurebfs.services.AbfsClient.appendSASTokenToQuery(AbfsClient.java:1233)

Online	Offline
Last Visited	‎03-05-2026 10:35 PM

Member Since	‎01-20-2026 04:21 AM
Last Visited	‎03-05-2026 10:35 PM
Posts	4

Cloudera Community

Re: HBase Snapshotting Failed because of Failure t...

More Details of OperationalDB Snapshots with HBase

Re: HBase Snapshotting Failed because of Failure t...

Re: HBase Snapshotting Failed because of Failure t...

HBase Snapshotting Failed because of Failure to aq...