Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3266

September 7th, 2011 18:00

NDMP backups to IBM ULTRIUM-TD5 drive

Trying to perform NDMP backups to a fiber connected IBM ULTRIUM-TD5 drive without much sucess.  The Celerra sees the drive and library and netbackup can sucessfully communicate to the Celerra.  However running a backup job generates the following error:

2011-09-07 19:45:53: DRIVERS: 6: FCDMTL 2 [9.0.2] Status buffer overrun: xid 19d, msg 60390a0, address id 620813
2011-09-07 19:45:54: DRIVERS: 6: FCDMTL 2 [9.0.2] Status buffer overrun: xid 1b9, msg 60397c0, address id 620813
2011-09-07 19:45:54: CAM: 3: I/O Error: c96t0l0: CamStatus 0x84 ScsiStatus 0x02 Sense 0x07/0x5a/0x02
2011-09-07 19:45:54: CAM: 3: camFlags 0x81 Addr 0x26db6000 Len 0x400 Resid 0x0
2011-09-07 19:45:54: CAM: 3: cdb: 0a 00 00 04 00 00 00 00 00 00 00 00
   | SCSI ERR ON #9600    camstat 0x84  bstat InvalidOperation
   | scsi stat.skey.ascq 0x02.07.5a02  Check condition
   |                     skey  [   ]   Write protect
   |____________________ ascq          Operator selected write protect
2011-09-07 19:45:54: NDMP: 3: Thread ndmp013 DartTapeInterface: write error
2011-09-07 19:45:59: CAM: 3: I/O Error: c96t0l0: CamStatus 0x84 ScsiStatus 0x02 Sense 0x07/0x5a/0x02
2011-09-07 19:45:59: CAM: 3: camFlags 0xc1 Addr 0xffffffff Len 0x0 Resid 0x0
2011-09-07 19:45:59: CAM: 3: cdb: 10 00 00 00 01 00 00 00 00 00 00 00
   | SCSI ERR ON #9600    camstat 0x84  bstat InvalidOperation
   | scsi stat.skey.ascq 0x02.07.5a02  Check condition
   |                     skey  [   ]   Write protect
   |____________________ ascq          Operator selected write protect

Basically from the netbackup side you see the tape mount and it looks like the job is about to write data but then fails immediately.

Any suggestions?

Thanks,

David-

5 Posts

November 3rd, 2011 14:00

OK,  our issue has finally been identified and resolved with the help of our first level Symantec Netbackup support vendor.

This is how is was desribed to me:

The other issue that may be causing it is that the LTO 5 drives now support Append-Only Mode from http://www.symantec.com/docs/TECH143890.

SCSI Stream Commands (SSC-4) has introduced a new data protection feature for tape drives called "Append Only Mode".

This feature causes the drive to prevent the overwrite of data on a cartridge unless the writing application performs a pre-authorization for the overwrite.

Pre-authorization for overwrite is a done with a new SCSI command (Allow Overwrite) that informs the drive that the data block at the current location is going to be overwritten.

Any attempt to overwrite a data block without pre-authorization returns a write protect error.

IBM LTO-5 drives support this feature (even with LTO-4 media).

Once set, LTO-5 drives remain in append mode until power cycled.”

---

So apparently the Celerra isn't sending the proper commands to Pre-Authorize the write?  Hince the write-protect error even when the tape isn't physically write protected.

The work around was to drop the following file into our Netbackup config:

\Netbackup\db\config\DISABLE_APPEND_MODE

This causes Netbackup to disable the Append Only Mode.  And now Celerra can write directly to the LTO5 drives via NDMP over the storage network.

Regards,

David-

9 Legend

 • 

20.4K Posts

September 7th, 2011 20:00

this is not related , is it ?

emc231989

9 Legend

 • 

20.4K Posts

September 8th, 2011 11:00

silly question but media is not write protected ?

5 Posts

September 8th, 2011 11:00

That doc talks about v6.5 of netbackup, we are currently running version 7.1

And Celerra dart 5.6.51.3

4 Operator

 • 

8.6K Posts

September 14th, 2011 07:00

Did you solve it ?

4 Operator

 • 

8.6K Posts

September 14th, 2011 08:00

