VERITAS: Stops In the middle of backup 1

[pmidwest]

VERITAS: Backup Exec 8.6 stops in the middle of backups.
The back up will run and back up everything until it gets to the last drive and it spits out the tape. When you put the tape back in it errors out and the job fails

Here is a look at the log file


Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
======================================================================
----------------------------------------------------------------------
OFO: Started for device: "C:"


Media Name: "Media created 1/6/03 09:00:10 PM"
Backup of "C: "
Backup set #4 on storage media #1
Backup set description: "Mon-Wed"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/6/03 at 9:38:54 PM.

Backup completed on 1/6/03 at 9:55:20 PM.
Backed up 23507 files in 1504 directories.
Processed 3,252,580,947 bytes in 16 minutes and 26 seconds.
Throughput rate: 188.8 MB/min
----------------------------------------------------------------------
OFO: Started for device: "F:"


Media Name: "Media created 1/6/03 09:00:10 PM"
Backup of "F: "
Backup set #5 on storage media #1
Backup set description: "Mon-Wed"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/6/03 at 9:55:54 PM.

Backup completed on 1/6/03 at 10:28:24 PM.
Backed up 46 files in 11 directories.
Processed 5,556,229,546 bytes in 32 minutes and 30 seconds.
Throughput rate: 163.0 MB/min
----------------------------------------------------------------------
OFO: Started for device: "P:"


Media Name: "Media created 1/6/03 09:00:10 PM"
Backup of "P: Company"
Backup set #6 on storage media #1
Backup set description: "Mon-Wed"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/6/03 at 10:28:49 PM.

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 2
Media Slot: 0
Media Cartridge Label: DLT000003
Targeted Media Set Name: Media Set 1
The media provided to continue the backup already contains data
from one or more sets created during this operation.
The operation can not be continued


Backup completed on 1/7/03 at 7:58:37 AM.
Backed up 314865 files in 13383 directories.
Processed 37,278,456,537 bytes in 4 hours, 19 minutes, and 27 seconds.
Throughput rate: 137.0 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: Tuesday, January 07, 2003 at 7:59:19 AM
Job completion status: Failed
======================================================================


I looked up the error and it said that it means the disk is full and to check that the Overwrite protection period and Append period were set to the proper amount of time I did this and still got the error last night. Any clues as to what I can do to fix this problem?
A co-worker suggested erasing the tapes and starting fresh but I can’t seem to find away to do this in Veritas.

Any help would be greatly appreciated

Thanks in advance

Paul

 

[SQLBill]

Paul,

First, here is the pertinent information from your error log:

The media provided to continue the backup already contains data from one or more sets created during this operation.

This means the tape was already used for this backup. Question for you: are you using a tape library (multiple tapes) or a stand-alone machine (one tape)?

It looks to me like you are using a stand-alone tape drive. If so, Veritas doesn't/can't wait for you to put in a new tape...it needs to finish the job and needs the tape right away. If this is your situation then you need to break the job into two or more backup jobs. Run one job, change the tape and run the second job.

If you are using a tape library with multiple tapes, this shouldn't be happening if your media set has the proper overwrite protection settings.

Lastly, to erase a tape, go to the Media tab, highlight the tape, right-click and select Erase > Quick.

-SQLBill

 

[pmidwest]

we are useing multiple tapes. we have a mon/wed a tue/thu and 4 friday tapes. the error is recent like the tapes have just gotten full... all the tapes are 80GB I beleve and we are only backing up around 52GB. I checked the Append period and it was set to Infinite so I set it to 0 hours saying as we over right the tapes every other day. this still didnt work. Do you think that eraseing the tapes and keeping the same jobs would fix this problem?

Thanks again

Paul

 

[SQLBill]

I think I found your problem:

You say "...we have a mon/wed a tue/thu and 4 friday tapes"

The error log says: (I bolded the important information)

Backup set description: "Mon-Wed"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/6/03 at 10:28:49 PM.

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 2
Media Slot: 0
Media Cartridge Label: DLT000003
Targeted Media Set Name: Media Set 1
The media provided to continue the backup already contains data
from one or more sets created during this operation.
The operation can not be continued

