Unless you have other parallel jobs using the same Storage and Storage policies at the time the verification job is executed, you can let the default settings to use maximum.
There are (maybe too much but) many locations where you can define streams limits, like storage/mount paths, Storage policies, Storage Policy copies..
I recommend to schedule an incremental verification of both jobs on disk and DDB, because that’s the way to make sure your new blocks are usable for your copies, restores, or next backups with same signatures..
You should always schedule such data verification as soon as you create a DDB, because the more you wait, the more data would have to be verified, which can take very long, depending on so many things like storage performance, volumes, you MA’s resources..
Unless you have other parallel jobs using the same Storage and Storage policies at the time the verification job is executed, you can let the default settings to use maximum.
There are (maybe too much but) many locations where you can define streams limits, like storage/mount paths, Storage policies, Storage Policy copies..
I recommend to schedule an incremental verification of both jobs on disk and DDB, because that’s the way to make sure your new blocks are usable for your copies, restores, or next backups with same signatures..
You should always schedule such data verification as soon as you create a DDB, because the more you wait, the more data would have to be verified, which can take very long, depending on so many things like storage performance, volumes, you MA’s resources..
@Laurent Thank you very much for the explanation!
@drPhil Thank you too, glad to help 
