Forum Discussion
Hamza_H
5 years agoModerator
You may want to check this : https://www.veritas.com/support/en_US/article.100003560
You said :
*I increased the client read timeouts (up to 1800) on the master server and increased the client read/file browse timeouts on the client to 7200 each. After doing this, the full backup timeout still occurred after about 45 minutes of the job running.*
My questions are : is the master server also the media server?
You should change ‘client read timeout’ on the media server and set it to 3600 and the same paramater on the client with the same value (no need to change file browse, you can change it back to 300)
After doing this, do another backup.
Is there a FW between the master/media and the client? If yes you should check with your network team to check logs for any drop connections.
Your backup full is failing because the amount of data to send is much more than the incremental. So if there is any delay on the client’s side.. the media is waiting to the Timeout that you set but this change wouldn’t mean anything if the FW had already dropped the connection..
My suggestions are :
Activate the accelerator and run a full backup.
If it fails, then try another test with deduplication on the client side (but the client must have enough ressources to handle the deduplication).
If this works then there is a problem on your connection and surely on the FW..
And also (I know this reply is a little bit long, but all network/connection status codes especially 13,14,41 are tricky and a lot of factors can be the root cause) so also you may want to check on your switches/routers/clients NIC IF they are on full duplex and not half duplex..
Good luck
You said :
*I increased the client read timeouts (up to 1800) on the master server and increased the client read/file browse timeouts on the client to 7200 each. After doing this, the full backup timeout still occurred after about 45 minutes of the job running.*
My questions are : is the master server also the media server?
You should change ‘client read timeout’ on the media server and set it to 3600 and the same paramater on the client with the same value (no need to change file browse, you can change it back to 300)
After doing this, do another backup.
Is there a FW between the master/media and the client? If yes you should check with your network team to check logs for any drop connections.
Your backup full is failing because the amount of data to send is much more than the incremental. So if there is any delay on the client’s side.. the media is waiting to the Timeout that you set but this change wouldn’t mean anything if the FW had already dropped the connection..
My suggestions are :
Activate the accelerator and run a full backup.
If it fails, then try another test with deduplication on the client side (but the client must have enough ressources to handle the deduplication).
If this works then there is a problem on your connection and surely on the FW..
And also (I know this reply is a little bit long, but all network/connection status codes especially 13,14,41 are tricky and a lot of factors can be the root cause) so also you may want to check on your switches/routers/clients NIC IF they are on full duplex and not half duplex..
Good luck
- Hamza_H5 years agoModerator
Hello dcbone ,
just wondering if you were able to resolve this ? if yes could you please share the solution or mark the post that helped you out.
Thanks :)
BR.
- dcbone4 years agoLevel 3
It resolved itself, however unfortunately there was no solution. It just stopped happening.
Related Content
- 12 years ago
- 11 years ago