Solved

Arcserve 11.1 with sp2 Merge Problems

Posted on 2007-03-18
24
4,889 Views
Last Modified: 2013-11-14
Hello all,

I am quite deperate here so I hope someone can help.

Here is the story with logs and details below.

I am running Arcserve version 11.1 with SP2 installed. The OS is Windows 2003 Standard with SP1 which runs on a Dell Poweredge 2850 server.

The tape media I am using is LTO2 Ultrium Tapes. The error I am about to state is happening with multiple month end tape sets. At one point merging these tapes worked fine. Each month end set is from a brand new purchase of tapes so I do not believe I have multiple sets of bad brand new mdia.

Secondly the original tape drive that I had was Overland Powervault. The device was over 3 years old and I had thought the error I was possible receiving was due to the fact that the device was damaged so now i have a brand new Overland Arcvault 24. The same problem still persists.

So now on to the details. Whenever I try to merge a tape set by either merging the whole set or by session the job fails afters a few minutes. The merge seems to be fine for about 5 minutes or so and then it just dies.

Below is the the log error codes I receive are error 6304 (scsi sense error code), followed by a e8005, and e3713. I will copy and paste these if anyone needs them.

I have also tried reinstalling sp2 for arcserve which hasnt helped.

Does anyone have any suggestions as to what I can do? I am really enrvous as I need to be able to merge and recover from my month end tapes.

If anyone needs more info on the device or set up please let me know.



0
Comment
Question by:PatrickPinto
  • 15
  • 9
24 Comments
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18747386
I just tried uninstlalling and reinstalling arcserve and trying it again but that did not help matters.
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18748759
Here are a few ideas:
1) update
install the Tape Engine update
http://supportconnectw.ca.com/public/storage/downloads/nt/111/basb111-patchmenu.asp
QO84873 10.9 MB 12/18/06 NT -DEVICE SUPPORT UPDATE 9

2) try a sequential merge, it is slow and will take as long as the backup took, but will tell you if the problem is related to the catalog merge. Add this registry hack to force it.
Go to HKEY_LOCAL_MACHINE on Local Machine
Open it to
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task
Highlight Task and select Edit Add Key from the menu bar.
Key Name: Merge
Class: <leave blank>
Highlight Merge and select Edit Add Value
Value Name: DonotUseCatalogMerge
Data Type: REG_DWORD
click OK
Data: 1         *// 1 = Enabled, 0 = Disabled

3) Put the Tape Engine into Detail mode (ARCserve Server Admin, Configuration, Tape Engine tab, message level Detail) then reproduce the problem and copy the section of tape.log here at the time and just prior to the error. Get the time stamp from the activity log.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18749754
Thanks for the response! I installed the patch 9 in between this post and response. After trying another merge it still failed.

I added the registry key in and added the message level Detail as you recommended. I am going to try a merge now and will let you know the results.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18750031
Dont want to speak to soon but the change after you had me do the registry edit seems to work now. It has merged over seven sessions and has been running for a bit now. I choose an incremental tape since it would be faster to merge completely. I will get back to you within an hour with a status update.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18750699
Something weird happened. After merging around seven sessions from the icnremental it started repeating one of the sessions over and over again. It kept merging the same servers data into a new session around 20 times...I stopped it because it seemed wrong. Any idea why this would happen?

I am going to try a merge of a regular month end tape set now.
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18750706
There are several things that could be causing this problem. It is possible the Tape Engine update fixed it. So when this merge finishes set this registry setting to 0 to disable it. Then try the regular catalog merge on a backup that was done after the Tape Engine update was installed. It could be that with the update only the old backups will not merge via the default catalog merge but new backups will work correctly.
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18750812
My last post was on the original problem not on the repeating sequential merge. Really not sure on that one. I think it is more likely to be a problem with that specific session and unlikely to happen again.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18751285
Still no go. Even with it set to 1 for the registry entry it did not work. Below is some of the last entris from the tape.log.

