Master server : LInux SLES11, NB 22.214.171.124
Client: Linux 2.6.16, NB 6.5.6
on the client run file system and oracle backups too. The file system backup fails with error 13. What I found in the bpbkar log:
13:28:50.718  <16> flush_archive(): ERR - Cannot write to STDOUT. Errno = 104: Connection reset by peer
13:28:50.737  <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 24: socket write failed
Strange that the backuped data size is always multiple of the maximum fragment size.
What I checked already:
But it didn't help.
Thank you in advance.
Solved! Go to Solution.
10/18/2012 04:27:43 - requesting resource StU_Group_VTL_7d_C2_B
10/18/2012 04:27:43 - requesting resource lp34nb9master.w34.NBU_CLIENT.MAXJOBS.lt34d03b.w34
10/18/2012 04:27:43 - requesting resource lp34nb9master.w34.NBU_POLICY.MAXJOBS.W34_UX_APP_SL_B4_PIP
10/18/2012 04:27:43 - granted resource lp34nb9master.w34.NBU_CLIENT.MAXJOBS.lt34d03b.w34
10/18/2012 04:27:43 - granted resource lp34nb9master.w34.NBU_POLICY.MAXJOBS.W34_UX_APP_SL_B4_PIP
10/18/2012 04:27:43 - granted resource MediaID=@aaacf;Path=/backup/VTL/na34001v4/7d_c2/lp34nb90;MediaServer=lp34nb90
10/18/2012 04:27:43 - granted resource lp34nb90_na34001_vol3_v2_7d_c2
10/18/2012 04:27:43 - started process bpbrm (pid=69944)
10/18/2012 04:27:44 - connecting
10/18/2012 04:27:44 - connected; connect time: 0:00:00
10/18/2012 04:27:57 - begin writing
10/18/2012 05:28:11 - end writing; write time: 1:00:14
file read failed (13)
It tired writing for 1 hour and ended with that error, seems to be it was stuck and then lost the connection.
1> Detailed status and bpbkar are not of the same time?
2> Post the complete bpbkar,bptm and bpbrm?
3> The file and oracle runs at the same time?
Are you sure you have done everything in the TN you mentioned
Better to upgrade the client to the same version as of Master server
It could be that the backup is hitting a barrier somewhere and exceeding the timeout.
If backing up through a firewall make sure that the firewall keeep alive timout is extended - you could also increae the cleint read timeout on the Media Servers involved, but it is more likely that the client is hitting something during the backup that is almost hanging it - a locked or corrupt file?
It may be worth increasing the logging levels for bpbkar on the client and bpbrm / bptm on the media server to see if you can pin down where it gets to when it stops responding and casues the timeout.
Are you Oracle databases excluded from the file system backups? (that would cause such a hand as it tries to get a hook on them - each locked file can make it hang for several minutes so it doesn't take many before the 1 hour has been reached and the timeout occurs)
Hope this helps
Could you please post the detailed status from the activity monitor for the same as well. Logs are too big to track without that. Put the complete information from the detailed status as well of the same time for which logs are attached.
Do you have millions of files in this folder to backup?? The backup may success some time taking hours to complete but most of the time it will fail with this error. You have mentioned it as oracle system so I may be wrong but check the number of file just in case if that could be the issue.