Dedicated BE server dual processor xeons quad core with 20 gigs of ram. LTO 5 Super Loader 3 and md1000 raid with 3TB storage. Server 2008 Standard. My backup system has been rock stable for about 2 year now without issue. I have 20 jobs, 12 are tape jobs and 8 are to b2d in case of the need for quick restore. I upgraded my system to 15 July 3rd and came back on monday to The raid full and the backupexec manager service shutdown. For some reason the backup job on the media server decided to backup the raid (to itself) even though I have that drive specifically exempt. I chalked this up to me not going through each job to verify the job settings though after doing this all settings were as they were supposed to be.
During the week the jobs locked up alltogether. 2 jobs, 1 backing up my fp server to tape and the other b2d of one of my utility servers had basically stalled after backing up 50 and 30 gigs. Job log lists backing up, time is still counting up but no active file or directory is listed in the job log and both the raid and the tape drive are idle. I installed the new update on thursday and pushed out the new agents to see if this was perhaps an issue that was fixed but had the same problem thursday night. Friday I decided to try splitting up the jobs. Put all the b2d jobs on hold and Everything ran as expected. I was actually surprised that the new update appeared to shave about 6 hours off my tape jobs. Removed hold one the b2d jobs and they ran as expected.
This leads me to believe that the issue has to do with running 2 jobs at the same time which 2014 did not have an issue with.