I would suggest to try to narrow down with server_archive without NDMP and TSM

5 Posts

September 14th, 2011 08:00

Nope,  issue still exists.   I thought we had found the solution with a firmware upgrade on the drives as the release notes had several items talking about write protect reporing issues.  But that did not work.

We have replaced fiber cables, rezoned the drives, tried aux port on other data mover, restarted data movers, adjusted the scsiReserve setting.  All attempts end up with the same error message.

Any additional details on the v4OldTapeCompatible setting?   Documentation only mentions the setting with regards to Arcserve

Have cases open with both EMC and Symantec.

EMC sent tech onsite to validate physical cabling.  Last I checked the ticket was being passed around.  Waiting for the next step, as I'm out of ideals.

Here's current NDMP settings:

[nasadmin@tron_hou ~]$ server_param server_2 -facility NDMP -list

server_2 :

param_name                       facility  default     current   configured

maxProtocolVersion                  NDMP          4          4

snapsure                            NDMP          0          0

dialect                             NDMP

scsiReserve                         NDMP          1          0          0

includeCkptFs                       NDMP          1          1

md5                                 NDMP          1          1          1

tapeSilveringStr                    NDMP         ts         ts

convDialect                         NDMP     8859-1     8859-1

bufsz                               NDMP        128        128

v4OldTapeCompatible                 NDMP          1          1

forceRecursiveForNonDAR             NDMP          0          0

excludeSvtlFs                       NDMP          1          1

snapTimeout                         NDMP          5          5

1 Rookie

 • 

3 Posts

September 30th, 2011 02:00

David, I see that this is a fairly recent note - has it been solved?

I'm seeing the same symptoms as you describe, fibre connected IBM ULTRIUM TD-5 drive, NetBackup v7.1, DART 5.6.51.320 and the same error ("Write Protect") in the log. Have you found a solution as yet?  I've not yet raised a ticket but will do so if you've not yet had a resolution.

5 Posts

September 30th, 2011 06:00

Nope,  issue has not yet been resolved.  EMC support has blown us off claiming it's an implementation issue versus a tech support issue because I opened my mouth and told them it worked fine with our LTO4 drives.  Our service request number is 43002544 but I'm not sure I would reference that ticket given the lack of help we've received.

I'm currently working the issue from the netbackup route with our EMC & Netbackup vendor.  Our vendor provides us with first level netbackup support.  They are also the ones who sold us the LTO5 drives just in case it is an "implementation issue."

We are currently doing NDMP backups via the network to get around this issue.  However going this route the performance is less than desired.  But at this point slow backups are better than no backups.

1 Rookie

 • 

3 Posts

September 30th, 2011 06:00

Thanks, David.  It sounds like we're in exactly the same boat with respect to the backups.  I too have resorted to backing up via the network but this is only a workaround, not a solution.

October 3rd, 2011 20:00

I was reviewing the NAS NDMP Interoperability Matrix and "technically" Netbackup v7.1 is not (yet?) supported as you'll note only v7.0 is mentioned.  Just as a quick note, the document is meant to be read as v7.0 and not v7.x as this PDF is explicit about the major and minor release numbers of the backup software.  Also, when qualifying your environment, you'll also want to verify that the tape drive itself is listed; and therefore, supported.  The PDF currently available is the September 2011 release, and we should be expecting the October 2011 results shortly. 

With that said, just because it is not listed says nothing about:

1) whether it was tested and issues were identified

2) or, simply it hasn't been tested yet

Of course, I'm not suggesting that it won't work with v7.1 of NetBackup.  The fact that 2 people with very similar configurations are reproducing the same thing suggests there might be a compatibility issue and that it simply won't work with your (or any currently released) array code level -or- there are specific configuration settings required which would be documented via footnotes if it is listed in a future release of the PDF.

dmassey,

You did mention that it "worked fine with our LTO4 drives".  I'm just curious if maybe when running with the LTO4 drives, you might have been running v7.0 of NetBackup?  Then when you went to LTO5 you just happened to also upgrade to v7.1?  Just a thought.

9 Legend

 • 

20.4K Posts

November 3rd, 2011 14:00

Thank you for sharing David ..very helpful for other folks.

No Events found!

Top