Solved

Concurrent Jobs Queue - Backup Exec 12.5

Posted on 2009-07-05
3
3,483 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Workplace bullying has increased with the use of email and social media. Retain evidence of this with email archiving to protect your employees.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

737 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