?
Solved

Backup Exec - Backup timing out with 0 Bytes written

Posted on 2005-05-10
8
Medium Priority
?
1,761 Views
Last Modified: 2013-12-01
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.
0
Comment
Question by:mellingham
  • 4
  • 2
  • 2
8 Comments
 
LVL 2

Expert Comment

by:rdesigaud
ID: 13966531
First, you could check the job's journal, to see what happened...

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 ?
0
 

Author Comment

by:mellingham
ID: 13966696
Of course.

The error in the Job Log is:

Error - Mount failed.
User canceled a Physical Volume Library operation.

Thanks.
0
 
LVL 2

Expert Comment

by:rdesigaud
ID: 13966763
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...
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 

Author Comment

by:mellingham
ID: 13967043
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.
0
 
LVL 2

Accepted Solution

by:
msaraceno earned 300 total points
ID: 13968800
I had a similiar problem with my backup exec and I found out it was due to the backup size. Im using a dd4 tape drive wich is 20gb/40gb and when I was hitting around 27gb the job was failing with that error. What I did was remove some mailboxes out of the backup and retest and it worked fine. I found out from veritas also that the backup compression can be the problem sometimes as it cant compress things down that much and you dont get the true 40gb compression. If your tapes are 40/80 and you say your backups in the past were working and completing at 50gb you have to have compression turned on. Try doing this change the option from the job to canceling after 11 hours and let it run. Check the backup the next day and see if the tape is spit out if it is insert another tape and see if the job finishes off if it does then you know what your problem is that the tapes cant compress the data enough. Then you have 2 options reduce the amount of data being backed up or you have to switch tapes or i guess there is also a third option you could use a tape library as well.
0
 

Author Comment

by:mellingham
ID: 13968905
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!
0
 
LVL 2

Expert Comment

by:msaraceno
ID: 13995738
status update ?
0
 

Author Comment

by:mellingham
ID: 14016737
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.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

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

When we purchase storage, we typically are advertised storage of 500GB, 1TB, 2TB and so on. However, when you actually install it into your computer, your 500GB HDD will actually show up as 465GB. Why? It has to do with the way people and computers…
Compliance and data security require steps be taken to prevent unauthorized users from copying data.  Here's one method to prevent data theft via USB drives (and writable optical media).
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
Learn how to create flexible layouts using relative units in CSS.  New relative units added in CSS3 include vw(viewports width), vh(viewports height), vmin(minimum of viewports height and width), and vmax (maximum of viewports height and width).
Suggested Courses

850 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