Getting errors backing up a Windows SAN

10 pts.
Backup and Recovery
Microsoft Windows Server 2003
Storage Area Network
I am running a Windows 2003 server on a SAN. using 2 qlogic 2300's connected to the IBM 2109-f16 switch. A IBM 4560slx tape library using a FCO (Fibre channel option) card in the library. The FCO card is connected to the IBM 2109-f16 switch. I have "port" zoned the Server and the library in one zone. I cannot write to tapes with this setup. Get Device errors,communication errors, then the drive is taken off line. But if I remove the FCO cable from the IBM 2109-f16 switch and plug it directly in the HBA's on the server it will write to the tapes. What am i missing?

Answer Wiki

Thanks. We'll let you know when a new response is added.

It is usually best practice to use a separate HBA in the fabric for tape access. Doing so keeps streaming tape traffic separate from standard disk traffic in the SAN. You can zone out the tape HBA with the tape port on the switch, which will decrease the impact of tape reset/rewind issues from your disk traffic. Also, make sure your tape library supports the FC-SW (fibre channel switched) protocol, and is not FC-AL (fibre channel arbitrated loop) only. If your tape library is FC-AL only, you still have options. Since the IBM 2109-f16 is actually a re-branded Brocade switch, you may be able to use the Brocade ?Quickloop? feature to attach the tape drive to a quickloop port on the switch.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • MrMagoobluebottom
    Hi Mark. Might I suggest you take a look at Microsoft Knowledgebase Article #842411. This deals with Windows 2003 servers in a SAN environment. There is a runaway service called TUR (test unit ready) that pings the devices consistently, causing timeouts to happen in a tape library unit. Zoning is always a good idea, as this separates the disk traffic from the tape traffic. However, that is not enough when running a win2003 server. The change is a registry change. Microsoft broke the RSM (removable storage manager) in this version, and it has been causing havoc in the tape library industry (when connected via a SAN). Hope this helps. MrMagoo
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: