Solved

Concurrent Jobs Queue - Backup Exec 12.5

Posted on 2009-07-05
3
3,437 Views
Last Modified: 2013-12-01
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.

0
Comment
Question by:tigermatt
  • 2
3 Comments
 
LVL 23

Expert Comment

by:ComputerTechie
ID: 24780638
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.

CT
0
 
LVL 58

Author Comment

by:tigermatt
ID: 24780744

It is not a credential problem because the backup jobs which queue are subsequently successful - after the previous job in the queue has completed.
0
 
LVL 58

Accepted Solution

by:
tigermatt earned 0 total points
ID: 24801602
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.

-Matt
0

Featured Post

Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

Join & Write a Comment

Suggested Solutions

This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now