03/19 15:47:54 [1304] =>ABSL:3010 [REQUEST SENSE   ] 03 00 00 00 40 00 00 00 00 00
03/19 15:47:54 [1304]             <LOAD                >, Sense Data as Follows:
03/19 15:47:54 [1304]          SENSE ABSL:3010      70 00 02 00 00 00 00 10 00 00 00 00 3a
03/19 15:47:54 [1304]       EX SENSE ABSL:3010      00 00 00 74 9a 00 00 00 00 00 00 00 00 00 00 00
03/19 15:47:54 [1304]          SENSE ABSL:3010      Not Ready [02]
03/19 15:47:54 [1304]       EX SENSE ABSL:3010      Medium Not Present [3a, 00]
03/19 15:47:54 [1304]      LDN:5 MOVE->: TapeName[M-PHL-FRI-10/27/06] RID[A643] Seq[2] BarCode[] Slot[7]
03/19 15:47:54 [1304]      LDN:5 MOVE->: From Slot[7] Element[0x0027]
03/19 15:47:54 [1304]      LDN:5 MOVE->: To Drive[4] ABSL[3010] S/N[HU10650RK1] Element[0x00C0]
03/19 15:47:54 [1304] =>ABSL:3011 [MOVE MEDIUM     ] a5 20 00 00 00 27 00 c0 00 00 tt[20]
03/19 15:48:52 [1304]      LDN:5 Indicates that the tape needs to be read in
03/19 15:48:52 [1304] =>ABSL:3010 [TEST UNIT READY     ] 00 00 00 00 00 00 00 00 00 00
03/19 15:48:52 [1304] =>ABSL:3010 [REQUEST SENSE   ] 03 00 00 00 40 00 00 00 00 00
03/19 15:48:52 [1304]             <TEST UNIT READY     >, Sense Data as Follows:
03/19 15:48:52 [1304]          SENSE ABSL:3010      70 00 06 00 00 00 00 10 00 00 00 00 28
03/19 15:48:52 [1304]       EX SENSE ABSL:3010      00 00 00 94 09 00 00 00 00 00 00 00 00 00 00 00
03/19 15:48:52 [1304]          SENSE ABSL:3010      Unit Attention [06]
03/19 15:48:52 [1304]       EX SENSE ABSL:3010      Not Ready to Ready Transition(Medium May Have Changed) [28, 00]
03/19 15:48:52 [1304] Drive[4] Waiting to become ready with media from Slot[7]
03/19 15:48:58 [1304] ChgGetSlotFlags(): Slot [7] has SlotFlag [0x18002100] for Changer Device [5]
03/19 15:48:58 [1304] =>ABSL:3010 [LOAD TAPE       ] 1b 00 00 00 01 00 00 00 00 00 tt[30]
03/19 15:48:58 [1304] =>ABSL:3010 [MODE SENSE      ] 1a 00 00 00 0c 00 00 00 00 00 tt[5]
03/19 15:48:58 [1304]    MS Page[00] ABSL:3010      0b 00 10 08 42 00 00 00 00 01 00 00
03/19 15:48:58 [1304]                ABSL:3010      00 00 00 00 00 00 00 00 00 00 00 00
03/19 15:48:58 [1304]         DRV:4 Tape is NOT Write Protected
03/19 15:48:58 [1304] =>ABSL:3010 [MODE SENSE      ] 1a 00 0f 00 1c 00 00 00 00 00 tt[5]
03/19 15:48:58 [1304]    MS Page[0f] ABSL:3010      1b 00 10 08 42 00 00 00 00 01 00 00
03/19 15:48:58 [1304]                ABSL:3010      0f 0e c0 80 00 00 00 01 00 00 00 01
03/19 15:48:58 [1304]         DRV:4 Compression Enabled
03/19 15:48:58 [1304] =>ABSL:3010 [INQUIRY         ] 12 00 00 00 40 00 00 00 00 00 tt[1]
03/19 15:48:58 [1304] ---------------INQUIRY HEX DUMP----------------
03/19 15:48:58 [1304] Hexdump Starts --------------------
03/19 15:48:58 [1304] 01 80 03 02 5b 10 11 32 48 50 20 20 20 20 20 20   ....[..2HP      
03/19 15:48:58 [1304] 55 6c 74 72 69 75 6d 20 33 2d 53 43 53 49 20 20   Ultrium 3-SCSI  
03/19 15:48:58 [1304] 44 32 31 48 00 00 00 00 01 00 00 00 00 00 00 00   D21H............
03/19 15:48:58 [1304] 00 00 00 00 00 00 00 00 0d 00 00 5c 0b 56 03 00   ...........\.V..
03/19 15:48:58 [1304]
03/19 15:48:58 [1304] DEVICE4 [HP      Ultrium 3-SCSI  D21H] - WORM drive
03/19 15:48:58 [1304] [Ultrium 3-SCSI  D21H] WORM drive
03/19 15:48:58 [1304] =>ABSL:3010 [MODE SENSE      ] 1a 00 00 00 40 00 00 00 00 00 tt[5]
03/19 15:48:58 [1304]    MS Page[00] ABSL:3010      0b 00 10 08 42 00 00 00 00 01 00 00
03/19 15:48:58 [1304]                ABSL:3010      0f 0e c0 80 00 00 00 01 00 00 00 01
03/19 15:48:58 [1304] NOT WORM []loaded
03/19 15:48:58 [1304] DB: Updating tapeusage in database: START
03/19 15:48:58 [1304] DB: Finished Updating tapeusage in database: END
03/19 15:48:58 [1304] =>ABSL:3010 [REWIND          ] 01 00 00 00 00 00 00 00 00 00 tt[30]
03/19 15:48:58 [1304] =>ABSL:3010 [READ POSITION   ] 34 00 00 00 00 00 00 00 00 00 tt[6]
03/19 15:48:58 [1304]         DRV:4 Current block #: [00000000] [0]
03/19 15:48:58 [1304] =>ABSL:3010 [MODE SENSE      ] 1a 00 00 00 0c 00 00 00 00 00 tt[5]
03/19 15:48:58 [1304]    MS Page[00] ABSL:3010      0b 00 10 08 42 00 00 00 00 01 00 00
03/19 15:48:58 [1304]                ABSL:3010      00 00 00 00 00 00 00 00 00 00 00 00
03/19 15:48:58 [1304] =>ABSL:3010 [READ            ] 08 01 00 00 01 00 00 00 00 00 tt[20]
03/19 15:49:01 [1304]         DRV:4 Read Tape Header Sequence Number: [2]
03/19 15:49:01 [1304]         DRV:4 Read Tape Header Random ID: [A643]
03/19 15:49:01 [1304]         DRV:4 Read Tape Header Tape Name: [M-PHL-FRI-10/27/06      ]
03/19 15:49:01 [1304]         DRV:4 Read Tape Header PreviousSessions: [18]
03/19 15:49:01 [1304] =>ABSL:3010 [REWIND          ] 01 00 00 00 00 00 00 00 00 00 tt[30]
03/19 15:49:04 [1304] =>ABSL:3010 [READ POSITION   ] 34 00 00 00 00 00 00 00 00 00 tt[6]
03/19 15:49:04 [1304]         DRV:4 Current block #: [00000000] [0]
03/19 15:49:04 [1304] DB: DBRegisterTape is being called. DBState[2]
03/19 15:49:04 [1304] DB: CAlling DBRegisterTapeInternal() [2]
03/19 15:49:04 [1304] DB: Registering tape [M-PHL-FRI-10/27/06] in database: START
03/19 15:49:04 [1304] 1. Local Database: TapeName []; BarCode []; RamdomID: [0]; Seq# [0]; PoolName []; PoolStatus: [0]
03/19 15:49:04 [1304] 1. From tape Header: TapeName [M-PHL-FRI-10/27/06]; BarCode []; RamdomID: [ffffa643]; Seq# [2]
03/19 15:49:04 [1304] DB: NAS Enabled Device BOOL[0] SEQ[2]
03/19 15:49:04 [1304] DB: Finished Registering tape [M-PHL-FRI-10/27/06] in database: END
03/19 15:49:04 [1304] DB: Retrieving tape record from database: START
03/19 15:49:04 [1304] DB: Finished Retrieving tape record from database: END
03/19 15:49:04 [1304] ChgGetSlotFlags(): Slot [7] has SlotFlag [0x18002100] for Changer Device [5]
03/19 15:49:04 [1304]      LDN:5 Mark Slot[7] is in use, tf:18002100
03/19 15:49:04 [1304] Slot[7] NO WORM Flag
03/19 15:49:04 [1304] ChgEnterSlotInfo(): Updating Slot [7] with SlotFlag [0x18002121] for Changer Device [5]
03/19 15:49:04 [1304] ClientConnectToTape:: usSlotNo = 7, currentDrive = 4, nReservedDrives = 0, nFreeDrives = 0 -- jID[8], mID[0], jTKN[3645500], jNUM@2@, dcb[4]
03/19 15:49:04 [1304] CheckTheFlags(): SlotFlag [0x18002121] SelectionFlag [7]
03/19 15:49:04 [1304] CheckTheFlags(): Complete match
03/19 15:49:04 [1304] Doing a LogSelect
03/19 15:49:04 [1304] =>ABSL:3010 [LOG SELECT      ] 4c 02 c0 00 00 00 00 00 00 00 tt[5]
03/19 15:49:04 [1304] ClientConnectToTape(): Setting EnumTape.bDontCheckMediaInUse to TRUE
03/19 15:49:04 [1668] DB: Updating tape info for read pass in database: START
03/19 15:49:04 [1668] DB: Finished Updating tape info for read pass in database: END
03/19 15:49:04 [1668]        DRV:4 Returning from ReadTapeHeader 0
03/19 15:49:04 [0ae0] LDN:4 Goto Absolute Session: [19]; JobType: [42h]
03/19 15:49:04 [0ae0] =>ABSL:3010 [REWIND          ] 01 00 00 00 00 00 00 00 00 00 tt[30]
03/19 15:49:04 [0ae0] =>ABSL:3010 [READ POSITION   ] 34 00 00 00 00 00 00 00 00 00 tt[6]
03/19 15:49:04 [0ae0]         DRV:4 Current block #: [00000000] [0]
03/19 15:49:04 [0ae0] =>ABSL:3010 [SPACE 2 FM      ] 11 01 00 00 02 00 00 00 00 00 tt[300]
03/19 15:50:25 [0ae0] =>ABSL:3010 [READ POSITION   ] 34 00 00 00 00 00 00 00 00 00 tt[6]
03/19 15:50:25 [0ae0]         DRV:4 Current block #: [0027a617] [2598423]
03/19 15:50:25 [0ae0] DYNAMICALLY SHARED SAN DEVICE  -> FALSE
03/19 15:50:25 [0ae0] OPTIMAL DEVICE HANDLE -> ADDRESS[0x00489F10]
03/19 15:50:25 [1668] MEM: Total Physical Memory 2146713600
03/19 15:50:25 [1668] MEM: Avail Physical Memory 1609822208
03/19 15:50:25 [1668] MEM: Avail Page File -596488192
03/19 15:50:25 [1668] MEM: Total Avail memory 1013334016
03/19 15:50:25 [1668] MEM: Total Buffers returned 2048, 32768 KB
03/19 15:50:25 [1668]         DRV:4 Daemon chuncks to use:2048 for JobID[8]
03/19 15:50:25 [1668] ClientStartSession(): Going to use Global namespace for SharedMem
03/19 15:50:25 [1668] ClientStartSession(): Using Global namespace for SharedMem.
03/19 15:50:25 [1668] ClientStartSession(): Assign Global namespace for SharedMem
03/19 15:50:25 [1668] ClientStartSession(): After global namespace.
03/19 15:50:25 [1668] CreateSharedMem(): Connection Type [4]
03/19 15:50:25 [1668]         DRV:4 ReadShots:4
03/19 15:50:25 [1668]         DRV:4 WriteShots:4
03/19 15:50:25 [1668]         DRV:4 ReadDeamon thread created TID[1050]
03/19 15:50:25 [1668] =>ABSL:3010 [READ ] Logging *DISABLED*
03/19 15:58:25 [1050] 15:58:25 =>ABSL:3010 [READ                ] 08 01 00 00 01 00 00 00 00 00
03/19 15:58:25 [1050] =>ABSL:3010 [REQUEST SENSE   ] 03 00 00 00 40 00 00 00 00 00
03/19 15:58:25 [1050]             <READ                >, Sense Data as Follows:
03/19 15:58:25 [1050]          SENSE ABSL:3010      f0 00 03 00 00 00 01 10 00 00 00 00 14
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      00 00 00 50 8f 00 00 00 00 00 00 00 00 00 00 00
03/19 15:58:25 [1050]          SENSE ABSL:3010      Media Error [03]
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      Recorded Entity Not Found [14, 00]
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] !!!!! Media error encountered, device[4][SN:]
03/19 15:58:25 [1050] !!!!! We'll retry reading the block(s). RetryCount[1]
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] =>ABSL:3010 [READ POSITION   ] 34 00 00 00 00 00 00 00 00 00 tt[6]
03/19 15:58:25 [1050]         DRV:4 Current block #: [0027fe3a] [2620986]
03/19 15:58:25 [1050] ** hDevice->pTapeInfo->blocksRead[2888064] ulBlocksIn512Byte[2888064] hDevice->ulCurrentBlockAddress[2598423]
03/19 15:58:25 [1050] ABSL:3010 SCSICommandRetry: Didn't actually Read.
03/19 15:58:25 [1050] Default Tape Block Size for Device [4] is [65536]
03/19 15:58:25 [1050] =>ABSL:3010 [MODE SENSE      ] 1a 00 00 00 0c 00 00 00 00 00 tt[5]
03/19 15:58:25 [1050]    MS Page[00] ABSL:3010      0b 00 10 08 42 00 00 00 00 01 00 00
03/19 15:58:25 [1050]                ABSL:3010      00 00 00 00 00 00 00 00 00 00 00 00
03/19 15:58:25 [1050] Current Tape Block Size for Device [4] is [65536]
03/19 15:58:25 [1050] 03/19 15:58:25 ABSL:3010 SCSICommandRetry: Retry Read.
03/19 15:58:25 [1050] 15:58:25 =>ABSL:3010 [READ                ] 08 01 00 00 01 00 00 00 00 00
03/19 15:58:25 [1050] =>ABSL:3010 [REQUEST SENSE   ] 03 00 00 00 40 00 00 00 00 00
03/19 15:58:25 [1050]             <READ                >, Sense Data as Follows:
03/19 15:58:25 [1050]          SENSE ABSL:3010      f0 00 03 00 00 00 01 10 00 00 00 00 14
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      00 00 00 50 8f 00 00 00 00 00 00 00 00 00 00 00
03/19 15:58:25 [1050]          SENSE ABSL:3010      Media Error [03]
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      Recorded Entity Not Found [14, 00]
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] !!!!! Media error encountered, device[4][SN:]
03/19 15:58:25 [1050] !!!!! We'll retry reading the block(s). RetryCount[2]
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] =>ABSL:3010 [READ POSITION   ] 34 00 00 00 00 00 00 00 00 00 tt[6]
03/19 15:58:25 [1050]         DRV:4 Current block #: [0027fe3a] [2620986]
03/19 15:58:25 [1050] ** hDevice->pTapeInfo->blocksRead[2888064] ulBlocksIn512Byte[2888064] hDevice->ulCurrentBlockAddress[2598423]
03/19 15:58:25 [1050] ABSL:3010 SCSICommandRetry: Didn't actually Read.
03/19 15:58:25 [1050] Default Tape Block Size for Device [4] is [65536]
03/19 15:58:25 [1050] =>ABSL:3010 [MODE SENSE      ] 1a 00 00 00 0c 00 00 00 00 00 tt[5]
03/19 15:58:25 [1050]    MS Page[00] ABSL:3010      0b 00 10 08 42 00 00 00 00 01 00 00
03/19 15:58:25 [1050]                ABSL:3010      00 00 00 00 00 00 00 00 00 00 00 00
03/19 15:58:25 [1050] Current Tape Block Size for Device [4] is [65536]
03/19 15:58:25 [1050] 03/19 15:58:25 ABSL:3010 SCSICommandRetry: Retry Read.
03/19 15:58:25 [1050] 15:58:25 =>ABSL:3010 [READ                ] 08 01 00 00 01 00 00 00 00 00
03/19 15:58:25 [1050] =>ABSL:3010 [REQUEST SENSE   ] 03 00 00 00 40 00 00 00 00 00
03/19 15:58:25 [1050]             <READ                >, Sense Data as Follows:
03/19 15:58:25 [1050]          SENSE ABSL:3010      f0 00 03 00 00 00 01 10 00 00 00 00 14
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      00 00 00 50 8f 00 00 00 00 00 00 00 00 00 00 00
03/19 15:58:25 [1050]          SENSE ABSL:3010      Media Error [03]
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      Recorded Entity Not Found [14, 00]
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] !!!!! Failed to retry reading the blocks.!!!!!
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] !!!!! We'll set the tape to OFF LINE
03/19 15:58:25 [1050]      LDN:5 ChgOriginalHomeSlot(): offset in TID:0 LDN:4 homeSlot[7] Invert:0
03/19 15:58:25 [1050] !!!!! Bad tape in Device[4] was from Slot[7].
03/19 15:58:25 [1050] !!!!! We now try to return this tape back to its slot, and mark it as UNREADABLE MEDIA.
03/19 15:58:25 [1050]      LDN:5 ...in ChgReturnTapeToHomeSlot
03/19 15:58:25 [1050]      LDN:5 ChgOriginalHomeSlot(): offset in TID:0 LDN:4 homeSlot[7] Invert:0
03/19 15:58:25 [1050] ChgSetSlotFlags(): Updating Slot [7] with SlotFlag [0x02000000] for Changer Device [5]
03/19 15:58:25 [1050]      LDN:5 Returning tape from Drive[4] to Slot :7.
03/19 15:58:25 [1050] Drive[4] Eject the tape from drive.
03/19 15:58:25 [1050] =>ABSL:3011 [READ ELEMENT STAT] b8 24 00 c0 00 01 00 00 00 80 tt[20]
03/19 15:58:25 [1050]      LDN:5 Element[0x00C0] Source Element[0x0027] Valid?[0x80]
03/19 15:58:25 [1050]       Drive[0x00c0] is FULL!
03/19 15:58:25 [1050]      LDN:5 Slot address of media in Drive[0x00c0] is [0x0027]
03/19 15:58:25 [1050] =>ABSL:3011 [READ ELEMENT STAT] b8 24 00 c0 00 01 00 00 00 80 tt[20]
03/19 15:58:25 [1050]      LDN:5 Element[0x00C0] Source Element[0x0027] Valid?[0x80]
03/19 15:58:25 [1050]      LDN:5 Moving Tape from Library Drive[4] to Slot[7]
03/19 15:58:25 [1050] =>ABSL:3010 [UNLOAD TAPE     ] 1b 00 00 00 00 00 00 00 00 00 tt[30]
0
 
