Problem
Windows backups fail with status code 24 "Socket write failed" when backing up All_Local_Drives
Error Message
Status 24: Socket write failed
Cause
The bpbkar log shows that the client is taking too long to get through its setup stage and actually start writing backup data. This leads to a socket timeout. The excessive delay was caused by a large \Windows\Temp folder on the client. There were over 6.3 million files/folders in Temp.
Solution
Empty the \Windows\Temp folder on the client or add an exclusion for the Temp folder
Applies To
Windows Server 2003 R2 Enterprise Edition (x64)
NetBackup 6.5.4
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.