DDB Verification Concurrent Operations

Hi All,

I currently have a few DDB Stores to run DDB Verification for the first time (Full) and they are quite large, so running multiple jobs would be quite helpful. So considering the statements below from the docs, I started 1 DDB Verf and specified 30 streams. Attempted to initiate a second one and it automatically goes into a queued state. My first job is only using 30, should I be able to run a second one in this scenario? What am I missing?

“You can perform only up to 50 concurrent data verification jobs. Any additional jobs that you perform get queued.”

“ By default, deduplicated data verification job uses 20 streams during Validate Data phase and 50 streams during Verify Data phase.”

Thanks

Page 1 / 1

Hi dude,

Running a concurrent DDB Verification operation is not supported for the same DDB, hence the new jobs being queued instead. Resources permitting, you could instead increase the number of stream for the DDB Verification for both phases.

Thanks @Jon Vengust - documentation is incorrect? or should be clarified perhaps?

Hi dude,

I agree it should be clarified in that it refers to concurrent DDB Verification operations within the Commcell entirely vs. the same, single DDB. It is definitely worth sending feedback for.

Reply

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded