Unsolved
This post is more than 5 years old
87 Posts
0
2079
September 10th, 2012 11:00
nsrvadp_save and hostname check
What kind of hostname is nsrvadp_save checking?
I've been checking out Networker8 for a couple of days and noticed that some of my VADP saves failed because of name resolution failures:
sep 10 08:00:18 nws01.t-i.demo: * dc02.t-i.demo:*FULL* Performing the backup via the Virtual Center.
sep 10 08:00:18 nws01.t-i.demo: * dc02.t-i.demo:*FULL* Trying to connect to the VM using ipaddr/DNS name 'dc02.t-i.demo'.
sep 10 08:00:18 nws01.t-i.demo: * dc02.t-i.demo:*FULL* 90227:nsrvadp_save: Unable to find the VM with an IP address or hostname of 'dc02.t-i.demo'
DNS all working fine, no problem there and my other host named dc01.t-i.demo working fine.
After trying different stuff I noticed that virtualcenter was seeing DC02.t-i.demo as the hostname via vmware tools. I've tried to use the VADP_VM_NAME attribute but still no luck:
sep 10 11:16:21 nws01.t-i.demo: * dc02.t-i.demo:*FULL* Application information attribute VADP_VM_NAME for client dc02.t-i.demo is set to "DC02.t-i.demo".
sep 10 11:16:21 nws01.t-i.demo: * dc02.t-i.demo:*FULL* Trying to connect to the VM using VM name 'DC02.t-i.demo'.
sep 10 11:16:21 nws01.t-i.demo: * dc02.t-i.demo:*FULL* 80398:nsrvadp_save: Unable to find the VM with VM name: DC02.t-i.demo.
After deploying a template, host was name DC02.t-i.demo.
I then tried with another VM, same problem. I've then renamed hostname in OS to be all lowercase and now it's working fine.
So what kind of name is nsrvadp_save checking, looks like it's not DNS but the stuff vmware tools is returning to my virtual center.
Regards,
John Grinwis
pn1lDbv3G612259
105 Posts
0
September 11th, 2012 02:00
Hi John,
The error " nsrvadp_save: Unable to find the VM with VM name: DC02.t-i.demo." occurs when there are mismatches in the host name.
Normally when using the VADP_VM_NAME parameter in the Application information attribute of the Virtual Machines client resource, ensure that this parameter is set to the same name as seen in the vSphere GUI, including matching the case and specifies if VM needs to be backed up using its name as seen in the Vsphere GUI
So I doubt that under vSphere GUI, the VM name was configured with DC02.t-i.demo name
Thank you
ShivaKiran
Panwar
79 Posts
0
September 11th, 2012 03:00
Hi,
Please check whether client is created with DNS name or as VM name created in the Vsphere GUI. If the client is created VM name in the Vsphere GUI, please add VADP_VM_NAME parameter in the Application information attribute of the Virtual Machines client resource as suggested by Sivakiran.
Regards
Panwar
DaGrin
87 Posts
0
September 11th, 2012 12:00
This is an example vm that will give vadp name error:
This is info from VirtualCenter:
hostname on host is resolving as DC02.
John
pn1lDbv3G612259
105 Posts
0
September 12th, 2012 03:00
Hi John,
Try updating the vCenter host file and the client host file with the name DC02.
Also make this client name as aliases under client properties under NMC.
That should resolve the name resolution
Thank you
ShivaKiran