cancel
Showing results for 
Search instead for 
Did you mean: 

NDMP Failure - file read failed(13)

mansoor_sheik
Level 6
Certified

Hi Team,

NDMP failure.

3/3/2016 9:39:05 PM - Error bpbrm(pid=41628) db_FLISTsend failed: file read failed (13)       
3/3/2016 9:39:06 PM - Error ndmpagent(pid=32748) terminated by parent process         
3/3/2016 9:39:06 PM - Info ndmpagent(pid=0) done            
3/3/2016 9:39:06 PM - Error ndmpagent(pid=32748) NDMP backup failed, path = /root_vdm_1/HongKong1       
3/3/2016 9:39:35 PM - Error ndmpagent(pid=32748) SNG2NAS02: Medium error          
3/3/2016 9:39:35 PM - Warning ndmpagent(pid=32748) SNG2NAS02: Write failed on archive volume 1      
3/3/2016 9:39:35 PM - Info ndmpagent(pid=32748) SNG2NAS02: server_archive: emctar vol 1, 437612 files, 0 bytes read, 213823913984 bytes written
3/3/2016 9:39:35 PM - Error ndmpagent(pid=32748) SNG2NAS02: Backup is aborted.         
3/3/2016 9:39:41 PM - Info ndmpagent(pid=0) done. status: 13: file read failed       

I refered the below tech note.

https://www.veritas.com/community/forums/ndmp-backup-failure-1

I have enabled the ndmpagent, bptm and bpprm logs. How to verify the logs in which file the backup failed with error.

2 ACCEPTED SOLUTIONS

Accepted Solutions

mnolan
Level 6
Employee Accredited Certified

With this you can see that you would get more info from BPDBM on the master server.

Check that the EMC device is using snapsure as without it inodes could get reused which would case the master to complain.

 

https://www.veritas.com/support/en_US/article.000082710

View solution in original post

mansoor_sheik
Level 6
Certified

Hi All, Sorry for the delay.

@Marriane : Sorry for the delay.

We opened a case with Symantec and they suggested to include 

SET SNAPSURE=YES in backup selection.

Now the backups are completed successfully.

 

View solution in original post

9 REPLIES 9

Will_Restore
Level 6

Open an SSH session to the EMC NDMP device.
Run the command nas_storage -c -a.


If the result of the command returns a storage device error for example error 5017: storage health check failed, contact EMC support.

 

https://www.veritas.com/support/en_US/article.TECH209515

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
I would start with ndmpagent log to see ndmp errors. bptm (at logging level 3) will show until when data was received. bpbrm (at logging level 3) will show until when metadata was received and if backup was terminated because of timeout. Can you show us a couple of lines before the 3/3/2016 9:39:05 PM timestamp?

mansoor_sheik
Level 6
Certified

Hi Marianne,

I have enabled the log after witnessing the error in detailed logs.

3/4/2016 10:36:28 PM - Error bpbrm(pid=26864) db_FLISTsend failed: file read failed (13)       
3/4/2016 10:36:28 PM - Error ndmpagent(pid=28288) terminated by parent process         
3/4/2016 10:36:28 PM - Info ndmpagent(pid=0) done            
3/4/2016 10:36:28 PM - Error ndmpagent(pid=28288) NDMP backup failed, path = /root_vdm_1/HongKong1       
3/4/2016 10:36:58 PM - Error ndmpagent(pid=28288) SNG2NAS02: Medium error          
3/4/2016 10:36:59 PM - Warning ndmpagent(pid=28288) SNG2NAS02: Write failed on archive volume 1      
3/4/2016 10:36:59 PM - Info ndmpagent(pid=28288) SNG2NAS02: server_archive: emctar vol 1, 332560 files, 0 bytes read, 186872496128 bytes written
3/4/2016 10:36:59 PM - Error ndmpagent(pid=28288) SNG2NAS02: Backup is aborted.         
3/4/2016 10:37:06 PM - Info ndmpagent(pid=0) done.  status: 13: file read failed       
3/4/2016 10:37:06 PM - end writing; write time: 3:38:27
file read failed(13)

getting below logs for ndmpagent log. I am unable to find time stamp.

- 228654 0 228654 0 346406 0 0 6 33188 32770 32775 228654 1430302194 1242356934 1364804255 0000002c240ef25e000000000003289d 207005,32:ConnectionToBrm::SendFileHistory,5
0,51216,134,134,694063,1457110366129,63900,60800,0:,145:FH TO BRM: Ino - 220318 0 220318 0 346407 0 0 6 33188 32770 32775 220318 1430302194 1242356950 1364804255 0000002c241275ad000000000003289e 207006,32:ConnectionToBrm::SendFileHistory,5
0,51216,134,134,694064,1457110366129,63900,60800,0:,145:FH TO BRM: Ino - 253086 0 253086 0 346408 0 0 6 33188 32770 32775 253086 1430302194 1242356964 1364804255 0000002c2415d8fc000000000003289f 207007,32:ConnectionToBrm::SendFileHistory,5
0,51216,134,134,694065,1457110366129,63900,60800,0:,145:FH TO BRM: Ino - 265952 0 265952 0 346409 0 0 6 33188 32770 32775 265952 1430302194 1242356976 1364804255 0000002c2419bc4b00000000000328a0 207008,32:ConnectionToBrm::SendFileHistory,5

 

 


 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
You need to use vxlogview to read ndmpagent. I am not close to a system to look up command usage. Please do so in Commands manual (or maybe Google). You can specify start and end times with vxlogview to narrow down the time span.

watsons
Level 6

vxlogview -p nb -o 134 -d all -b "3/4/2016 10:30:00 PM"

This gives you the readable (date & time) of ndmpagent logs (OID=134) from that 3/4/2016 10:30PM onwards, you can give it an end range by -e , if you know when the job ends or fails.

Btw, your error looks more like a tape media issue:

3/4/2016 10:36:28 PM - Error ndmpagent(pid=28288) NDMP backup failed, path = /root_vdm_1/HongKong1       
3/4/2016 10:36:58 PM - Error ndmpagent(pid=28288) SNG2NAS02: Medium error  

I would use a different tape or tape drive to test the backup again.

Will_Restore
Level 6

Have you checked the EMC hardware logs per my post above?

 

mnolan
Level 6
Employee Accredited Certified

With this you can see that you would get more info from BPDBM on the master server.

Check that the EMC device is using snapsure as without it inodes could get reused which would case the master to complain.

 

https://www.veritas.com/support/en_US/article.000082710

View solution in original post

mansoor_sheik
Level 6
Certified

Hi All, Sorry for the delay.

@Marriane : Sorry for the delay.

We opened a case with Symantec and they suggested to include 

SET SNAPSURE=YES in backup selection.

Now the backups are completed successfully.

 

View solution in original post

Genericus
Level 6
   VIP   

mnolan for the win!

 

NetBackup 8.3.0.1 on Solaris 11, writing to Data Domain 9800 6.2.1.0
duplicating via SLP to LTO5 in SL8500 via ACSLS