Now, based on your comments about the media sets you have, it looks like you have one tape assigned to mon/wed, one tape assigned to tues/thurs and four tapes for friday. The failed job was your mon/wed job and it needed two tapes. However, the media set it is using only has one tape. So it tries to reuse tape, but it can't because it has data from this backup job already...so it fails for lack of a tape.

Solution, assign another tape to the mon/wed media set.

-SQLBill

 

[SQLBill]

By the way....let's say you have a 50GB tape and your backup is only 20 GB. BE will do two backups (total of 40GB) on the tape, then append 10GB from the third backup and fail because it can't add the last 10GB to the tape. And it can't overwrite either. A backup has to all be on one tape or span to a second. It can't be on the end and the beginning of the same tape.

-SQLBill

 

[pmidwest]

But with an Overwrite protection period of 0 and a Append period of 0 shouldn’t the tape overwrite its self every time its inserted?
If I do a successful backup on Monday then insert the tape on Wednesday shouldn’t Monday be erased and Wednesday become a fresh copy of the servers files?

 

[kingtyrone]

Paul,

My situation was the same as yours, only I have a tape per day Mon - Thu doing differential backups and a three-tape Friday Full.

Remember that the compression isn't always 2:1
Therefore a 40:80 DLT may become full at 50GB if the compression is 1.3:1 (I found that out the hard way!)
Thus, you may need two tapes for one backup job.

I would try making your mon/wed and tue/thu tapes into Daily1 and Daily2,
thereby reusing both tapes on a daily basis.
You still have a full Friday backup.

Then set your overwrite protection to say 8 hours.
That way the same tape is protected from being pulled back in until the next day.

Hope this helps on you quest for secure backups.

Cheers,
Tyrone

 

[SQLBill]

Your question:
If I do a successful backup on Monday then insert the tape on Wednesday shouldn’t Monday be erased and Wednesday become a fresh copy of the servers files?
My answer:
No. You are probably allowing appends. That means it WON'T overwrite the data as long as there is room to append.

If you want the information overwritten everytime you insert the tape, you need to change the properties of the media set to OVERWRITE and don't allow appends. Go to TOOLS > OPTIONS > Media Overwrite tab. Change Media Overwrite Protection Level to NONE.

This will only solve your problem if your backup fits on one tape. If it is requiring two tapes for one backup, this won't solve the problem.

-SQLBill

 

[pmidwest]

Ok,

Last nights backup stopped at the same place...

This morning I went to Tools>Options>Media Overwrite>

Media overwrite protection level = None
Media overwrite options = Overwrite scratch media before overwriting recyclable media contained in the targeted media set

Tools>Options>Backup

Backup Method For Files: NORMAL - Backup Files - Reset Archive Bit
Overwrite Options: Append to media, overwrite if no appendable media is available. (I changed this option to Overwrite Media)
Compression Type: Hardware (if available, otherwise software)

We are only backing up around 50 some GB total so I don’t know why it would be a compression problem unless the tapes are just bad... They are a little over a year old and we have had the same backup schedule since day 1

Also I tried to erase the tape but when I go to the erase option both options are grayed out.

I will let the tape run tonight with the changed settings and see if it helps... but if anyone can think of anything else please let me know

Thanks a lot

Paul

 

[pmidwest]

Since my last post I have erased the disks and have reinstalled the drivers and that seems to have done something because I’m not getting the same errors… although my jobs are still failing. In the mornings when I come in the tape is ejected like always but the job still says running 72% (its never had a % next to it) when I put the tape back in the drive I get an alert on the alerts screen saying

Media Request:
Please remove the media from the drive, and respond ok

When I hit the eject button and the tape comes out I click “respond ok” and the alert goes away but the job stops and says failed. The error log seems to only be reporting 2 corrupt files. (That could be causing the job to fail… right?) But I don’t think that all the files are getting copied to the tape…

After right clicking on the failed job and clicking properties, the “Complete Job” tab says total bytes: 25,951,236,365
When right clicking on all three drives and clicking properties then adding up total bytes (in use) I come up with 58,815,947,264.

