cancel
Showing results for 
Search instead for 
Did you mean: 

ERR - Cannot write TIR data to media, NDMP return code 20

TimWillingham
Level 5

So, did my backup complete successfully or not?

 

03/16/2015 14:55:08 - Info ndmpagent (pid=23873) 51545000 entries sent to bpdbm
03/16/2015 14:55:10 - Info ndmpagent (pid=23873) gaxgpns1pr08: Filetransfer: Transferred 2570489214464 bytes in 25675.083 seconds throughput of 97769.629 KB/s
03/16/2015 14:55:10 - Info ndmpagent (pid=23873) gaxgpns1pr08: CPU  user=5923.456872  sys=29030.848957
03/16/2015 14:55:10 - Info ndmpagent (pid=23873) gaxgpns1pr08: maxrss=282540  in=326478744  out=45  vol=298808019  inv=187285667
03/16/2015 14:55:10 - Info ndmpagent (pid=23873) gaxgpns1pr08: . Objects (scanned/included):. ----------------------------. Regular files:  (25673858/25673858). Sparse files:  (0/0). Directories:  (100779/100779). ADS Entries:  (0/0). ADS Containers:  (0/0). Soft Links:  (0/0). Hard Links:  (0/0). Block Device:  (0/0). Char Device:  (0/0). FIFO:   (0/0). Socket:   (0/0). Whiteout:  (0/0). Unknown:  (0/0)
03/16/2015 14:55:10 - Info ndmpagent (pid=23873) gaxgpns1pr08: . Dir Depth (count). ----------------------------. Total Dirs:  100779. Max Depth:  5.. File Size (count). ----------------------------. == 0   120. <= 8k   8240633. <= 64k   8845246. <= 1M   8425611. <= 20M   160640. <= 100M   1532. <= 1G   72.  > 1G   4. -------------------------. Total Files:  25673858. Total Bytes:  2511457801931. Max Size:  6787784704. Mean Size:  97821
03/16/2015 14:55:10 - Info ndmpagent (pid=23873) gaxgpns1pr08: . File History. ----------------------------. Num FH_HIST_FILE messages:  0. Num FH_HIST_DIR  messages:  25976194. Num FH_HIST_NODE messages:  25774637
03/16/2015 14:55:11 - Info ndmpagent (pid=23873) NDMP backup successfully completed, path = /ifs/xgp/GAXGPFD09/F/Groups/SCS_Documentum_Prod/GLSLEG_PROD
03/16/2015 14:55:12 - Info ndmpagent (pid=23873) 51549275 entries sent to bpdbm
03/16/2015 15:00:04 - Error bptm (pid=23874) ERR - Cannot write TIR data to media, NDMP return code 20.
03/16/2015 15:00:12 - Info bptm (pid=23874) EXITING with status 84 <----------
03/16/2015 15:00:12 - Info ndmpagent (pid=0) done. status: 84: media write error
03/16/2015 15:00:12 - end writing; write time: 1:04:06
03/16/2015 15:10:13 - Info bpbrm (pid=6143) gaxgpns1pr08 is the host to backup data from
03/16/2015 15:10:13 - Info bpbrm (pid=6143) reading file list for client
03/16/2015 15:10:13 - Info bpbrm (pid=6143) starting ndmpagent on client
03/16/2015 15:10:13 - Info ndmpagent (pid=6153) Backup started
03/16/2015 15:10:13 - Info bpbrm (pid=6143) bptm pid: 6154
media write error  (84)

1 ACCEPTED SOLUTION

Accepted Solutions

CRZ
Level 6
Employee Accredited Certified

It did not.

Do you have SIZE_DATA_BUFFERS_NDMP set?  To what?

Do you have NDMP_PROGRESS_TIMEOUT set?  (It DOES look like almost exactly 15 minutes passes from your log excerpt...could it be 900?)

Anything else interesting in /usr/openv/netbackup/db/config/ndmp.cfg (does it exist)?

This looks like an enormous backup.

View solution in original post

4 REPLIES 4

CRZ
Level 6
Employee Accredited Certified

It did not.

Do you have SIZE_DATA_BUFFERS_NDMP set?  To what?

Do you have NDMP_PROGRESS_TIMEOUT set?  (It DOES look like almost exactly 15 minutes passes from your log excerpt...could it be 900?)

Anything else interesting in /usr/openv/netbackup/db/config/ndmp.cfg (does it exist)?

This looks like an enormous backup.

Marianne
Level 6
Partner    VIP    Accredited Certified
No, the status 84 right at the end means that the backup has failed. NBU has discarded all catalog info for this backup.

TimWillingham
Level 5

SIZE_DATA_BUFFERS_NDMP was 131072, so I increased it to 196608 and the job completed successfully.  These 84 errors are pretty sporadic, so I'm not convinced that solved the problem.  I have another environment nearly identical that gets 84s with it set to 262144.

I do not have the touch file NDMP_PROGRESS_TIMEOUT or an ndmp.cfg file.

And yes, we do have some enormous backups.  We have been breaking them up into smaller chunks, but there are limits to what we can do.

Thanks for the response!

TimWillingham
Level 5

That's what I thought, just wanted to confirm!

Thanks!!