Veritas Ejecting Tape Mid-Backup

Question

Veritas Ejecting Tape Mid-Backup

CharlieDav01 (IS/IT--Management)

(OP)

10 Nov 04 05:06

Hey there

I have a weird Veritas Problem. I have installed a new drive, as the old one was fubared! I installed the Veritas drivers for it (HP DDS4 SCSI) But when booting up my Windows 2000 Server it was erroring saying it couldnt load 4MMDDS_VRTS which is the Veritas driver failing to load. So i installed the HP drivers and did all the Tests and the drive passed all of them

So i do a full backup and leave it over night, but in the morning the tape has ejected and Veritas Job was saying "Loading Media" with an Activty report saying "Load Media Into Drive" So i reinserted the Tape back into the drive and the Job started to run again, but then Failed with the "On Hold (Failed)" Status. The whole job errored with this report

#####################################
#####################################

======================================================================
Job server: TLCSRV
Job name: Backup 0068
Job started: 08 November 2004 at 17:40:50
Job type: Backup
Job Log: BEX00.txt
======================================================================

Drive and media information from media mount:
Robotic Library Name:
Drive Name: HP
Slot: 0
Media GUID: {104D4D29-F104-4C65-A6B8-45B2EAE2D0BF}
Media Label: 4MM000010
Overwrite Protection Time Left: None
Append Time Left: Infinite
Targeted Media Set Name: Data Tape 2

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

Media Name: "Media created 08/11/2004 17:40:38 "
Backup of "C: "
Backup set #1 on storage media #1
Backup set description: "Backup 0068"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 08/11/2004 at 17:41:35 .
File "emc.log" in use - Backed up.
File "QTC_TEMP.001" in use - Backed up.
File "QTC_TEMP.002" in use - Backed up.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET2D.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET31.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\JETF99A.tmp in use - skipped.
File "MMC1.tmp" in use - Backed up.
File "~DFD853.tmp" in use - Backed up.
File "~DFD85B.tmp" in use - Backed up.
File "avg7log.log" in use - Backed up.
File "avg7log.log.lck" in use - Backed up.
File "avgdb.fdb" in use - Backed up.
File "adamm.log" in use - Backed up.
File "namesvc.log" in use - Backed up.
File "pvl.ldb" in use - Backed up.
File "pvl.mdb" in use - Backed up.

Drive and media information from media mount:
Robotic Library Name:
Drive Name: HP
Slot: 0
Media GUID: {104D4D29-F104-4C65-A6B8-45B2EAE2D0BF}
Media Label: 4MM000010
Overwrite Protection Time Left: None
Append Time Left: Infinite
Targeted Media Set Name: Data Tape 2
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 09/11/2004 at 09:39:38 .
Backed up 54077 files in 5277 directories.
13 files were in use
3 items were skipped.
Processed 22,729,633,003 bytes in 3 hours, 46 minutes, and 45 seconds.
Throughput rate: 95.6 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: 09 November 2004 at 09:39:38
Job completion status: Failed
======================================================================

#####################################
#####################################

So bascially the tape just ejects for no reason at about 22GB worth of data, its really weird! There are also no event errors in the Windows Event Log, apart from these:

################
Job "Backup 0068" ended in an error state. Examine recent event log entries and the job log for details.
################

###############
Job "Backup 0068" was canceled at the user's request.
###############

I am recieving lots of AVG Errors on my Server, this could be the problem, i dont know!

#################
! FireBird database error: Dynamic SQL Error SQL error code = -104 Unexpected end of command
#################

So basically Mid Backup my Tape ejects and when i re-enter the tape in the morning, it then fails!!!! I cant understand why this happening!

Any help would be much appreciated!

Cheers
Charlie

justin2000 (MIS) · Answer 1 · 2004-11-10 05:42:32

It's because the first tape is getting full.

When you insert the tape again - you get the error :-
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.

You are getting compression - Processed 22,729,633,003 bytes in 3 hours, 46 minutes, and 45 seconds
but obviously not enough.

Maybe you were sent a dud drive, or you need to update to Veritas drivers to see if it makes any difference.

CharlieDav01 (IS/IT--Management) · Answer 2 · 2004-11-10 09:23:25

The drive passes the compression test of 2.3:1 in HP Tools. I will uninstall Veritas and ReInstall, and use Vertias Drivers and see what happens.

Cheers
Charlie

CharlieDav01 (IS/IT--Management) · Answer 3 · 2004-11-10 09:23:27

It passed the compression test in HP Tools.... so i dont know what to do?!?! Im gonna uninstall/reinstall Veritas and use Veritas Drivers, will report back tomoz

Cheers
Charlie

SQLBill (MIS) · Answer 4 · 2004-11-10 09:25:17

Like Justin says, your tape is full. What size tapes are you using? Have you tried erasing the tapes and allowing overwrite? If you only allow append, eventually the tape will get full and require a second tape. Backup jobs cannot 'wrap around' to the beginning of the tape.

-SQLBill

justin2000 (MIS) · Answer 5 · 2004-11-10 17:42:52