Leading me to believe the backup was unsuccessful. Also in the error log under each drive it says that 0 files were different. I don’t know if this is because I am overwriting the media and it doesn’t have anything to compare with or if its just not writing the files to the tape.

Here is the job log:

======================================================================
Job server: BUDWEISER
Job name: Friday1
Job started: Friday, January 17, 2003 at 9:00:03 PM
Job type: Backup
Log file: BEX01.txt
======================================================================

Drive and media information from media mount:
Changer Name:
Drive Name: DELL 2
Media Slot: 0
Media Cartridge Label: DLT000006
Targeted Media Set Name: Media Set 1

======================================================================
Job Operation - Backup
Media operation - overwrite.
Software compression enabled.
======================================================================

Media Name: "Media created 1/17/03 09:00:04 PM"
Backup of "\\BUDWEISER\Microsoft Exchange Directory "
Backup set #1 on storage media #1
Backup set description: "Friday1"
Backup Type: FULL - Database & Logs (flush committed logs)
Backup started on 1/17/03 at 9:00:19 PM.

Backup completed on 1/17/03 at 9:00:27 PM.
Backed up 1 Exchange Server store(s)
Processed 8,405,262 bytes in 8 seconds.
Throughput rate: 60.1 MB/min
Software compression ratio: 11.6:1
----------------------------------------------------------------------

Media Name: "Media created 1/17/03 09:00:04 PM"
Backup of "\\BUDWEISER\Microsoft Exchange Information Store "
Backup set #2 on storage media #1
Backup set description: "Friday1"
Backup Type: FULL - Database & Logs (flush committed logs)
Backup started on 1/17/03 at 9:00:28 PM.
Access denied to database .
^ ^ ^ ^ ^
WARNING: "Information Store" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^

Backup completed on 1/17/03 at 9:00:36 PM.
Backed up 1 Exchange Server store(s)
1 corrupt file was backed up
Processed 0 bytes in 8 seconds.
Throughput rate: 0.0 MB/min
----------------------------------------------------------------------

Media Name: "Media created 1/17/03 09:00:04 PM"
Backup of "\\BUDWEISER\Microsoft Exchange Mailboxes "
Backup set #3 on storage media #1
Backup set description: "Friday1"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/17/03 at 9:00:37 PM.

Backup completed on 1/17/03 at 9:26:26 PM.
Backed up 29288 mail message(s) in 573 folder(s) in 23 mailbox(es)
Processed 3,053,312,882 bytes in 25 minutes and 49 seconds.
Throughput rate: 112.8 MB/min
Software compression ratio: 1.2:1
----------------------------------------------------------------------
OFO: Started for device: "C:"


Media Name: "Media created 1/17/03 09:00:04 PM"
Backup of "C: "
Backup set #4 on storage media #1
Backup set description: "Friday1"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/17/03 at 9:27:08 PM.
The item \SmallBusiness\CLIENTS\ca\inoculan\Win95\VIRTEST.AVB in use - skipped.
The item \SmallBusiness\CLIENTS\ca\inoculan\winnt\i386\135060BE.AVB in use - skipped.
The item \SmallBusiness\CLIENTS\ca\inoculan\winnt\i386\VIRTEST.AVB in use - skipped.

Backup completed on 1/17/03 at 9:46:08 PM.
Backed up 24057 files in 1513 directories.
3 items were skipped.
Processed 3,813,989,534 bytes in 19 minutes and 0 seconds.
Throughput rate: 191.4 MB/min
Software compression ratio: 2.1:1
----------------------------------------------------------------------
OFO: Started for device: "F:"


Media Name: "Media created 1/17/03 09:00:04 PM"
Backup of "F: "
Backup set #5 on storage media #1
Backup set description: "Friday1"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/17/03 at 9:46:37 PM.

Backup completed on 1/17/03 at 10:00:57 PM.
Backed up 26 files in 7 directories.
Processed 2,841,829,977 bytes in 14 minutes and 20 seconds.
Throughput rate: 189.1 MB/min
Software compression ratio: 1.2:1
----------------------------------------------------------------------
OFO: Started for device: "P:"


