02-18-2014 10:49 AM
Netbackup 7.5.0.7
Windows Server 2008 R2 with SP1 x64
I'm only backing up VM's that are connected to my vCenter server which Netbackup has complete access too.
Full error found in Reports-->Problems
"netbackup unable to resolve hostname <host>, no hostname alias added to pem name manager."
Started seeing this about two weeks ago.. Not sure if 7.5.0.7 is the cause because I dont remember seeing it with version 7.5.0.6.
Been searching the forums, and google and the manual.. Not seeing a solution to this issue. Been looking in logs, and looking at the nbpem log.. Not really seeing anything in there that makes any sense...
Can anyone help resolve? Thanks!
Solved! Go to Solution.
02-18-2014 11:17 AM
Hello,
Even though your backing up a VM. NetBackup is trying to see if it can resolve the hostname of your VM. In this case it can't, so it tries for the alias if you have set up one with the bpblient command (TECH189804).
Please check and see if your NetBackup environment can resolve the VM hostname you specified in the policy. Please also check for short name VS FQDN as well. If it doesn't resolve, modify DNS or hosts file.
02-18-2014 09:23 PM
Have a look at Primary VM identifier in Backup options on the VMware tab.
The default is VMhostname which requires network lookup.
Have a look at Table 5-3 on p. 54 of NetBackup 7.5.0.x for VMware Administrator's Guide http://www.symantec.com/docs/DOC5605
See if one of the other options will work.
I must admit, this is a first for me:
"All or most of the VM's in my environment are dev, so some dont have an IP and are not routable."
You will also want to disable IP Resolution.
See p.158 of the same manual for instructions on changing disableIPResolution in the Registry of the backup host.
02-18-2014 11:17 AM
Hello,
Even though your backing up a VM. NetBackup is trying to see if it can resolve the hostname of your VM. In this case it can't, so it tries for the alias if you have set up one with the bpblient command (TECH189804).
Please check and see if your NetBackup environment can resolve the VM hostname you specified in the policy. Please also check for short name VS FQDN as well. If it doesn't resolve, modify DNS or hosts file.
02-18-2014 12:59 PM
Hi SymTerry,
Thanks for the reply and the link.
How can I disable NB from trying to see if it can resolve the hostname of a VM? All or most of the VM's in my environment are dev, so some dont have an IP and are not routable. I'd like it to backup the VM and use the shortname rather than the FQDN. Or whichever is the best pratice...
Thank you very much for the help!
02-18-2014 09:23 PM
Have a look at Primary VM identifier in Backup options on the VMware tab.
The default is VMhostname which requires network lookup.
Have a look at Table 5-3 on p. 54 of NetBackup 7.5.0.x for VMware Administrator's Guide http://www.symantec.com/docs/DOC5605
See if one of the other options will work.
I must admit, this is a first for me:
"All or most of the VM's in my environment are dev, so some dont have an IP and are not routable."
You will also want to disable IP Resolution.
See p.158 of the same manual for instructions on changing disableIPResolution in the Registry of the backup host.
02-19-2014 09:58 AM
Marianne,
Thank you very much! I should have been able to find those entries in the manual.
My Primary VM identifier is set to "VM display Name" for every policy.
I already have the disableIPResolution registry key. Curious if the value is left at 0, or should it be set as 1. I'm assuming to leave the value as "0" as the manual does not specify.
Thanks to both of you! I hope this resolves my issues.
02-19-2014 10:15 AM
Set it to 1 per this post:
https://www-secure.symantec.com/connect/forums/recently-upgraded-75-and-now-vm-browsing-doesnt-work
02-19-2014 10:34 PM
Think of it as a 'double negative'.
disableIPResolution = 0
means that disabling IP resolution is off. Meaning that IP resolution is ON.
disableIPResolution = 1
means that disabling IP resolution is on. Meaning that IP resolution is OFF.
02-20-2014 06:39 PM
Read that post, set to one and rebooted.
Thanks!
02-24-2014 12:57 PM
Still getting the same error for VM's even tho I have disableIPResolution = 1. I have rebooted since I made the change..
"netbackup unable to resolve hostname <host>, no hostname alias added to pem name manager."
The tech doc says you need to add the reg, but since I'm on a 64bit machine I added it to the wow6432node section. None of your tech docs I found says to add it in this path if your x64 OS. So do the docs need to be updated to reflect this info or I'm I putting it in the wrong spot?
"Backup of client exited with status 6 (the backup failed to back up the requested files)"
"unexpected terminiation of client... "
"Could not send server status message..."
I wanted to add that for all of my policies that I have selected automatic client selection thru query. The environment changes to much to specificy thru the browse option..
Why is NB having such a hard time backing up VM's and templates? It should not be this difficult.. *sigh*
I have NB 7.5.0.7, using basic disks..
Please help!
02-24-2014 01:48 PM
The technote linked in my post above says it is good for
and the registry path is
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\BACKUP\disableIPResolution
as for the other issues, you should open a new thread, especially since this one was closed a few days ago
02-24-2014 02:34 PM
Thanks for letting me know! Will create a new thread.