03-11-2010 09:09 AM
Solved! Go to Solution.
03-11-2010 01:01 PM - edited 08-31-2016 06:00 AM
If FQDN names are used either in DNS or aliased in local hosts files, ensure that FQDN names for master and media servers match in all directions.
I have seen situations where media servers can be backed up as clients, all comms tests complete 100% fine, but backups would fail when used as media server. All NBU config was done using short names, but it seems when FQDN is used anywhere (e.g. alias in hosts file) resource allocation will try to use the long name.
1) In one scenario, all config was done using short names, but media server backups kept on failing with 811.
After weeks of troubleshooting, the FQDN for the Media server was found to be incorrect in the /etc/hosts file on the Master server (extra 'c' in FQDN):
nnn.nn.n.nn ipcprod1 ipccprod1.yyyyyy.co.za
On the media server, the entry for itself was correct:
nnn.nn.n.nn ipcprod1 ipcprod1.yyyyyy.co.za loghost
2) Another scenario with status 811 (again, all NBU config was done using short names):
Entry for media server in /etc/hosts on master server:
10.30.3.20 sp-adm01 sp-adm01.xxxxxx.co.za
On the media server itself, it had no knowledge of FQDN for itself. There was no alias for sp-adm01.yyyyyyy.co.za in it's own /etc/hosts file and nslookup could not resolve sp-adm01.xxxxxx.co.za either.
I removed the FQDN alias from /etc/hosts on master server and backups started working.
I hope these examples help you to double-check & troubleshoot your environment.
03-11-2010 09:56 AM
IBM.ULT3580-TD4.002 No No No hcart
unixmastermedia /dev/rmt0.1 SCAN-TLD
unixmedia /dev/rmt0.1 TLD
WinSanMedia {0,0,2,0} TLD
WinSanMedia {0,0,2,0} TLD
So now the question is why do you have issues...
I have not looked at the compatibility list - I assume that your Linux is supported as a media server?
have you tried rebooting the Linux server or at least bouncing netbackup on it.
that is all I have for you because it looks ok to me.
03-11-2010 01:01 PM - edited 08-31-2016 06:00 AM
If FQDN names are used either in DNS or aliased in local hosts files, ensure that FQDN names for master and media servers match in all directions.
I have seen situations where media servers can be backed up as clients, all comms tests complete 100% fine, but backups would fail when used as media server. All NBU config was done using short names, but it seems when FQDN is used anywhere (e.g. alias in hosts file) resource allocation will try to use the long name.
1) In one scenario, all config was done using short names, but media server backups kept on failing with 811.
After weeks of troubleshooting, the FQDN for the Media server was found to be incorrect in the /etc/hosts file on the Master server (extra 'c' in FQDN):
nnn.nn.n.nn ipcprod1 ipccprod1.yyyyyy.co.za
On the media server, the entry for itself was correct:
nnn.nn.n.nn ipcprod1 ipcprod1.yyyyyy.co.za loghost
2) Another scenario with status 811 (again, all NBU config was done using short names):
Entry for media server in /etc/hosts on master server:
10.30.3.20 sp-adm01 sp-adm01.xxxxxx.co.za
On the media server itself, it had no knowledge of FQDN for itself. There was no alias for sp-adm01.yyyyyyy.co.za in it's own /etc/hosts file and nslookup could not resolve sp-adm01.xxxxxx.co.za either.
I removed the FQDN alias from /etc/hosts on master server and backups started working.
I hope these examples help you to double-check & troubleshoot your environment.
03-11-2010 11:40 PM
03-12-2010 04:17 AM
03-12-2010 04:23 AM