You will never ever ever get compression of 2.3:1 when doing normal backups of servers. If you were backing up only text files then no problems, you may even get better compression.

CharlieDav01 (IS/IT--Management) · Answer 6 · 2004-11-16 08:13:45

guys i formatted the tape, and set over write, but still it errors and ejects.

these are brand new tapes

the drive can do compression as it did pass the test!

any other ideas?
Cheers
Charlie

SQLBill (MIS) · Answer 7 · 2004-11-16 08:46:01

I still say you are running out of room on the tapes.

BUT...

1. what size tapes are they? I know they are 4MM, but how much are they SUPPOSED to hold?

2. try setting the job for software compression.

3. Have you checked the Windows Event Viewer logs for related error messages?

-SQLBill

CharlieDav01 (IS/IT--Management) · Answer 8 · 2004-11-17 04:15:56

Right ok,,,,,,

The tapes are DDS 4 HP Tapes the ones they actually recomend for the drive. These tapes are 20/40's

I did a software compression last night and backed up 23GB of data

The event log had no errors in it

What course of action should i take now?

Cheers
Charlie

justin2000 (MIS) · Answer 9 · 2004-11-17 05:42:45

Stay with software compression as it is getting a better compression ratio for your files than what the hardware compression is doing.

CharlieDav01 (IS/IT--Management) · Answer 10 · 2004-11-17 06:03:09

Ok,,,,

Is this a standard and acceptable way to back up? here is the log from the completed backup:

======================================================================
Job server: TLCSRV
Job name: Backup 0008
Job started: 16 November 2004 at 16:16:29
Job type: Backup
Job Log: BEX01.txt
======================================================================

Drive and media information from media mount:
Robotic Library Name:
Drive Name: HP 1
Slot: 0
Media GUID: {86ADC258-3365-4907-8B7F-4ABE067F147E}
Media Label: 4MM000002
Overwrite Protection Time Left: None
Append Time Left: Infinite
Targeted Media Set Name: TLC

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

Media Name: "Media created 16/11/2004 16:14:43 "
Backup of "C: "
Backup set #1 on storage media #1
Backup set description: "Backup 0008"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 16/11/2004 at 16:16:52 .
File "emc.log" in use - Backed up.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET2.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET6.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET730D.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\1\JETCAA9.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\1\JETCAAA.tmp in use - skipped.
File "MMC1.tmp" in use - Backed up.
File "MMC2.tmp" in use - Backed up.
File "MMC3.tmp" in use - Backed up.
File "MMC4.tmp" in use - Backed up.
File "~DFFDD5.tmp" in use - Backed up.
File "~DFFDDE.tmp" in use - Backed up.
File "avg7log.log" in use - Backed up.
File "avg7log.log.lck" in use - Backed up.
File "avglog.log" in use - Backed up.
File "avglog.log.lck" in use - Backed up.
The item \Program Files\Grisoft\AVG TCP Server\journal.fil in use - skipped.
The item \Program Files\Grisoft\AVG TCP Server\transact.fil in use - skipped.
File "wb8.fil" in use - Backed up.
File "wbsqllog.txt" in use - Backed up.
File "adamm.log" in use - Backed up.
File "namesvc.log" in use - Backed up.
File "pvl.ldb" in use - Backed up.
File "pvl.mdb" in use - Backed up.
File "BEX02.txt" in use - Backed up.
File "dnary.ldb" in use - Backed up.
File "ias.ldb" in use - Backed up.
File "ias.mdb" in use - Backed up.
File "ex041116.log" in use - Backed up.
The item \WINNT\Temp\JET559F.tmp in use - skipped.
The item \WINNT\Temp\JET588D.tmp in use - skipped.

Backup completed on 16/11/2004 at 20:14:03 .
Backed up 62557 files in 5750 directories.
22  files were in use
9 items were skipped.
Processed 22,944,375,014 bytes in  3 hours,  57 minutes, and  11 seconds.
Throughput rate: 92.3 MB/min
Software compression ratio: 1.3:1
----------------------------------------------------------------------

Media Name: "Media created 16/11/2004 16:14:43 "
Backup of "\\TLCSRV\System?State "
Backup set #2 on storage media #1
Backup set description: "Backup 0008"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 16/11/2004 at 20:14:04 .

Backup completed on 16/11/2004 at 20:18:43 .
Backed up 2045 files in 105 directories.
Processed 298,261,758 bytes in  4 minutes and  39 seconds.
Throughput rate: 61.2 MB/min
Software compression ratio: 1.9:1
----------------------------------------------------------------------

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

Verify of "C: "
Backup set #1 on storage media #1
Backup set description: "Backup 0008"
Verify started on 16/11/2004 at 20:20:32 .

Verify completed on 16/11/2004 at 21:50:50 .
Verified 62557 files in 5750 directories.
0 files were different.
Processed 16,769,489,199 bytes in  1 hour,  30 minutes, and  18 seconds.
Throughput rate: 177.1 MB/min
----------------------------------------------------------------------

Verify of "\\TLCSRV\System?State "
Backup set #2 on storage media #1
Backup set description: "Backup 0008"
Verify started on 16/11/2004 at 21:50:52 .

