15 minutes queued?

[Rick_Kutschera]

Hi everyone!

I have a strange phenomenon since upgrading to BE 12: Whenever I start a backup job for a SQL Server (cann't actually say that this is only for SQL backup, but it's most annoying for me there...) the job get's a "Queued" state and remains in that state for 15 minutes every time. After that the backup (Backup to Disk in my case, so definitily no problem with the tape drive...) runs fine and writes the data in a very short time (3 minutes for the 200 MB differential log backup) 

Anyone around any ideas about this? How can I get to the bottom of that? How can I fix that?

Rick

[Steve_W_]

Have you tried creating a test job backing up the same data to see if the same issue occurs?

[Rick_Kutschera]

I just created a backup job that is set to just backup one file on the Media Server to a disk on the same server... It also stays queued 15 minutes (and then runs the backup in 5 seconds...)

[Rick_Kutschera]

Something else: I just tried enabling PreScan for the backup jobs. This leads to the job no longer being queued for 15 minutes but backup scanning for 15 minutes...

[Anup]

Bhttp://support.veritas.com/docs/191793

Also create another test B2D and see if it behaves in same manner.

Run inventory on B2D and see how long it takes.

[Rick_Kutschera]

Sorry, it seems that my last posting was not very well formulated... I know article 191793... I only enabled PreScan for testing to see if it gets me more details...

Also I already switched to B2D testjobs before writing the last entry, just to be sure that it's not an issue with the tape system.

Inventory runs quickly, only backups have that behaviour.

Rick

[Anup]

What is the device on which the B2D is created?

Configuring advanced options for a backup-to-disk folder 

http://support.veritas.com/docs/299362 

Uncheck Auto detect settings on B2D properties window and then run the backup job. 

[Rick_Kutschera]

Unfortunately no change whatsoever... I tried some other devices too, just to make sure (three different tape drives, a SAS HDD, a network share, a USB 2.0 HDD and an IEEE1394 HDD) all behave exactly the same way with the same delays.

I am under the impression that the systems get's stuck even before it starts doing anything, like if it would be waiting for a response or for a timer to trigger...

[Anup]

Is AOFO selected in backup job?

[Rick_Kutschera]

Yes. But with SQL backups this shouldn't matter, should it?

[Anup]

AOFO is not recommened to use with database back ups like SQL or exchange.

AOFO creates snapshot..which might take time to create snapshots....but it explicitely tells u a bakcup job status as snahpshot-processing....I dont think removing AOFO will resolve the problem...but dont take snapshot backups of SQL as they can not be redirected

Using snapshot technology with the SQL Agent

http://support.veritas.com/docs/300169