Is anyone else using Azure Blob discovery in Commvault? Specifically under Protect → Object Storage → Object Storage Groups?
I’ve defined several Object Storage Groups to automatically detect new Azure Storage accounts. Discovery itself works—new accounts are picked up as expected. However, I’m running into issues with excluding certain accounts from backup.
🚫 Exclusion Logic Challenges
In one subscription, we have Storage accounts that should not be backed up. We’ve applied a tag to those accounts and created a rule in the Object Storage Group to exclude them. But it doesn’t work.
From what I can tell, the rule behaves like an inclusion filter, not a traditional exclusion filter. That means I have to define what should be backed up, rather than what shouldn’t. This is problematic:
- There’s no support for wildcards.
- It’s difficult to write a rule that includes “everything except these few tagged accounts.”
⏰ Discovery Timing Flaw
Another issue: the Azure Blob discovery job runs daily at 10:00 AM. That’s a bad time operationally. If someone creates a new Storage account at 2:00 PM, and my backup runs later that evening, that account won’t be backed up until the next day. So I lose a day of protection.
Ideally, I’d like to change the discovery schedule to 6:00 PM, after most users have finished provisioning resources.
🔍 Hidden System Policy
Here’s the kicker: the job that runs at 10:00 AM is tied to a “System Created cloud resource discovery schedule policy.” But this policy is not visible or editable to admins. It’s masked from the UI, and support hasn’t been helpful—they’re answering unrelated questions and ignoring the actual issue in the ticket.
All I want to know is:
How do I modify the “System Created cloud resource discovery schedule policy”?
Sorry for the rant—just a long-time customer (20+ years) missing the days of solid support and intuitive design. If anyone has figured this out or has a workaround, I’d love to hear it.