Verify completed on 16/11/2004 at 21:51:40 .
Verified 2045 files in 105 directories.
0 files were different.
Processed 149,572,631 bytes in  48 seconds.
Throughput rate: 178.3 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: 16 November 2004 at 21:51:40
Job completion status: Successful
======================================================================

Does this all look ok?

Cheers
Charlie

is there a reason why a new drive cant do the compression needed?

justin2000 (MIS) · Answer 11 · 2004-11-18 04:33:37

Looks like software is getting better compression than you hardware.

The compression is ALL to do with the drive - it will keep writing to it, compressing on the fly until it is full - then it will spit it out and tell backup exec u need a new tape.

CharlieDav01 (IS/IT--Management) · Answer 12 · 2004-11-22 04:59:59

Hey guys,

My backup errored again this morning!!! I am not sure what is going on here

#############################
======================================================================
Job server: TLCSRV
Job name: TLC:Full
Job started: 19 November 2004 at 22:00:03
Job type: Backup
Job Log: BEX05.txt
======================================================================

Drive and media information from media mount:
Robotic Library Name:
Drive Name: HP 1
Slot: 0
Media GUID: {F0DE9B47-AD9C-41F7-9F5C-316A4A3AEB08}
Media Label: 4MM000009
Overwrite Protection Time Left: None
Append Time Left: 3 Days
Targeted Media Set Name: Rotation - Full

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

Media Name: "Media created 18/11/2004 14:16:21 "
Backup of "C: "
Backup set #1 on storage media #1
Backup set description: "Media created 18/11/2004 14:16:21 "
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 19/11/2004 at 22:00:50 .
File "emc.log" in use - Backed up.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET2.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\JET2F.tmp in use - skipped.
The item \Documents and Settings\Administrator\Local Settings\Temp\JETFC4B.tmp in use - skipped.
File "MMC1.tmp" in use - Backed up.
File "MMC2.tmp" in use - Backed up.
File "MMC3.tmp" in use - Backed up.
File "~DFDE2C.tmp" in use - Backed up.
File "~DFDE35.tmp" in use - Backed up.
File "avg7log.log" in use - Backed up.
File "avg7log.log.lck" in use - Backed up.
File "avglog.log" in use - Backed up.
File "avglog.log.lck" in use - Backed up.
The item \Program Files\Grisoft\AVG TCP Server\journal.fil in use - skipped.
The item \Program Files\Grisoft\AVG TCP Server\transact.fil in use - skipped.
File "wb8.fil" in use - Backed up.
File "wbsqllog.txt" in use - Backed up.
File "adamm.log" in use - Backed up.
File "namesvc.log" in use - Backed up.
File "pvl.ldb" in use - Backed up.
File "pvl.mdb" in use - Backed up.

Drive and media information from media mount:
Robotic Library Name:
Drive Name: HP 1
Slot: 0
Media GUID: {F0DE9B47-AD9C-41F7-9F5C-316A4A3AEB08}
Media Label: 4MM000009
Overwrite Protection Time Left: None
Append Time Left: 3 Days
Targeted Media Set Name: Rotation - 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

^ ^ ^ ^ ^

Backup completed on 22/11/2004 at 09:45:49 .
Backed up 59104 files in 5680 directories.
16 files were in use
5 items were skipped.
Processed 25,777,941,467 bytes in 4 hours, 13 minutes, and 2 seconds.
Throughput rate: 97.2 MB/min
Software compression ratio: 1.2:1
----------------------------------------------------------------------

======================================================================
Job ended: 22 November 2004 at 09:45:49
Job completion status: Failed
======================================================================
#######################

Can anyone suggest anything, i have now done software compression but it still errors out!

Cheers
Charlie

rtichnor (MIS) · Answer 13 · 2004-11-22 13:29:04

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

^ ^ ^ ^ ^

Look at the area above the carats (^)....

It looks like your tape is getting full and not being able to get another tape to continue the backup operation.

Zelandakh (MIS) · Answer 14 · 2004-11-22 15:26:55

22.9 worked without an error.
25.77 doesn't work and says it can't fit the data on the tape.

Honestly, we aren't all making this up. Your tape is full. Your data is fully compressed. Get a second drive and daisy chain it.

rtichnor (MIS) · Answer 15 · 2004-11-22 16:16:41

CharlieDav01,

Do you use a tape library?

It appears that the device needs another tape inserted to continue the backup.
Veritas cannot use the current tape to continue the backup because it is tape #1 of the current set.

SQLBill (MIS) · Answer 16 · 2004-11-23 13:06:36

1. You will never get the full compression amount onto a tape. Every file must be perfect and be able to be fully compressed. That will never happen.

2. Your backup has hit the end of the tape and since it cannot use the beginning of the tape without 'erasing' everything, it needs another tape.

PERIOD.

We all would like perfect compression. But tape manufactures give us compression values that are ONLY under perfect circumstances.

Sorry we can't give you the answer that you want.

-SQLBill

Come Join Us!

Posting Guidelines

Veritas Ejecting Tape Mid-Backup