One environment we manage is a Netbackup 7.5.0.6. Master server in Server 2008 R2 Ent 64bit.
We are getting intermittent status 24 or 41 backing up windows servers with several terrabytes of data. The servers have multiple drives. The policy allows multi streams. Backup selection is "All local Drives". The policy will create one stream per drive. However, the backup for the big drives would run for for hours and even days before it fails with status 24 or 41.
If we try to rerun, it will eventually fail again.
As a workaround, we broke up the policies into several. We created separate policies for the drives with the most data. For one server with over 7 TB of data, we created 5 policies just to backup the contents of R:\global.
On the first polciy, we created a Backup Selection like this:
R:\global\0*\
R:\global\1*\
.
.
.
R:\global\a*\
R:\global\b*\
On the second
R:\global\c*\
... and so forth.
This creates one stream for each R:\global subfolder. The jobs are smaller and we are getting better success.
But some of the drawbacks are.. if someone creates folder starting with a character I did not anticipate, it will not be backed up.
If lets say, there is no folder starting with a letter which is in the selection list, the stream for that job will fail with status 71.
CPU and Network utilization on both the clients and server appear to be ok when I checked. Each time we ask the Network guys to check, they are unable to find anything wrong.
Has anyone encountered similar issues and how you fixed it?