Backup job delayed for six hours

[Dennis_Martinez]

I have a intermittent problem with my Veritas backup job. I have a Windows 2003 SBS with SP1 with Veritas 9.1 Backup Exec installed. My job is set up to backup (Full Backup with reset archive bit) itself first and then the remote servers. All servers are on the same subnet and are physically in the same closet. So no WAN links. The problem that I am running into is that some times the job will delay for 6 hours. Since it does full backup on my servers when it delays it is backing them up during business hours causing one of my application server to slow down. I know I can change the selection order for the application server and I will not have this problem, but that is just a work around. The big problem is that it does this intermittently with different media. I have been monitoring this problem for the past three weeks. The job delays after it scans all sources that needs to backup. Here is the bengine*.log file from the server:

338 2/20/2006 21:00:03: DeviceManager: processing pending requests
338 2/20/2006 21:00:03: DeviceManager: query cache miss
338 2/20/2006 21:00:03: DeviceManager: query result = 0x00000000
338 2/20/2006 21:00:03: Available and held drives from the pool
338 2/20/2006 21:00:03: DELL 1 {4ca203e4-35c0-47ee-98c9-a0e3935474af}
338 2/20/2006 21:00:03: Drives not in use by the Engine
338 2/20/2006 21:00:03: DELL 1 {4ca203e4-35c0-47ee-98c9-a0e3935474af}
338 2/20/2006 21:00:03: Drives available (not in use and not held)
338 2/20/2006 21:00:03: DELL 1 {4ca203e4-35c0-47ee-98c9-a0e3935474af}
338 2/20/2006 21:00:03: Handing out drive:
338 2/20/2006 21:00:03: DELL 1 {4ca203e4-35c0-47ee-98c9-a0e3935474af}
338 2/20/2006 21:00:03: DeviceManager: going to sleep for 900000 msecs
5d0 2/20/2006 21:00:03: BackupJob: acquired device DELL 1
5d0 2/20/2006 21:00:03: BackupJob: trying to mount appending volume
5d0 2/20/2006 21:00:04: BackupJob: unable to mount appending volume, attempting scratch mount
338 2/20/2006 21:15:03: DeviceManager: timeout event fired
338 2/20/2006 21:15:03: DeviceManager: processing pending requests
338 2/20/2006 21:15:03: DeviceManager: going to sleep for 900000 msecs

<>

338 2/21/2006 2:45:03: DeviceManager: timeout event fired
338 2/21/2006 2:45:03: DeviceManager: processing pending requests
338 2/21/2006 2:45:03: DeviceManager: going to sleep for 900000 msecs
5d0 2/21/2006 3:00:00: Block size: 65536
5d0 2/21/2006 3:00:00: Buffer size: 65536
5d0 2/21/2006 3:00:00: Num buffers: 10
5d0 2/21/2006 3:00:00: High water: 0
5d0 2/21/2006 3:00:00: BackupJob: medium successfully mounted
5d0 2/21/2006 3:00:00: Media Label: LTO000006
5d0 2/21/2006 3:00:00: Media GUID: {66790667-FFB8-4A69-BFA7-12C7741540F6}
5d0 2/21/2006 3:00:00: Overwrite Protected Until: 2/26/2006 11:00:00 AM
5d0 2/21/2006 3:00:00: Appendable Until: 2/22/2006 11:00:00 AM
5d0 2/21/2006 3:00:00: TAPEALERT: Get TapeAlert Flags Return Code = 0X0
5d0 2/21/2006 3:00:00: TAPEALERT: TapeAlert Device Flag = 0X0
5d0 2/21/2006 3:00:00: TAPEALERT: TapeAlert Changer Flag = 0X0

I have turned on/off AOFO for my job and it will still delay. I have changed the order in the selection by selecting a remote server and then this server but still the job delays with the same error. I have searched around forums and one user in the Veritas forum had the same issue, but with Exchange Mailboxes on a remote server and his problem was the Remote Agent. This server is a Domain Controller, DNS, WINS, Print Server, Norton Antivirus Server and of course Veritas Backup Server. It is not creating any Dr Watson logs, and the Event logs are no help either. I have the installed Veritas SP4 and the latest Veritas drivers. I have the job setup to append/overwrite. I have BEUtility to autoanswer Yes to overwrite media. I will be using SGMon to see if I can see anything for tonights backup. I have searched the net and cannot find a solid solution. Is there a way to change the default wait time from 90000 milliseconds (15 Minutes) to 30 milliseconds? The whole thing is that it only happens once in a while not all the time! I am totally confused on what can be the issue.

Thanks
P

[Ajit_Kulkarni]

Hello,


You can refer to the following mentioned technotes which will help you in resolving the slow backup problem:


- Reasons why the data throughput rate can be slower than the theoretical maximum when backing up to tape media
http://support.veritas.com/docs/231488


- How to correct slow backup performance, slow virus or pre-job scans, and agent initialization problems on fragmented Windows NT, Windows 2000, and Windows 2003 server partitions
http://support.veritas.com/docs/237444

- What Backup Exec settings can be modified to reduce the amount of time it takes for a backup to run?
http://support.veritas.com/docs/249090


Hope this helps you.


Regards



NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Dennis_Martinez]

I have looked a the technotes and the drive is configured correctly, my volumes have been defragmented. Those were of no help. Is there a way to configure Backup exec to change the default sleep time for the device from 90000 milliseconds to 30 milliseconds? If this is not possible then my only option at this time is to un-install and re-install. Please advise!

[Dennis_Martinez]

I have resorted to the last option "Reinstall Veritas". So far its been two days and backups are running correctly. I am crossing my fingers on this. I will post next week for a good status. I just hope no one else has the same problem as I did. Because I could not find a resolution!

P

[Amruta_Bhide]

Hello Dennis,
We apologise on the late Response.
Could you Update us on the latest status of the Issue?

******************************************************************
*****************************************************************

Note : If we do not receive your reply within two business days, this post would be marked ?assumed answered? and would be moved to ?answered questions? pool.


Thanks.