LVL 22

Accepted Solution

by:
dovidmichel earned 500 total points
ID: 18753798
The tape drive is having a problem reading the tape.

03/19 15:58:25 [1050] 15:58:25 =>ABSL:3010 [READ                ] 08 01 00 00 01 00 00 00 00 00
03/19 15:58:25 [1050] =>ABSL:3010 [REQUEST SENSE   ] 03 00 00 00 40 00 00 00 00 00
03/19 15:58:25 [1050]             <READ                >, Sense Data as Follows:
03/19 15:58:25 [1050]          SENSE ABSL:3010      f0 00 03 00 00 00 01 10 00 00 00 00 14
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      00 00 00 50 8f 00 00 00 00 00 00 00 00 00 00 00
03/19 15:58:25 [1050]          SENSE ABSL:3010      Media Error [03]
03/19 15:58:25 [1050]       EX SENSE ABSL:3010      Recorded Entity Not Found [14, 00]
03/19 15:58:25 [1050] !!!!!
03/19 15:58:25 [1050] !!!!! Media error encountered, device[4][SN:]
03/19 15:58:25 [1050] !!!!! We'll retry reading the block(s). RetryCount[1]

The recorded entity not found is a bit of a deceptive media error. The drive can read the tape but it can not read what was previously written to the tape, if that makes any sense. In other words it is not like there is a bad spot on the tape and so it gets an unrecoverable data error, but the drive knows something was written to the tape but can not read what it is.

