11-08-2013 08:08 AM
hello,
i get this error when trying to restore from a hyper-v VM which has the netbackup client installed.
in the hyper-v policy i have 3 clients (selected by hostname) and only one of them exhibits this error.
output of bpclntcmd on the culprit machine:
C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -self
gethostname() returned: HOSTNAME
host HOSTNAME: hostname.dom.corp.net at xx.xxx.xx.xxx
aliases: hostname.dom.corp.net HOSTNAME xx.xxx.xx.xxx
getfqdn(HOSTNAME) returned: hostname.dom.corp.net
C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -pn
expecting response from server masterserver.hki.com
hostname.gt.es *NULL* xx.xxx.xx.xxx 3005
any thoughts?
thanks
Solved! Go to Solution.
11-09-2013 12:58 AM
You can see that the client knows itself as hostname.dom.corp.net.
This is the the hostname sent to the master for the restore request.
The master is resolving client IP as hostname.gt.es.
You can see that these are not the same.
Fix hostname resolution or else create No.Restrictions file (case sensitive and no extension in netbackup\db\altnames folder on the master.
11-11-2013 08:59 AM
This is all usually taken from DNS or hosts files
Create the bpcd directory under logs on the Master and Client so that we can see exactly what they are both seeing - the clue would normally be in there
Worth checking your hosts files all round too
There is also this to bear in mind:
http://www.symantec.com/docs/TECH124897
Hope this helps
11-08-2013 08:23 AM
what is the output of the command that you see in list images and for restore.. does it allowed there?
bpclient -client <clientname> -L
does the above output in bpclntcmd command gave the correct hostname in 2 commands...
mainly short name in bpclntcmd -pn output?
11-09-2013 12:58 AM
You can see that the client knows itself as hostname.dom.corp.net.
This is the the hostname sent to the master for the restore request.
The master is resolving client IP as hostname.gt.es.
You can see that these are not the same.
Fix hostname resolution or else create No.Restrictions file (case sensitive and no extension in netbackup\db\altnames folder on the master.
11-11-2013 07:50 AM
hi Marianne,
that is actually the problem, the hostname that is sent to the master server for restore is: "hostname.gt.es"
i have tried changing the client name and putting the fqdn which is "hostname.dom.corp.net" instead of just hostname but seems to make no difference.
where is the client name config kept do yo know?
i cannot use No.Restrictions because it will than allow me select an image for backup but the restore will fail because it will still try to connect to hostname.gt.es.
thanks,
florin
11-11-2013 08:59 AM
This is all usually taken from DNS or hosts files
Create the bpcd directory under logs on the Master and Client so that we can see exactly what they are both seeing - the clue would normally be in there
Worth checking your hosts files all round too
There is also this to bear in mind:
http://www.symantec.com/docs/TECH124897
Hope this helps
11-11-2013 12:55 PM
hi,
ofcourse it was the hosts file on the master although i've checked a couple of times i did not see the 1 digit ip change.
sorry to have wasted your time.
thanks,
florin
11-11-2013 08:39 PM
11-11-2013 10:54 PM
Glad your problem is solved!
Please remember to close off this discussion by marking the solution.