Media Name: "Media created 1/17/03 09:00:04 PM"
Backup of "P: Company"
Backup set #6 on storage media #1
Backup set description: "Friday1"
Backup Type: NORMAL - Back Up Files - Reset Archive Bit
Backup started on 1/17/03 at 10:01:26 PM.
Unknown OFO error: 0xc000007f.
OFO: Error during backup. Set has been aborted.
WARNING: "\NETWORK\LinkOne\Projects\books\Rayairco\XPIPC\BOOK.SFB" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^

Backup completed on 1/17/03 at 11:35:31 PM.
Backed up 143814 files in 8119 directories.
1 corrupt file was backed up
Processed 16,233,698,710 bytes in 1 hour, 34 minutes, and 5 seconds.
Throughput rate: 164.6 MB/min
Software compression ratio: 1.3:1
----------------------------------------------------------------------

======================================================================
Job Operation - Verify
======================================================================

Verify of "\\BUDWEISER\Microsoft Exchange Directory "
Backup set #1 on storage media #1
Backup set description: "Friday1"
Verify started on 1/17/03 at 11:36:47 PM.

Verify completed on 1/17/03 at 11:36:47 PM.
Verified 1 Exchange Server store(s)
Processed 724,521 bytes in 1 second.
Throughput rate: 41.5 MB/min
----------------------------------------------------------------------

Verify of "\\BUDWEISER\Microsoft Exchange Information Store "
Backup set #2 on storage media #1
Backup set description: "Friday1"
Verify started on 1/17/03 at 11:36:47 PM.

Verify completed on 1/17/03 at 11:36:47 PM.
Verified 1 Exchange Server store(s)
Processed 0 bytes in 1 second.
Throughput rate: 0.0 MB/min
----------------------------------------------------------------------

Verify of "\\BUDWEISER\Microsoft Exchange Mailboxes "
Backup set #3 on storage media #1
Backup set description: "Friday1"
Verify started on 1/17/03 at 11:36:47 PM.

Verify completed on 1/17/03 at 11:51:45 PM.
Verified 29288 mail message(s) in 573 folder(s) in 23 mailbox(es)
0 files were different.
Processed 2,510,303,553 bytes in 14 minutes and 58 seconds.
Throughput rate: 160.0 MB/min
----------------------------------------------------------------------

Verify of "C: "
Backup set #4 on storage media #1
Backup set description: "Friday1"
Verify started on 1/17/03 at 11:51:45 PM.

Verify completed on 1/18/03 at 12:02:12 AM.
Verified 24057 files in 1513 directories.
0 files were different.
Processed 1,742,889,167 bytes in 10 minutes and 27 seconds.
Throughput rate: 159.1 MB/min
----------------------------------------------------------------------

Verify of "F: "
Backup set #5 on storage media #1
Backup set description: "Friday1"
Verify started on 1/18/03 at 12:02:12 AM.

Verify completed on 1/18/03 at 12:16:12 AM.
Verified 26 files in 7 directories.
0 files were different.
Processed 2,359,691,777 bytes in 14 minutes and 0 seconds.
Throughput rate: 160.7 MB/min
----------------------------------------------------------------------

Verify of "P: Company"
Backup set #6 on storage media #1
Backup set description: "Friday1"
Verify started on 1/18/03 at 12:16:13 AM.

Verify completed on 1/18/03 at 1:30:31 AM.
Verified 143815 files in 8119 directories.
0 files were different.
Processed 12,088,664,836 bytes in 1 hour, 14 minutes, and 18 seconds.
Throughput rate: 155.2 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: Monday, January 20, 2003 at 9:09:02 AM
Job completion status: Failed
======================================================================


Note: the skipped files on C: are “test” viruses that came with our virus software and we have not deleted them yet. (They shouldn’t harm anything)

I am about to give up on this thing and just uninstall / reinstall because its really starting to get to me. I just thought that I would post again to see if anyone here could find anything in the log or explain to me what’s going on here.

Thank you,

Paul

Veritas Backup Exec!

 

[TechJosh]

I am experiencing a similar problem on a network I work with. My boss has asked me to take over some of the lighter admin duties, but BE is not my strong-point. Here's a sampling of my log:

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

