03-29-2021 12:22 AM
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 220.127.116.11 we've experienced a lot of full backup failures during the weekend.
The errors can be summarized as :
(2074) Disk volume is down
(41) network connection timed out
(24) socket write failed
All seems to point to network timeouts. But we've never had issues with 8.1.2. This is the second weekend that we're taking backups with 18.104.22.168 and that these failures occur. Some clients were still on 8.1.2 last week. They are on 22.214.171.124 now, but this does apparantly not make any difference.
Anyone had similar experiences?
03-29-2021 11:17 AM
The Master does not serve the role of Media Server?
03-29-2021 11:00 PM
Yes, the master is also media server.
03-30-2021 04:59 AM
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...
03-30-2021 12:25 PM - edited 03-30-2021 12:26 PM
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.
03-30-2021 01:16 PM
It may be unrelated, but I experience 2074s on OST when a media server is unable to query the storage the disk pools are attached to. The problem is, the storage unit is reported as down for all media servers until the culprit re-establishes connectivity to the storage servers. Could be food for thought though.
03-30-2021 11:37 PM
Are you aware of the new sizing guidance for NBU 8.3 and later?
Please see the recommended minimum processors and memory:
Size guidance for the NetBackup master server and domain
03-31-2021 12:27 AM
We do not use MSDP.
I've seen the requirements. Master server only has 64 GByte of RAM in our case. But we only have 3 media servers. And i haven't seen memory or cpu shortage.
03-31-2021 04:49 AM
@pnobels please check usage of your sockets on the Windows Master server. Use netstat utility to figure out if there are more than usual or normal usage of sockets from or to the master. You may have to work with your Windows admin to find more on this.