Hello,
We are trying to do a restore of a file from a incremental WMware backup. The media server is a Windows 2008 and the client is a Suse 11 server. We are trying to retore the file to anther server that has a NetBcakup client installed.
What we have done so far
At first we tried to restore the the file to the Windows media server and it didn't work. My co-worker put in a ticket to Symantec (07351850) and they say that you can't restore a Linux file to a windows machine. The tech said to restore to another Linux/Unix based client? He also sent us this tech note http://www.symantec.com/docs/TECH31677.
My co-worker sent this to the tech working the case after we tryied to restore to the Linux client.
Made several attempts, but they failed. Seems I have a connectivity issue
between the media server (B) that originally performed the backup and the
client (C) I am attempting to restore to. For the client (C) I am attempting
to restore to, a different media server (A) is used. Connectivity between
media server A and client C is obviously OK.
bpclntcmd output (-pn -hn and -ip) is as expected on B and C.
I just discovered the bptestbpcd command. From media server A to client C,
the output is as expected.
From media server B to C, I get (client name changed to C):
C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client C -verbose
<16>bptestbpcd main: Function ConnectToBPCD(C) failed: 46
server not allowed access
I am baffled. Everything I have checked shows the settings are correct.
Although, DNS has a different IP address for B and C, I have everything using
local hosts files. Both B and C have two interfaces, but everything is
directing connectivity to use a specific interface (our backup VLAN).
Environment info.
Master server: Solaris 10 - NetBackup version 7.5.0.7
Media Server: Windows 2008 R2 -NetBackup version 7.5.0.7
Media Server: Windows 2008 R2 -NetBackup version 7.5.0.7
Media Server: Solaris 10 - NetBackup version 7.5.0.7
Any help would be great.
____________________
Update
My co-worker had a typo in the bp.conf file eariler in the day. He as sence fixed this issue. The error has changed form 59 to 5 and 2820