Try retentioning the tapes. Strange thing about LTOs IBM and HP both recommend it but Certance which is not Quantum does not. Regardless it should be tried.

This could be caused by the way the tapes were handled or stored, or the brand tapes.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18754114
Thanks for the response again...I am sorry if this is a dumb question but what to do I do to retention the tapes?
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18754820
Sorry I found how to do it...I am going to try it now. I will let you know how it goes.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18754916
The retension option is greyed out when I select a tape that I want to retension. What can I do to retention the tape?
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 22

Expert Comment

by:dovidmichel
ID: 18757147
I was afraid of this. I just tried it out and Retention does not work with Libraries. OK here is how to do it.

Run Device Configuration.
select Tape Library
at the next window select the drive/s under the library and click Remove
Click Exit
manually load tape in a drive
now Retention is available
when finished run Device Configuration again to setup the library as it was.
 
Here is a little blurb on retentioning from the LTO tape manual.
Tape Retensioning:
Ultrium data cartridges require periodic retensioning to operate properly. Retensioning reduces pack shift and stabilizes the tape pack. See your backup software manual for instructions on how to retensioning a tape cartridge. You should retension a tape cartridge under the following circumstances:
• If the cartridge is being used for the first time.
• If the tape cartridge has not been used for over a month.
• If the tape cartridge has been exposed to changes in temperature (first allow the media to acclimate to its surroundings).
• If the tape is “shoe shining” back and forth and backups are proceeding slowly.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18759282
David,

