NDMP backup failure
- 10 years ago
You will need logs on the media server to try and find the reason for the failure.
We can see that the backup had already written quite a bit of data when it seemed to get hung on an image thumbnail!
7/15/2015 2:56:28 PM - begin writing
7/15/2015 8:16:18 PM - Error bpbrm(pid=27544) db_FLISTsend failed: file read failed (13)
7/15/2015 8:16:18 PM - Error ndmpagent(pid=25552) write socket err 10054 (An existing connection was forcibly closed by the remote host.
.)
7/15/2015 8:16:18 PM - Error ndmpagent(pid=25552) FH send to BRM failed - Ddi - 0 0 0 0 4701543 0 0 9 13680367 Thumbs.db
7/15/2015 8:16:18 PM - Error ndmpagent(pid=25552) NDMP backup failed, path = /root_vdm_1/FS_XXXXXXXX_01/MPFS_XXXXXXXX_01/FS01_QTR010Logs needed:
ndmpagent
bpbrm and bptm (at logging level of 3 minimum)nbdmpagent will hopefully give more info about the file/folder where backup is getting stuck.
bptm will tell us up to when data was received from the filer.
bpbrm will show when last metadata was received and the failure was actually a timeout because no data was received from the filer.
In the meantime, change Client Read Timeout on the media server to 1800 (30 minutes).