Backup fails with socket read failed
Hi All,
Netbackup 7.1.0.3 , Windows server 2008 standard R2, client - windows 2000
ONLY FULL Backup is failed with socket read failed.
22/01/2016 23:30:38 - begin writing
22/01/2016 23:30:39 - Info bptm(pid=2928) start
22/01/2016 23:32:10 - Error bpbrm(pid=984) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
22/01/2016 23:32:40 - Error bpbrm(pid=984) could not send server status message
22/01/2016 23:33:06 - Error bpbrm(pid=984) cannot send mail to netbackup@acco.com
22/01/2016 23:33:08 - end writing; write time: 00:02:30
file read failed(13)
Increase client read out time 1800 and communication buffer size to 128 but no use.
D:\>bptestbpcd -client EUAVDC02 -verbose
0 1 2
10.1.10.1:589 -> 172.16.171.239:13782
10.1.10.1:13724 <- 172.16.171.239:689
PEER_NAME = euaylnbu01.accoeu.local
HOST_NAME = euavdc02
CLIENT_NAME = euavdc02
VERSION = 0x06500000
PLATFORM = nt
PATCH_VERSION =
SERVER_PATCH_VERSION =
MASTER_SERVER = Euaylnbu01
EMM_SERVER = Euaylnbu01
10.1.10.1:13724 <- 172.16.171.239:759
D:\>bpclntcmd -hn EUAVDC02
host EUAVDC02: euavdc02.europe.gbcglobal.local at 172.16.171.239
aliases: euavdc02.europe.gbcglobal.local EUAVDC02 172.16.171.239
D:\>bpclntcmd -ip 172.16.171.239
host 172.16.171.239: 172.16.171.239 at 172.16.171.239
aliases: 172.16.171.239
As we already missed 2 weeks full backup. Kindly assist me.
client - windows 2000
Windows 2000? Really??
With NBU 6.5 client by the looks of it?Wi0ndows 2000 TCP stack had many shortcomings and there are no longer any patches/updates available from Microsoft.
Windows 2000 and any pre-7.0 version of NBU are no longer supported by Microsoft or Veritas.
No support from OS vendor or Veritas means that you are under no obligation to backup this client.
Get server owners to backup their data with Windows backup on this host to a network share on a supported client or server.
You can then backup this location on the supported client/server using MS-Windows policy.
