Forum Discussion
Setting CLIENT_READ_TIMEOUT lets netbackup be a little more patience with client slow responding clients. Especially incremental backup are normal exposed to falling for the CLIENT_READ_TIMEOUT. Its the selection process if a file is due for incremental backup in directory with thousands files that cause this. Especially Oracle audit or alert directories.
Try to double the value - else you have have to do bpbkar debugging to see which directories causes the timeout ?
Any firewall between master/media and clients ?
- T_N7 years agoLevel 6
I have same issue ( 2 media server/client (a & b)), even I changedCLIENT_READ_TIMEOUT = 3600 on media server, master & clients, I am not able to backup them with datadomain disk pool, but when I run backup client a with STU tape it self, it worked well.
- Marianne7 years agoLevel 6T_N,
It is never a good idea to tag onto an old post. You will notice that the original poster stopped responding to questions.
Best to start a new discussion and give us all relevant info of your environment, like master, media, client OS and NBU version, if problem is seen with specific client or type of backup, if there are any firewalls in the picture, if your network team tried to investigate possible network issues between media server and DD, etc.
Please post all text in job details and tell us if you have enabled logging for all the processes that can be seen in job details.- T_N7 years agoLevel 6
Thank you Marianne
Related Content
- 9 months ago
- 10 years ago