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

MSL 6060 Drive connectivity

SOLVED
Go to solution
Akram Shaik
Frequent Advisor

MSL 6060 Drive connectivity

Dear,

Need to connect the MSL 6060 Tape drives.

Configuration is

MSL 6060
2 drives
One NSR (Single FC card)
One Library controller card


Kindly let knwo connectivity schema.

Thanks all

Regards,
Akram
when everyting is coming your way then you are in the wrong lane
5 REPLIES
Wei Jung
Trusted Contributor

Re: MSL 6060 Drive connectivity

Please see the diagram in the guide for the NSR,

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00637161/c00637161.pdf?jumpid=reg_R1002_USEN

pag18 Figure 10

Make sure the SCSI bus are terminated in the drives and not in the library controller.

There is an advisory about it here:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00659626&jumpid=reg_R1002_USEN
Akram Shaik
Frequent Advisor

Re: MSL 6060 Drive connectivity

Hi,

I connected in this manner,

SCSI1-Tapedrive1-terminator
Scsi2-tapedrive2-Robotic-terminator.

Scsi means the SCSI ports on the NSR with the FC port.

It is working fine and able to see the drives.

Is the cabling okay??


Regards,
Akram
when everyting is coming your way then you are in the wrong lane
Wei Jung
Trusted Contributor
Solution

Re: MSL 6060 Drive connectivity

Seem incorrect Akram.
Terminators should be in both drives.

Please open the guide and go to the page indicated. The picture is there, should be easier to follow.
Akram Shaik
Frequent Advisor

Re: MSL 6060 Drive connectivity

Hi Wei,

Actually with the config which I used worked with normal bkup but was failing with Oracle 11g DB backup with the following error ...
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/10/2008 10:07:26
ORA-19502: write error on file "testbkup<+ASM1_40:657020481:1>.dbf", block number 497409 (block size=1024)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_WriteObjData() failed! ERR(-2)

Recovery Manager complete.
[Major] From: ob2rman@bap01 "+ASM1" Time: 06/10/08 10:07:28
The database reported error while performing requested operation.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 06/10/2008 10:07:26
ORA-19502: write error on file "testbkup<+ASM1_40:657020481:1>.dbf", block number 497409 (block size=1024)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_WriteObjData() failed! ERR(-2)

Recovery Manager complete.

[Major] From: ob2rman@bap01 "+ASM1" Time: 06/10/08 10:07:28
Oracle Recovery Manager completed with errors.

[Major] From: ob2rman@bap01 "+ASM1" Time: 06/10/08 10:07:29
Backup of target database failed.

[Normal] From: BSM@prismaserver "testbkup" Time: 6/10/2008 10:05:23 AM
OB2BAR application on "bap01" disconnected.

[Normal] From: BSM@prismaserver "testbkup" Time: 6/10/2008 10:05:23 AM

Backup Statistics:

Session Queuing Time (hours) 0.00
----------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 1
Aborted Disk Agents .......... 0
----------------------------------------
Disk Agents Total ........... 1
========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 1
Aborted Media Agents ......... 0
----------------------------------------
Media Agents Total .......... 1
========================================
Mbytes Total ................. 487 MB
Used Media Total ............. 1
Disk Agent Errors Total ...... 1


============================================================================
Session completed with failures!
============================================================================



After changing the connection as referred in the advisory the DB backup also went fine.


Thanks for the valuable info shared..

Regards,
Akram..


Closing the thread.

when everyting is coming your way then you are in the wrong lane
Wei Jung
Trusted Contributor

Re: MSL 6060 Drive connectivity

Well the way you had it connected would work for slow drives, but the issue is that if you terminate it in the library controller, there is a known issue that the library wont be able to handle fast backups, meaning that after a while of started a backup, you might see I/O errors, CRC errors or failed backups because of the drive timing out.
By terminating the SCSI bus in the drive (for the drive daisy chained with the library controller) it will prevent the drive of running in degraded performance.