Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Error 84 with SSO drives in NDMP backups

Updated: 21 May 2010 | 4 comments
VikasSharma's picture
VikasSharma
0 0 Votes
Login to vote

Hello Netbackup Gurus,

I have NBU 6.5.4 on Solaris 10 with SSO licenses to share the tape drives amoung 20+ netapp filers. The filers may have different versions of Ontap ranging from 7.0 to 7.3.

Now, the problem is that every now and then, some or the other drive paths are going down and creates error 84 and followed by frozen media. I checked this forum and one place suggested to tweak SIZE_DATA_BUFFERS. I am using default settings for this parameter (i.e. did not set it by myself).

I have also got the tape drives replaced but still the problem of 84 now and then!!!

Do you think that it may be related to SIZE_DATA_BUFFERS parameter or there may be a different reason of slowly failing all paths for SSO drives in all the Netapp filers?

Any help/ideas will be appreciated.

Thanks,
Vikas

discussion Filed Under:
, , ,

Comments

Nicolai's picture
27
Oct
2009
0 Votes 0
Login to vote
Nicolai

Not SIZE_DATA_BUFFERS problem

NDMP backups write their own format and are not affected by NUMER_DATA_BUFFERS file. Data don't even pass thru the media server.

my poor advice : - D

  • Take a look at the messages file on the Netapp filer - What does it say - Any sence key codes 
  • Ensure the SAN is 100% stable.

Assumption is the mother of all mess ups.

If this post solved you’re questions please send a gratitude by marking it as a solution.

 

Ialahmad's picture
27
Oct
2009
0 Votes 0
Login to vote
Ialahmad

I think Error 84 become  from

I think Error 84 become  from bad media tapes , also from instability in fabric connections ,, so check the stability between  Tape drive and fabric switch also between Media server and fabric switch, OR if your tape drives need to clean.

Omar Villa's picture
28
Oct
2009
0 Votes 0
Login to vote
Omar Villa

Bad tapes

on the master server go to /usr/openv/netbackup/db/errors/media here you will see a list of the tapes with more errors, froze that media and check if are the ones who came up on the bptm log, 84's are hardware issue, if is not the drive, can be the backplane, wire, port, switch,  but in the 95% of the cases is media or drives.

hope this helps.
regards.

Omar A Villa

Netbackup Expert

These are my personal views and not those of the company I work for

VikasSharma's picture
29
Oct
2009
0 Votes 0
Login to vote
VikasSharma

Update: As of now, I see error messages given as below:

Gurus,

As of now:

1) I have disabled my SAN monitoring (for precaution only)

2) Saw following logs on Netbackup master server and netapp filers.

3) I realised that I have EMC Celerra also where I may need to enable tape drive reservations. Is there any way to enable tape drive reservations on EMC? I am wondering if EMC is causing any problem?

4) Also, my filers are also variety of models (from FAS270 to 3070) and hence the HBA inside them support 1GPBS and 2GBPS in any given filer. Is it possible that this speed difference can create any problem??===============================================================================

-Vikas

On Netbackup master server:
 

Oct 28 12:39:53 nbumaster scsi: [ID 799468 kern.info] sgen0 at fp2: name w500104f000ad4df8,0, bus address 291100
Oct 28 12:39:53 nbumaster genunix: [ID 936769 kern.info] sgen0 is /pci@8,600000/lpfc@2/fp@0,0/sgen@w500104f000ad4df8,0
Oct 28 15:23:01 nbumaster tldcd[25748]: [ID 183166 daemon.error] TLD(0) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENT
Oct 28 15:23:01 nbumaster tldcd[25748]: [ID 719803 daemon.error] TLD(0) Move_medium error
Oct 28 15:23:19 nbumaster tldcd[25804]: [ID 183166 daemon.error] TLD(0) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENT
Oct 28 15:23:19 nbumaster tldcd[25804]: [ID 719803 daemon.error] TLD(0) Move_medium error
Oct 28 15:25:57 nbumaster tldcd[26043]: [ID 183166 daemon.error] TLD(0) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENT
Oct 28 15:25:57 nbumaster tldcd[26043]: [ID 719803 daemon.error] TLD(0) Move_medium error
Oct 28 15:26:15 nbumaster tldcd[26045]: [ID 183166 daemon.error] TLD(0) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENT
Oct 28 15:26:15 nbumaster tldcd[26045]: [ID 719803 daemon.error] TLD(0) Move_medium error
Oct 28 15:27:15 nbumaster ltid[488]: [ID 770066 daemon.error] Operator/EMM server has DOWN'ed drive Tape_Drive_9 (device 2)
Oct 28 15:27:16 nbumaster ltid[488]: [ID 888577 daemon.error] Operator/EMM server has DOWN'ed drive Tape_Drive_5 (device 3)
Oct 28 15:32:20 nbumaster ltid[488]: [ID 471226 daemon.error] Operator/EMM server has DOWN'ed drive Tape_Drive_15 (device 12)

On NetApp filers:
==============================================================================
Filer name : netappfiler1

Sun Oct  4 23:42:14 PDT [netappfiler1: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-12.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Mon Oct  5 06:08:13 PDT [netappfiler1: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-12.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Fri Oct 16 18:09:17 PDT [netappfiler1: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-10.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Sat Oct 24 22:48:24 PDT [netappfiler1: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-24.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Sun Oct 25 18:31:34 PDT [netappfiler1: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-20.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).

==============================================================================
Filer name : netappfiler2

Sat Oct 17 13:47:47 PDT [netappfiler2: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-24.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Sat Oct 24 10:43:43 PDT [netappfiler2: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-12.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Sun Oct 25 16:54:54 PDT [netappfiler2: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-24.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).
Sun Oct 25 21:54:04 PDT [netappfiler2: tape.cmd.chkCondErr:error]: Tape device SAN-SWITCH1:0-24.126: Check Condition: SCSI Op Code Write(06)) (CDB 0x0a: 0x00fc00 bytes): hard error - Write error (0x3 - 0xc 0x0 0x0).

==============================================================================
 

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
259,078