Hi !
I’ve noticed a strange behaviour of a daily DDB incremental verification job, normally set to 30 readers, but getting much higher than this since a few days..
See below
![](https://uploads-eu-west-1.insided.com/commvault-eu/attachment/4ce32334-b48c-4ce3-9005-dcfa7d67b1ee.png)
How can this be possible ?
I thought that the limit was.. a limit
So, what has changed ? Well, not sure it is related, but since sept9, I upgraded from v11FR21HP20 to v11FR21HP53, and no other change.
The Gridstor of 4 hosting this DDB also host another DDB, whose verification job runs without getting (or printing only) the maximum 30 readers limits.
That’s a bit annoying because the first job goes pending for a while with :
Error Code: o19:1105]
Description: No Resources Available. Please check the Streams tab for details.
Of course no ressources are available, as it’s trying to allocated more than 30..
A few details about this job and blocks to process :
![](https://uploads-eu-west-1.insided.com/commvault-eu/attachment/856e9298-8184-4d41-9a81-c744a8af60ea.png)
Should I log a case or, have you already been used to such ?