04-17-2018 05:24 AM
Hi all,
Here is my problem :
Client is HP Prodesk 600 G2 SFF, backed up successfully with 8.0 version. I have got 2 differents BMR bootable ISO (each on bootable USB keys).
First comes from SRT created with Netbackup 7.6 and with NIC drivers added editing SRT. it fails but it's okay because we can't restore 8.0 backup with 7.6 BMR.
Second comes from newly created SRT with Netbackup 8.0, in which I inserted NIC drivers too... Seems to be done fine : created Veritas folder, and copied same *.inf folders already included in first one. But this didn't work : "no network interfaces were discovered". Then I tried to insert Win 8.1 NIC drivers. But still same error.
And now... I don't know what to do next. Please help.
Regards.
Solved! Go to Solution.
04-21-2018 10:41 PM
The error code 58 is well-known. There are technotes specific to BMR https://www.veritas.com/support/en_US/article.100023265 but also check this https://www.veritas.com/support/en_US/article.100020482
04-23-2018 04:18 AM - edited 04-23-2018 04:22 AM
Network connection is missing. This is whay you get status 5.
20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) connect failed STATUS (18) CONNECT_FAILED 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd VIA pbx 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd VIA vnetd 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd 20 avr. 2018 09:42:08 - Error bpbrm (pid=7400) Cannot connect to PC-GA2-JXZN-2 20 avr. 2018 09:42:09 - Info tar32 (pid=0) done. status: 58: can't connect to client
Adding of drivers should be done on the master server, there are two tech notes describing this:
04-17-2018 06:16 AM
If memory serves me well, you can't just copy drivers to SRT and make them work, you have to add package through the NBU Admin Console and re-generate the boot image. Did you do that?
04-17-2018 06:25 AM - edited 04-17-2018 07:26 AM
I use Netbackup BMR - Boot Server Assistant, in the Shared Resource Tree Administration Wizard, Edit SRT > Explore SRT and then I add driver files.
After all I re-generate boot image.
04-17-2018 09:36 AM
You need drivers for the respective version of Windows which SRT is built for, specifically:
For an SRT at release 7.6, the device drivers must be compatible (loadable) with Windows 2008R2 and WinPE 3.0. This is a major change from previous releases.
For an SRT at release 7.6.1, the device drivers must be compatible (loadable) with Windows 2012 and WinPE 5.0. This is a major change from previous releases.
For an SRT at release 7.7.x and 8.0, the device drivers must be compatible (loadable) with Windows 2012 and WinPE 5.1 This is a major change from previous releases.
Have a look https://www.veritas.com/support/en_US/article.100026233.html
04-18-2018 07:36 AM
I had to try different drivers version downloaded from HP website, and finally found good ones.
Now, it boot but when restoring this error occurs "Could not restore files from C:, rc=5. Verify NetBackup configuration and retry"
04-18-2018 10:01 PM
Is there anything in
/usr/openv/netbackup/logs/bmrrst/client_name/log.mmddyy (UNIX) install_path\NetBackup\logs\bmrrst\client_name\log.mmddyy (Windows)
on the master server?
04-19-2018 12:08 AM
I got this.
04-19-2018 06:30 AM
From the log:
1 DEBUG nbutils.cpp:NBURestore() Restore command failed! Tried (bprestore -w -L C:\BMR\nbulog.txt -T -f "X:\listfile.txt" )--rc(5).
So bprestore get a status code 5. Do you have a failed restore job in the activity monitor - if yes what is the text in it ?
04-20-2018 12:50 AM
Yes I do have a fail error in the activity monitor.
[...] 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) connect failed STATUS (18) CONNECT_FAILED 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd VIA pbx 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd VIA vnetd 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd 20 avr. 2018 09:42:08 - Error bpbrm (pid=7400) Cannot connect to PC-GA2-JXZN-2 20 avr. 2018 09:42:09 - Info tar32 (pid=0) done. status: 58: can't connect to client 20 avr. 2018 09:42:09 - Error bpbrm (pid=7400) client restore EXIT STATUS 58: can't connect to client 20 avr. 2018 09:42:33 - restored from image PC-GA2-JXZN-2_1524138339; restore time: 0:05:21 20 avr. 2018 09:42:57 - Warning bprd (pid=19780) Restore must be resumed prior to first image expiration on 21/07/2018 13:45:39 20 avr. 2018 09:42:57 - end Restore; elapsed time 0:06:13 Windows File System policy restore error (2808)
04-21-2018 10:41 PM
The error code 58 is well-known. There are technotes specific to BMR https://www.veritas.com/support/en_US/article.100023265 but also check this https://www.veritas.com/support/en_US/article.100020482
04-23-2018 04:18 AM - edited 04-23-2018 04:22 AM
Network connection is missing. This is whay you get status 5.
20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) connect failed STATUS (18) CONNECT_FAILED 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd VIA pbx 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd VIA vnetd 20 avr. 2018 09:42:08 - Info bpbrm (pid=7400) status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO PC-RESTORE-JO 123.8.50.40 bpcd 20 avr. 2018 09:42:08 - Error bpbrm (pid=7400) Cannot connect to PC-GA2-JXZN-2 20 avr. 2018 09:42:09 - Info tar32 (pid=0) done. status: 58: can't connect to client
Adding of drivers should be done on the master server, there are two tech notes describing this:
05-03-2018 01:16 AM
Answering a bit lately.
In fact, our network routing was not correct. Just had to add some routes and edit some firewalls and gateways.
Everything working fine now. Thanks everyone.
05-26-2019 01:33 AM
Hello, I have the same problem as you. How do you solve it?
05-26-2019 11:35 PM
The original issue in this discussion was solved.
Pease see the post marked as Solution.
Best to start a new discussion with details of your exact environment if the marked solution does not help.