StoreEver Tape Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Ultrium 960 and OmniBack II Backups Failed on One Drive

Ultrium 960 and OmniBack II Backups Failed on One Drive

Hi,
We currently have the issue when backing up using OmniBack II with HP Ultrium 960 tape drives. The backups occasionally failed on one of the tape drive. We have 2 Ultrium 960 tape drives. The other tape drive has no problem at all. We greatly appreciate the help.

HP OmniBack II
Product Version: A.04.10
Internal built version: 176

We disabled Microsoft Removable Storage service.

Below is part of the debug.log:

4/10/2006 9:47:05 AM BMA.5260.2288 ["ma/spt/sctl_NT.c /main/r41/2":1844] A.04.10 b176
SCTL_Write: (scsi addr=6:0:3:0) error. [1026] ()


4/10/2006 9:47:05 AM BMA.5260.2288 ["ma/dev/devseq.c /main/r41/6":2353] A.04.10 b176
SeqWrite: (Tape1:0:3:0C): SCTL_Write()=-1: {1026}

4/10/2006 9:47:05 AM BMA.5260.2288 ["ma/dev/devseq.c /main/r41/6":2372] A.04.10 b176
SeqWrite: SCTL_Write() error. Tape drive status:
SeqWrite: SK : 00h
ASC : 00h
ASCQ: 00h
FRU : 00h
SeqWrite: B15 : 00h
B16 : 00h
B17 : 00h
LSB : 00h

4/11/2006 10:12:05 AM BMA.3172.2508 ["ma/spt/sctl_NT.c /main/r41/2":1844] A.04.10 b176
SCTL_Write: (scsi addr=6:0:3:0) error. [1026] ()


4/11/2006 10:12:05 AM BMA.3172.2508 ["ma/dev/devseq.c /main/r41/6":2353] A.04.10 b176
SeqWrite: (Tape1:0:3:0C): SCTL_Write()=-1: {1026}

4/11/2006 10:12:05 AM BMA.3172.2508 ["ma/dev/devseq.c /main/r41/6":2372] A.04.10 b176
SeqWrite: SCTL_Write() error. Tape drive status:
SeqWrite: SK : 00h
ASC : 00h
ASCQ: 00h
FRU : 00h
SeqWrite: B15 : 00h
B16 : 00h
B17 : 00h
LSB : 00h

4/23/2006 6:24:35 AM BMA.2508.2888 ["ma/spt/sctl_NT.c /main/r41/2":1844] A.04.10 b176
SCTL_Write: (scsi addr=6:0:3:0) error. [1026] ()


4/23/2006 6:24:35 AM BMA.2508.2888 ["ma/dev/devseq.c /main/r41/6":2353] A.04.10 b176
SeqWrite: (Tape1:0:3:0C): SCTL_Write()=-1: {1026}

4/23/2006 6:24:35 AM BMA.2508.2888 ["ma/dev/devseq.c /main/r41/6":2372] A.04.10 b176
SeqWrite: SCTL_Write() error. Tape drive status:
SeqWrite: SK : 00h
ASC : 00h
ASCQ: 00h
FRU : 00h
SeqWrite: B15 : 00h
B16 : 00h
B17 : 00h
LSB : 00h

4/30/2006 6:28:52 AM BMA.5184.3660 ["ma/spt/sctl_NT.c /main/r41/2":1844] A.04.10 b176
SCTL_Write: (scsi addr=6:0:3:0) error. [1026] ()


4/30/2006 6:28:52 AM BMA.5184.3660 ["ma/dev/devseq.c /main/r41/6":2353] A.04.10 b176
SeqWrite: (Tape1:0:3:0C): SCTL_Write()=-1: {1026}

4/30/2006 6:28:52 AM BMA.5184.3660 ["ma/dev/devseq.c /main/r41/6":2372] A.04.10 b176
SeqWrite: SCTL_Write() error. Tape drive status:
SeqWrite: SK : 00h
ASC : 00h
ASCQ: 00h
FRU : 00h
SeqWrite: B15 : 00h
B16 : 00h
B17 : 00h
LSB : 00h

5/1/2006 10:53:44 AM BMA.6040.3624 ["ma/spt/sctl_NT.c /main/r41/2":1844] A.04.10 b176
SCTL_Write: (scsi addr=6:0:3:0) error. [1026] ()


5/1/2006 10:53:44 AM BMA.6040.3624 ["ma/dev/devseq.c /main/r41/6":2353] A.04.10 b176
SeqWrite: (Tape1:0:3:0C): SCTL_Write()=-1: {1026}

5/1/2006 10:53:44 AM BMA.6040.3624 ["ma/dev/devseq.c /main/r41/6":2372] A.04.10 b176
SeqWrite: SCTL_Write() error. Tape drive status:
SeqWrite: SK : 00h
ASC : 00h
ASCQ: 00h
FRU : 00h
SeqWrite: B15 : 00h
B16 : 00h
B17 : 00h
LSB : 00h
3 REPLIES
Kurt Beyers.
Honored Contributor

Re: Ultrium 960 and OmniBack II Backups Failed on One Drive

Allison,

There is a good chance that OBII4.1 did not support Ultrium3 yet. And it is itself no longer supported.

An upgrade to DP5.5 should be planned. This is what HP support will tell you too.

best regards,
Kurt

Re: Ultrium 960 and OmniBack II Backups Failed on One Drive

Thanks for the information. That was what we got when we contacted HP. However, backups are running fine on one tape drive; and always failed on the other (especially with large backups). Do you guys have any idea why? Any help would be greatly appreciated. Please see previous post for debug.log.
Kurt Beyers.
Honored Contributor

Re: Ultrium 960 and OmniBack II Backups Failed on One Drive

Allison,

I cannot extract further information from the debug.log file, this requires further analysis from within HP.

The upgrade of OBII4.1 to DP5.5 is however that straightforward and easy that I would waist any time on it and plan it is as fast as possible.

And check the SCSI cabling once more, a bad connection here often can cause problems too.

best regards,
Kurt