Yoseph,
The CDB issue in this technote relates directly to SCSI commands/calls,
and NDMP so I feel it may still be appropriate for you to investigate
this.
As I mentioned, my environment was also divided between master server
and media server, but we only experienced the problem on the master.
The nice thing about the touch files is you don't even have to cycle
services. I believe you can create them anytime (except when a catalog
is running). It just "reads" it when the next backup launches. You can
delete it when NetBackup isn't doing anything.
If you're not comfortable with the proposed solution, I would strongly
suggest opening a call with Symantec support to get their input. There
may be a better way.
I wish you success,
Kent Eagle
Systems Engineer, MCP, MCSE
Tech Services / SMSS
------------------------------
Message: 4
Date: Sun, 12 Nov 2006 17:02:01 -0800 (PST)
From: Yoseph Leleputra <leleputra at yahoo.com>
Subject: Re: [Veritas-bu] Media write error at NDMP (Yoseph Leleputra)
To: "Eagle, Kent" <KEagle at WilmingtonTrust.com>
Cc: veritas-bu at mailman.eng.auburn.edu
Message-ID: <20061113010202.74684.qmail at web54711.mail.yahoo.com>
Content-Type: text/plain; charset="us-ascii"
thanks for reply ..
my drive type is IBM SCSI - LTO 2
my backup problem only happen to NDMP drive . Backup still running welll
at drive who attached at my Master server
so from my 10 drive i devide 2 group : 6 drive for NDMP ( problematic
drive ) attach to Netapp storage and 4 drive attach to my Master sever (
work fine ) .
----- Original Message ----
From: "Eagle, Kent" <KEagle at WilmingtonTrust.com>
To: leleputra at yahoo.com
Cc: veritas-bu at mailman.eng.auburn.edu
Sent: Saturday, November 11, 2006 2:00:20 AM
Subject: re: Media write error at NDMP (Yoseph Leleputra)
Yoseph,
Are you using Emulex LP11002 HBA's?
We had an issue with Status 84 errors on just our Master after a
firmware upgrade on our i2000. All HBA drivers and firmware had remained
the same. The media server has LP9000's, and was fine! Frustrating!!!
The solution was to disable use of 16 byte CDB as a workaround. Please
see the following from Symantec support:
http://seer.support.veritas.com/docs/281312.htm
The doc lists AIT drives, but the solution worked with our FC LTO2 drive
environment.
FYI: We are not running NDMP, but experienced the symptom.
---
When running NetBackup 6.0, the following workaround can be applied to
disable the use of 16-byte CDB commands, by creating the following empty
file (Touch File):
<install_dir>\Volmgr\database\NO_SIXTEEN_BYTE_CDB
This will disable the use of 16-byte CDB commands. It will not be
necessary to restart NetBackup for these changes to take effect. The
file will be read during the next backup or restore operation.
Good luck,
Kent C. Eagle
Systems Engineer, MCP, MCSE
Tech Services / SMSS
-------------------------------------------
Message: 2
Date: Fri, 10 Nov 2006 02:06:57 -0800 (PST)
From: Yoseph Leleputra <leleputra at yahoo.com>
Subject: [Veritas-bu] Media write error at NDMP
To: Veritas-bu at mailman.eng.auburn.edu
Message-ID: <20061110100657.67904.qmail at web54709.mail.yahoo.com>
Content-Type: text/plain; charset="us-ascii"
Dear NBU Expert
I got problem with my backup.
My Environment using ADIC I2000 Scalar Library with 10 LTO-2 tape drives
4 drives attach to master server , 6 drives attach to netapp Storage as
NDMP drives
My problem comes after upgrading master Server Solaris patches .
Now my NDMP backup always failed with error code 84 , media write error.
What i had done to solve this problem is
Replace cleaning tape and delete Size Buffer file
but i problem still appear .
I hope there is some one who ever experiencing in problem like this to
share with me
Thanks in advance
Salam
./yoseph
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.
|
