06-08-2018 04:38 AM
We have a windows 2012 server. However, we are unable to backup. Connection is established between the backup server and client server however, the data transfer does not take place and after about 2 hours, the backup fails with status 24.
bptetsbpcd command to cleint from backup/media server is completing successfully. However, backup fails.
Please advise what could be the solution:
Client NBU version: 7.5.0.6
Master\media version: 7.5.0.6
Solved! Go to Solution.
06-11-2018 06:23 AM
You need to look at the bpfis log to find hints for why it took an hour and 40 minutes to take a snapshot.
I second the recommendation to move up. 7.5.0.6 was the very first release to support Windows 2012. It was followed quickly by 7.5.0.7. You can have 7.5.0.7 clients with 7.6.0.6 master server. Even so, you should be at least at 7.6.0.3 even if you're trying to get by without support. VSS snapshots are taken by a component called BEDS that NetBackup shares with Backup Exec. The timing of the BE release was such that NetBackup 7.5.0.6 through 7.6.0.2 used BEDS from a pre-release version of the BE release needed for Windows 2012.
06-08-2018 05:35 AM
Have you looked through the following article?
https://www.veritas.com/support/en_US/article.TECH150369
This error code is usually associated with a communications issue between client/media/master.
What is the network load on the server before a backup commences?
Can you provide the following logs:
bpbkar,bpcd
06-08-2018 06:02 AM
When was NBU deployed on the 2012 client?
Has it ever worked?
Did you use the special NB_7.5.0.6 Full Installer Package for Win2012?
Have you tried the bpbkar test on the client to see if NBU can read data successfully?
Have you checked bpbkar log on the client?
One more thing....
Are you aware that all support for NBU 7.x up to 7.6.1.2 has ended more than a year ago?
06-08-2018 06:24 AM
06-08-2018 06:25 AM
06-08-2018 06:48 AM
06-08-2018 06:57 AM
This is a newly built VM. NBU was deployed recently. We were unable to backup, then we changed the attributes from host properties to continue backup if snapshot error encountered. However, we were not able to backup still. then we tested backup of C and D drive alone and it completed successfully once. However, since then, backup has been failing with status 24 after about 2 hours.
Yes, I am aware that there is no support for the current version which we are using.
I have attached the bpcd, bpbkar logs. I have also attached the bptestbpcd command result.
The bptestbpcd command exits with status 0. However, we could find the below statement in the bpbkar log.
OS Error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of
time, or established connection failed because connected host has failed to respond.
06-08-2018 07:09 AM
Can you please follow this document
https://www.veritas.com/support/en_US/article.100032031
It would from the below error that you are ultimately having Connection Refused issue (58)
status: RETRY, (42) CONNECT_REFUSED; system: (10061) No connection could
be made because the target machine actively refused it. ; FROM 0.0.0.0 TO vngnp
mac-cm 172.20.5.53 bpcd VIA pbx
As Marianne stated, has this every worked? And you really need to upgrade to the latest version, or at the very least a supported version of NetBackup.
06-08-2018 07:14 AM
06-08-2018 07:42 AM
06-08-2018 10:11 PM
@Marianne yes, NB_7.5.0.6 Full Installer Package for Win2012 is used.
Regarding the below error::
status: RETRY, (42) CONNECT_REFUSED; system: (10061) No connection could
be made because the target machine actively refused it. ; FROM 0.0.0.0 TO client 172.x.x.x bpcd VIA pbx
Yes, it is showing refused for pbx. however, bptestbpcd command is successful with status 0 over port 13724.
And we have other 2012 servers where the bptestbpcd command shows same results and backup is completing for them.
06-08-2018 10:23 PM
06-08-2018 10:25 PM
@Marianne when backup had failed, we had used disable snapshot and continue in snapshot error control in client attributes to test backup.
06-09-2018 02:27 AM
06-11-2018 06:23 AM
You need to look at the bpfis log to find hints for why it took an hour and 40 minutes to take a snapshot.
I second the recommendation to move up. 7.5.0.6 was the very first release to support Windows 2012. It was followed quickly by 7.5.0.7. You can have 7.5.0.7 clients with 7.6.0.6 master server. Even so, you should be at least at 7.6.0.3 even if you're trying to get by without support. VSS snapshots are taken by a component called BEDS that NetBackup shares with Backup Exec. The timing of the BE release was such that NetBackup 7.5.0.6 through 7.6.0.2 used BEDS from a pre-release version of the BE release needed for Windows 2012.
06-20-2018 12:50 AM
@Marianne Thanks. We have deselected WOFB for now . We have asked Wintel team to check at OS why snapshot is taking long time.
06-20-2018 06:51 AM
Look at your bpfis log. Your OS admins will be able to help you better if you can tell them which snapshot action takes a long time. Or the delay might not be the snapshot itself. It could be in some other processing within NetBackup.