07-31-2017 04:01 AM
I added a new client to an existing MS-Windows backup policy.
I have the netbackup agent installed on the client, the backups are failing error 112.
(112) no files specified in the file list
bptestbpcd if failing for this client from the master server.
kindly need your help in understanding the issue.
Solved! Go to Solution.
08-01-2017 09:14 AM
08-16-2017 07:32 AM
,FROM 0.0.0.0 TO newhost 10.x.x.x bpcd VIA pbx status: FAILED, (42) CONNECT_REFUSED; system: (110) Connection timed out; FROM 0.0.0.0 TO newhost 10.x.x.x bpcd VIA vnetd status: FAILED, (42) CONNECT_REFUSED; system: (110) Connection timed out; FROM 0.0.0.0 TO newhost 10.x.x.x bpcd
it points to windows firewall services, please check and disable them from start>run>services.msc.
ANd try to create inbound/outbound rules for PBX, Vnetd, bpcd under Server Manger> Configuration> windows Firewal & advanced Security> inbound/oubound rules > create new rule.
It should be opened vice versa.
except it also make sure name resolution does not have any issue.
08-17-2017 03:47 AM
Hi sorry for the delay in response.
At client side we had to open the respective ports :
07-31-2017 04:44 AM
What did you enter in Backup Selection of the policy?
Please show the policy config.
From cmd (in ...\netbackup\bin\admincmd):
bppllist <policy-name> -U
Please copy the text output and post here.
07-31-2017 04:50 AM
About bptestbpcd failing - please show us the output?
(Include -verbose and -debug options)
Have you checked that Windows Firewall is disabled on the client?
07-31-2017 08:04 AM - edited 07-31-2017 08:06 AM
newhost is the client added to policy WinServers_Policy_DC2
[root@master admincmd]# bppllist WinServers_Policy_DC2-U
------------------------------------------------------------
Policy Name: WinServers_Policy_DC2
Policy Type: MS-Windows
Active: yes
Effective date: 06/25/2012 12:51:31
Backup network drvs: no
Collect TIR info: yes
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: slp_ndmp_dc2
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: yes
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Use Accelerator: yes
Optimized Backup: no
HW/OS/Client: Windows-x64 Windows2008 host1
Windows-x64 Windows2008 host2
Windows-x64 Windows2008 host3
Windows-x64 Windows2008 host4
Windows-x64 Windows2008 newhost
Include: ALL_LOCAL_DRIVES
Schedule: MonthlyBackup
Type: Full Backup
Frequency: every 26 days
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Maximum MPX: 1
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: slp_winservers_dc2_monthly
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Daily Windows:
Saturday 20:00:00 --> Sunday 08:00:00
Schedule: WeeklyBackup
Type: Cumulative Incremental Backup
Frequency: every 4 days
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
Synthetic: 0
PFI Recovery: 0
Maximum MPX: 1
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: slp_winservers_dc2_weekly
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Daily Windows:
Saturday 20:00:00 --> Sunday 08:00:00
Schedule: DailyBackup
Type: Differential Incremental Backup
Frequency: every 12 hours
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 1
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: slp_winservers_dc2_daily
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Daily Windows:
Sunday 20:00:00 --> Monday 08:00:00
Monday 20:00:00 --> Tuesday 08:00:00
Tuesday 20:00:00 --> Wednesday 08:00:00
Wednesday 20:00:00 --> Thursday 08:00:00
Thursday 20:00:00 --> Friday 08:00:00
Friday 20:00:00 --> Saturday 08:00:00
[root@master admincmd]$ ./bptestbpcd -client newhost -verbose -debug
12:13:01.533 [30127] <2> bptestbpcd: VERBOSE = 2
12:13:01.533 [30127] <2> read_client: dname=OAA_0, offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:13:01.533 [30127] <2> read_client: dname=COA_0, offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:13:01.533 [30127] <2> read_client: dname=., offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:13:01.533 [30127] <2> read_client: dname=CO_0, offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:13:01.533 [30127] <2> read_client: dname=OA_0, offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:13:01.533 [30127] <2> read_client: dname=host_info, offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:13:01.533 [30127] <2> read_client: dname=.., offline=0, online_at=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
12:16:10.546 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:16:22.546 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:16:34.548 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:19:21.552 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:19:33.553 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:19:46.556 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:22:33.568 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:22:47.574 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
12:23:02.574 [30127] <8> async_connect: [vnet_connect.c:1846] getsockopt SO_ERROR returned 110 0x6e
,
,FROM 0.0.0.0 TO newhost 10.x.x.x bpcd VIA pbx status: FAILED, (42) CONNECT_REFUSED; system: (110) Connection timed out; FROM 0.0.0.0 TO newhost 10.x.x.x bpcd VIA vnetd status: FAILED, (42) CONNECT_REFUSED; system: (110) Connection timed out; FROM 0.0.0.0 TO newhost 10.x.x.x bpcd
12:29:42.588 [30127] <16> vnet_connect_to_bpcd: connect_to_service(newhost, bpcd, ...) failed: 18
12:29:42.588 [30127] <16> local_bpcr_connect: vnet_connect_to_bpcd(newhost) failed: 18
12:29:42.588 [30127] <2> local_bpcr_connect: Can't connect to client newhost
12:29:42.588 [30127] <2> ConnectToBPCD: bpcd_connect_and_verify(newhost, newhost) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(newhost) failed: 25
12:29:42.588 [30127] <16> bptestbpcd main: Function ConnectToBPCD(newhost) failed: 25
<16>bptestbpcd main: cannot connect on socket
12:29:42.600 [30127] <16> bptestbpcd main: cannot connect on socket
<2>bptestbpcd: cannot connect on socket
12:29:42.600 [30127] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
12:29:42.601 [30127] <2> bptestbpcd: EXIT status = 25
cannot connect on socket
07-31-2017 08:06 AM
Please confirm that NBU services are running on the new client and that Windows firewall is disabled.
08-01-2017 08:48 AM
Yes the netbackup services are running , and firewall is disabled
08-01-2017 09:14 AM
08-01-2017 11:00 AM
Can you post the output from the following, run it on the client newhost.
bin\bpclntcmd -self
08-16-2017 07:32 AM
,FROM 0.0.0.0 TO newhost 10.x.x.x bpcd VIA pbx status: FAILED, (42) CONNECT_REFUSED; system: (110) Connection timed out; FROM 0.0.0.0 TO newhost 10.x.x.x bpcd VIA vnetd status: FAILED, (42) CONNECT_REFUSED; system: (110) Connection timed out; FROM 0.0.0.0 TO newhost 10.x.x.x bpcd
it points to windows firewall services, please check and disable them from start>run>services.msc.
ANd try to create inbound/outbound rules for PBX, Vnetd, bpcd under Server Manger> Configuration> windows Firewal & advanced Security> inbound/oubound rules > create new rule.
It should be opened vice versa.
except it also make sure name resolution does not have any issue.
08-16-2017 09:15 AM
08-17-2017 03:47 AM
Hi sorry for the delay in response.
At client side we had to open the respective ports :
08-17-2017 03:53 AM
08-17-2017 05:14 AM
Please mark this post as solved, it might assist others like me in future.
Coz i prefer to scroll through Solved Discussions for solution to my issues.
08-24-2017 07:56 AM