Media Name: "Media created 1/17/03 11:19:22 PM"
Backup of "\\HCNT3\MUG Mug Folder-Law Enforcement"
Backup set #18 on storage media #1
Backup set description: "HCNT3_FWKLY_BU"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 1/18/03 at 3:32:11 PM.

Backup completed on 1/18/03 at 3:57:06 PM.
Backed up 62230 files in 440 directories.
Processed 967,195,248 bytes in 24 minutes and 55 seconds.
Throughput rate: 37.0 MB/min
----------------------------------------------------------------------
Performing Remote Agent backup

Media Name: "Media created 1/17/03 11:19:22 PM"
Backup of "\\HCNT3\Resources "Event logging files""
Backup set #19 on storage media #1
Backup set description: "HCNT3_FWKLY_BU"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 1/18/03 at 3:57:07 PM.

Backup completed on 1/18/03 at 3:57:14 PM.
Backed up 14 files in 1 directory.
Processed 2,012,084 bytes in 7 seconds.
Throughput rate: 16.4 MB/min
----------------------------------------------------------------------
Performing Remote Agent backup

Media Name: "Media created 1/17/03 11:19:22 PM"
Backup of "\\HCNT3\SMS_HCS SMS Site HCS 11/15/00"
Backup set #20 on storage media #1
Backup set description: "HCNT3_FWKLY_BU"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 1/18/03 at 3:57:14 PM.

Drive and media information from media mount:
Robotic Library Name: DELL 1
Drive Name: DELL 1
Slot: 3
Media GUID: {F28E12F1-70B6-4C57-AF54-DAF72BBB33A3}
Media Label: WK7SLOT3HCNT3
Overwrite Protection Time Left: None
Append Time Left: Infinite
Targeted Media Set Name: SLOT3 HCNT3 FULL
The media provided to continue the backup already contains data
from one or more sets created during this operation.
The operation can not be continued

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

It always occurs on SLOT3 and it doesn't matter what tape set we use (robotic backup system w/ 8 slots), it always fails on SLOT3 for some reason.

We also have trouble backing up a particular SQL database, as well as backing up certain files from our NT4.0 Terminal Server.

Any thoughts on this? I'm at wits end and I'm not sure what to do--pay VERITAS for support or reinitialize all SLOT3 tapes.

TechJosh

 

[SQLBill]

Paul,

Next time the job 'locks' up with 72% or whatever showing, try this:

Remove the tape, put a new tape in (or the original if it allows overwrite). When the message pops up, DO NOT EJECT the tape, just leave it in and select "Respond OK'.

I have found that, sometimes, the popup window is 'delayed'. Meaning that it shows up after the action already happened. I think that's what is happening in your case. It's telling you to remove the media when you already have done so.

-SQLBill

 

[dln2560]

This is the same problem we are having - I have tried putting in a blank tape and responding to the question yes that I have blank overwritable media in the drive. It still just sits and waits forever - until I cancel the job.

I would love to use two tapes if it would let me - the older version of BE let us used two tapes for our full Friday backup.

Can someone tell me how to change the settings so that it will allow this?

Thanks

DLN

 

[bryanblc]

I am having a similar problem with Backup Exec 8.6. I have a single drive and after it writes 13-15 gigs it stops with the error media mount failed. I have tried everything including adding a new tape and nothing seems to work. Does anyone have any ideas?

 

[smeek]

Pmidwest- Not sure if you ever corrected, but did you verify that the drive format and tape format were the same (don't laugh, I had some client buy a DDS4 drive and buy new DDS3 tapes). I think that any "Corrupt" file error will mark the job as failed. It also looked like you had an issue with your Exchange backups. You can always exclude certain files from your backups (Veritas has docs on excluding SQL, Exchange, Oracle and other files that are being captured by an agant. I believe they suggest excluding certain anti-virus files, too.)


dln2560- BENT does allow you to use 2 tapes. Note that in addition to the Tools>Options global settings, that you can also have settings per individual job that overrule the global ones. Right-click on your job, open properties and verify the settings.


bryanblc- Media mount is a diff error. I have found that occur when I have a bad drive or when I have driver/update issues. What brand server, whose driver you using...