Actual backup starts two hours later than the start of the job

[Pavel_Novikov]

Hello,

Quite frequently I find in the BE log the following situation

Job started: Friday, March 17, 2006 at 5:05:12 AM
Job ended: Friday, March 17, 2006 at 7:42:50 AM

Backup started on 3/17/2006 at 7:30:08 AM.
Backup completed on 3/17/2006 at 7:38:03 AM.

Verify started on 3/17/2006 at 7:38:24 AM.
Verify completed on 3/17/2006 at 7:42:50 AM.

As you can see the actual backup and verify time is about 15 minutes, but it takes more than two hours to complete the job.

I use BackupExec 9.1 for Windows Servers running on Windows 2003 Server with IBM DAT72 TapeDrive. This particular case happened with SQL server agent backup job, but I have a feeling it's not relevant.

Any ideas?

[Guest_User]

>I use BackupExec 9.1 on
>Windows 2003 Server with
>IBM DAT72 TapeDrive.

One of my servers is similarly configured. Do you run any other backup jobs on this tape drive that exhibit the same behavior? Try a test backup and schedule it to run while you can watch the backup progress.

[Joshua_Small]

Do you have AOFO turned on?

On a busy server, this can take longer to start than is feasible.

[Shilpa_pawar_2]

Hi,

The job may start late if the device was not available at start time.

Also refer this technote: http://support.veritas.com/docs/192098

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.