If the hostname column is blank then the hostname is not being
reported to vCenter which in turn cannot report the hostname to NetBackup. A
previously mentioned, one cause for this could be that VMware tools has not
been installed inside the VM. Another reason could be that the VM has never
been powered on and therefore has never reported (via VMware tools) the
hostname of the VM to vCenter.
A workaround for this is to define the VM (for backup purposes)
using the virtual machine Display Name or the UUID.
-George
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Rusty.Major AT sungard DOT com
Sent: Thursday, December 09, 2010 3:35 PM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Blank Hostnames in VMware Client Browse Windows in
Policy
Can anyone
explain why when trying to setup a policy for 4 new VMs, all I get in the client
browse window (when trying to add the new clients to the policy) are 4 gray
icons with an empty space for the name? I select them and get an error that
they cannot be added with a blank hostname. They are now up, but they do not
have an IP that will communicate with vCenter currently, but they are working
on getting that done. Any ideas?
Thanks,
Rusty
Major, MCSE, BCFP, VCS
▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite
200, Houston TX 77079 ▪ 281-584-4693
Keeping People
and Information Connected® ▪ http://availability.sungard.com/
P Think
before you print
CONFIDENTIALITY:
This e-mail (including any attachments) may contain confidential, proprietary
and privileged information, and unauthorized disclosure or use is
prohibited. If you received this e-mail in error, please notify the
sender and delete this e-mail from your system.