Thank you for this detailed. info. I am offsite but will be back in the office late tonight. I am going to try this before I leave.

Thanks again for all your time and expertise.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18764824
David,

I was able to retension the tapes. They still will not merge...I started getting an error 6300 windows NT scsi error now?

Patrick
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18766205
Check the Windows Event Viewer System log at the point in time the SCSI error was recorded in the tape log.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18796255
Hi David,

sorry for the delay.

I am getting two errors both event ID 15. One for hplto and the other libxprmc.

the hplto one says the \device\tape 0 is not ready and the libxprmc says the \device\chang is not ready.
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18796409
What brand tapes are being used?
Are there any other devices on that SCSI bus?
Are the tape drives and library disabled from within the OS Device Manager?
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18796479
TDK Ultrium 2 LTO Tapes.

No other devices on the scsi bus.

I realized I didnt mention taht I also have an overland reo 9000 that the backups dump to and then I use the tapecopy command to dump to tape on the Arcvault. The reo is configured as a virtual tape library/

The arcvault and the the vlt is not disabled as a tape drive...but for some reason arcserve did not like the arcvault of the overland neo medium changer was enabled so that is disabled.

If this all sounds confusing I can email you screenshots if you are interested?
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18796515
ARCserve does not use the OS tape device drivers so perhaps they are conflicting. Disable the tape drives also.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18796690
when i disable them do i need to run the device configuration again?
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18797205
david one more thing...I updated to the demo version of 11.5 to see if that would help. Obviously it hasnt but one thing I found odd was when the merge starts the first informational event logged in the job log says Session Type :Windows NTFS Drive.  Is that a clue to anything or am I just reading into something irrelevant?
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 18797644
Usually it is not necessary to run device configuration again.

It is just an informational message about the type of data contained in the session.
0
 
LVL 1

Author Comment

by:PatrickPinto
ID: 18890995
Got it fixed. Bad LTO3 Drive in the brand new arcvault. They have replaced it.

The first merge I tried to run failed with the catalog merge but then automatically tried doing it sequentially and succeeded. The next merge I ran used the catalog file fine and worked like a charm.

So looks like all is well.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Problem description :  Some external hard disks / USB flash drives do not show actual space as mentioned in the factory settings. This is a common problem when you use an 8 GB USB drive to make it bootable to install a firmware/ driver on a serv…
The article will include the best Data Recovery Tools along with their Features, Capabilities, and their Download Links. Hope you’ll enjoy it and will choose the one as required by you.
This video teaches viewers how to encrypt an external drive that requires a password to read and edit the drive. All tasks are done in Disk Utility. Plug in the external drive you wish to encrypt: Make sure all previous data on the drive has been …
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

743 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now