As it clearly says Maximum I/O stream count has been reached for disk volume for Storage Unit: CSD-SYD-STU-PD
As you have set this to Limit I/O streams = 32 per volume and if there would be more jobs running then they will remain in queued state unless it finishes the current job which are running. And if the jobs remain in queued state and if backup window closes then jobs will fail with 196.
You have to check what kind of disk pool you are using and if that i/o stream can be increased, make sure you check the hardware vendor for it or it might thrash the disk.
Check you backup window, if it is too small you can increase it.
From the Netbackup 7.5 SLP best pratice manual:
http://www.symantec.com/docs/HOWTO73205
Use “Maximum I/O streams per volume” with Disk Pools
Disk storage units allow you to limit the number of concurrent write jobs that use the storage unit, however there are no limits on the number of read jobs (restores and duplications) that may be accessing the same disk pool at the same time and it is also possible to configure multiple storage units to access the same disk pool simultaneously. This can give rise to unexpected I/O contention on the disk pool. By setting the Maximum I/O streams per volume option on the Disk Pool, you can limit the total number of jobs that access the disk pool concurrently, regardless of the job type. While the disk pool is maxed out with backup jobs that are writing images to the device, no duplication jobs are allowed to start reading from the device. (The one exception to this rule is that restore jobs are allowed to read from the Disk Pool even if the maximum configured number of input and output streams is already being utilized.)
When you enable the Maximum I/O streams per volume option on the Disk Pool the default number of streams is 2. Although the optimal number of streams per volume will vary depending on the disk type, a general guide line to minimize contention would be to divide the maximum concurrent jobs count for all the storage units using the disk pool by the number of volumes in the disk pool.