mellingham
asked on
Backup Exec - Backup timing out with 0 Bytes written
Hi there.
I am running Veritas BE 9.1 Rev 4691 on Windows 2000 Server. The backup is for files on the local server only, including MS Exchange DB's. The Device is an HP DLT VS80 with latest drivers and firmware on a new SCSI controller. Compression is turned off for the device as there are a large number of image files in the backup set.
I have set the backup to cancel after 11 hours so that the next day will run as scheduled without having to wait for the previous job to finish. WHEN the job does complete it takes about 10 hours to write approx 50GB. When the job times out BE shows the byte count as zero.
Any ideas what to check?
Thanks.
I am running Veritas BE 9.1 Rev 4691 on Windows 2000 Server. The backup is for files on the local server only, including MS Exchange DB's. The Device is an HP DLT VS80 with latest drivers and firmware on a new SCSI controller. Compression is turned off for the device as there are a large number of image files in the backup set.
I have set the backup to cancel after 11 hours so that the next day will run as scheduled without having to wait for the previous job to finish. WHEN the job does complete it takes about 10 hours to write approx 50GB. When the job times out BE shows the byte count as zero.
Any ideas what to check?
Thanks.
ASKER
Of course.
The error in the Job Log is:
Error - Mount failed.
User canceled a Physical Volume Library operation.
Thanks.
The error in the Job Log is:
Error - Mount failed.
User canceled a Physical Volume Library operation.
Thanks.
have a look there : http://seer.support.veritas.com/docs/246967.htm
seems the tape cannot be read...
I had trouble sometimes with the tape pool, tape reader got deconnected from time to time...
seems the tape cannot be read...
I had trouble sometimes with the tape pool, tape reader got deconnected from time to time...
ASKER
I was just looking at that doc too! :)
There is nothing in the logs about the device failing though. Working properly in Windows device manager too. Tapes aren't filling up as they are 40/80 GB.
Very odd.
There is nothing in the logs about the device failing though. Working properly in Windows device manager too. Tapes aren't filling up as they are 40/80 GB.
Very odd.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK that sounds feasible...I didn't think it was space though as our other backup set is hitting 60+ GB with the same config within the time period. The only difference is the number of image files in the failing backup - these don't compress very well hence my disabling of compression on the tape drive.
I'll look at the results tomorrow and post again with the results. Thanks so much for your suggestions!
I'll look at the results tomorrow and post again with the results. Thanks so much for your suggestions!
status update ?
ASKER
Hi. Sorry I have been ill. I have checked the backup logs today and the backup appears to have completed okay last night but the previous 2 nights failed. I still don't think it is a space issue as another server with similar config and backup set is running to 65GB on the same media. Also, this wouldn't explain the mount failure.
The backup byte count is also within 1-2 GB of the size when it was failing so it seems like a fairly random occurrence. Any other ideas. I think the mount failure is the key - sounds like a device failure. I am going to try to update the mainboard and SCSI BIOS this week to see if it is hardware related. The Drive is running on a brand new controller on a Proliant ML370 board (G1) so it could be compatibility.
Will keep you posted.
The backup byte count is also within 1-2 GB of the size when it was failing so it seems like a fairly random occurrence. Any other ideas. I think the mount failure is the key - sounds like a device failure. I am going to try to update the mainboard and SCSI BIOS this week to see if it is hardware related. The Drive is running on a brand new controller on a Proliant ML370 board (G1) so it could be compatibility.
Will keep you posted.
Then make sure you didn't delete any Exchange user recently, as it would block BE from completing the task.
can you copy the job's journal here ?