Lots of socket write failed on 8.3.0.1

Question

Hi,setup : 3 x media servers running Windows 2012 R2, backups going to disk and then stage to LTO7.Since we've upgraded from 8.1.2 to 8.3.0.1 we've experienced a lot of full backup failures during the weekend.The errors can be summarized as :&nbsp;(2074) Disk volume is down(41) network connection timed out(24) socket write failedAll seems to point to network timeouts.&nbsp; But we've never had issues with 8.1.2.&nbsp; This is the second weekend that we're taking backups with 8.3.0.1 and that these failures occur.&nbsp; Some clients were still on 8.1.2 last week.&nbsp; They are on 8.3.0.1 now, but this does apparantly not make any difference.Anyone had similar experiences?&nbsp;

marianne · Answer

pnobels&nbsp;
Are you aware of the new sizing guidance for NBU 8.3 and later?
Please see the recommended minimum processors and memory:&nbsp;Size guidance for the NetBackup master server and domain
https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146051743-146141073
&nbsp;
&nbsp;

alexis_jeldrez · Answer

The Master does not serve the role of Media Server?

pnobels · Answer

Yes, the master is also media server.

pnobels · Answer

Been doing a little bit of further investigation... Turns out i was wrong and the issue does not appear on all media servers. All above mentioned errors point to one media server, which happens to be the master.

There were some other errors on other media servers (snapshot error while reading file) but i've also seen these in the past and am not too worried about these ones.

No network bandwidth exhaustion during backup window. Nothing strange in the event logs...

alexis_jeldrez · Answer

Only for Windows Servers: https://www.veritas.com/support/en_US/article.100037977
"DO NOT configure MSDP on NetBackup (NBU) master servers..."
I learned it the hard way: MSDP generally worked fine but at random the volume went down with status 2074.
My workaround: reduce the number of duplications from disk to tape. For example, if backups to disk are done during the night, then the duplications to tape are done during the day. The real fix is migrating the MSDP resource to another Windows Server that is not a NetBackup Master Server.

Forum Discussion

Lots of socket write failed on 8.3.0.1

8 Replies

Related Content

Socket Fail Issue

socket read failed (23)

socket read failed: errno = 62 - Timer expired

What's new in Netbackup 8.3.0.1?

Re: Netbackups failing with error code 24 on linux clients

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date