Concurrent Jobs Queue - Backup Exec 12.5

Using Backup Exec 12.5 I have never had any problems with creating a Backup-to-disk folder, allowing 16 concurrent jobs, and then running all our various backup jobs to this folder at the same time. With over 1.6TB to back up over a period of 2 days, this makes for a very effective backup.

This weekend I have hit a problem whereby all the jobs I would expect to run simultaneously queue, with the exception of 1 job which will be allowed to run. They will run in a sequential order - wait for 1 job to complete then move on to the next one in the queue. The backup-to-disk folder still has '16 concurrent jobs' registered, but only 1 job will run to the folder at a time. Furthermore, if I create a new Backup-to-Disk folder, and run a test backup to this second folder while backups to the first folder are running/queued, the backup to this second folder also queues, so it doesn't appear to be a B2D-folder-specific issue.

500 points to anyone who can offer a resolution. Thanks.

LVL 58
Who is Participating?
tigermattConnect With a Mentor Author Commented:
After several hours on the telephone to Symantec Support, it turned out this was a faulty Backup-to-disk folder. Deleting and recreating the folder resolved the issue.

We narrowed down the cause to being a SAN drive which was switched off while Backup Exec was started (not running backups, but the services were activated). Backup Exec uses a LUN on the SAN for storage of backups. When the drive was switched off without Backup Exec being shut down, the end markers on the backup files were lost. As BE didn't know where the 'end' of the files was, it could only launch one job at a time; multiple jobs means BE needs to know what files to store in - and so needs to know the 'end' of files to do this.

Have you changed permission or passwords. it sound like  a access problem.
I would check the account using to backup to ensure there correct rights on each backup server /  workstation.

tigermattAuthor Commented:

It is not a credential problem because the backup jobs which queue are subsequently successful - after the previous job in the queue has completed.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.