Hi,
I have an issue with a server that fails to backup the C: drive with an error Status 24: Socket Write Error. Yet the child jobs for the D:, E: & F: drives all work without any problems.
When i start a backup job it looks like its going to start okay. Looking in the detailed status of the job it gets down to where it says "begin writing" and starts to count up the files being written then we get this error;
Critical bpbrm(pid=) from client CLIENT1: FTL - socket write failed
NOTE: I cannot post any log files or outputs on here as these servers operate in our secure cloud environment. So posting logs/hostnames/IP is not allowed. Sorry.
This is a Windows 2012 R2 Virtual Machine and it was built at the same time as another server of the same design which works. We are running 7.5.0.6 client and 7.6.0.4 on the media and master servers.
I have read all sorts of posts about possible network issues or client timeouts but since this server with the problem is sat on the same ESX host as the second server built at the same time (which works perfectly) i cannot see networks this being the issue here.
So i was wondering if anyone might have any ideas where to start looking?