Hello Kent
We ran into this when we upgraded to netbackup 6.0. But with us it was using
IBM lto-2 tape drives in an IBM 3584 library attached to netapp R200 boxes.
With out solaris and hp/ux masters writing to IBM lto-2 tape drives in the same
libraries we did not see the problem.
We put the touch file in place and have not really tracked down the root
problem. But as I understand it, the netbackup code is generating advanced scsi
code with is either not supported by the IBM lto-2 tape drive or is changed by
the netapp or is incorrect to start with or some function of the prior causes.
Most likely using a 16 byte contol block which either is not supported by the
tape hardware, but there is no problem with using the older shorter control
block.
len
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces
at mailman.eng.auburn.edu] On Behalf Of Eagle, Kent
Sent: Monday, March 05, 2007 3:49 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] NO_SIXTEEN_BYTE_CDB touch file. Anyone else need this?
Environment:
NBU Enterprise 6.0 MP3
Master Server - Windows Server 2003 SP1
HBA Emulex LightPulse LP11002-E
Media Servers - Windows Server 2003 SP1
HBA Emulex LightPulse LP10000
Encryption - NeoScale CrypoStor FC702. Firmware fc-2.3.2-Build3
Library - ADIC (Quantum) i2000. Firmware 4.4.2
Drives - IBM FC LTO2 (IBM Ultrium-TD2). Driver
6.0.7.1 Drive Firmware 5AT0
The issue:
After a firmware upgrade on the i2000 and the CryptoStor's to the levels noted
above, all jobs using the Master server as the Media server would fail with
Exit Status 84. All jobs submitted to the Media servers ran without incident.
The only common denominator seems to be that the Master server has Emulex
LightPulse LP11002-E HBA's, and the Media servers run Emulex LightPulse LP10000
HBA's.
The solution provided by NeoScale was to utilize the following touch file on
the Master:
< install_dir >\ Volmgr\ database\ NO_SIXTEEN_BYTE_CDB " touch file.
This fixed the problem, but to this day no one seems to really know why.
There is an active case open with all 3 hardware vendors.
The following Tech Note was offered as a partial explanation; but it falls
short of being directly applicable to our problem/environment (we are running
FC LTO2's, not AIT-4).
http://seer.support.veritas.com/docs/281312.htm
I can't help but think this environment is not all that unique. Is anyone else
running this configuration, and if so, do you have to use the touch file?
Thank you,
Kent Eagle
MTS Infrastructure Engineer II, MCP, MCSE Tech Services / SMSS
Visit our website at www.wilmingtontrust.com
Investment products are not insured by the FDIC or any other governmental
agency, are not deposits of or other obligations of or guaranteed by Wilmington
Trust or any other bank or entity, and are subject to risks, including a
possible loss of the principal amount invested. This e-mail and any files
transmitted with it may contain confidential and/or proprietary information.
It is intended solely for the use of the individual or entity who is the
intended recipient. Unauthorized use of this information is prohibited. If
you have received this in error, please contact the sender by replying to this
message and delete this material from any system it may be on.
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|