Working with a new backup product here and we’re having a few issues with snapshots getting out of order and getting disk consolidation alarms, but are unable to do so.

The fix I use is this shell command and then manually edit the VMDKs (not the -flats) and point to the correct parent disks:

grep “CID=” `ls *.vmdk | grep -v ‘delta\|flat’`

That outputs the following:

SERVERNAME-000001.vmdk:CID=da409ac4
SERVERNAME-000001.vmdk:parentCID=da409ac4
SERVERNAME.vmdk:CID=59111937
SERVERNAME.vmdk:parentCID=ffffffff
SERVERNAME_1-000001.vmdk:CID=014da149
SERVER1_1-000001.vmdk:parentCID=014da149
SERVER1_1.vmdk:CID=0dfb62a4
SERVER1_1.vmdk:parentCID=ffffffff
SERVER1_2-000001.vmdk:CID=182d97e6 <–in this case, the child, parentCID and actual parent have the same CID. So here you can just changed the snapshot’s CID to something random.
SERVER1_2-000001.vmdk:parentCID=182d97e6
SERVER1_2.vmdk:CID=182d97e6
SERVER1_2.vmdk:parentCID=ffffffff

As you can see, the “parentCID” for the snapshots is the same as the child CID itself. The snapshot is pointing to itself as the parent.

So, after editing, this is how it should look:

SERVERNAME-000001.vmdk:CID=da409ac4
SERVERNAME-000001.vmdk:parentCID=59111937
SERVERNAME.vmdk:CID=59111937
SERVERNAME.vmdk:parentCID=ffffffff
SERVERNAME_1-000001.vmdk:CID=014da149
SERVER1_1-000001.vmdk:parentCID=0dfb62a4
SERVER1_1.vmdk:CID=0dfb62a4
SERVER1_1.vmdk:parentCID=ffffffff
SERVER1_2-000001.vmdk:CID=thevlab1
SERVER1_2-000001.vmdk:parentCID=182d97e6
SERVER1_2.vmdk:CID=182d97e6
SERVER1_2.vmdk:parentCID=ffffffff

You can now consolidate your disks.

{ 0 comments }

We ran into this issue when rebuilding some hosts.  When trying to vMotion the guests to the newly rebuilt hosts, the vMotion would fail at 82% with the error “Source detected that destination failed to resume.”

I came across the following article that gave me an idea:  KB: 1006052

The article mentions the following:

Adding a host by these three different methods produces three different UUIDs:

  • hostname
  • hostname.domainname
  • IP.address.of.host

 It appears that the hostname or hostname.domain is also case sensitive.  Mounting a datastore by “DATASTORE.domain.com” will generate a different UUID than “datastore.domain.com”.

Running esxcfg-nas –l on a host will show you the name of the NFS mounts.  ls -l from the /vmfs/volumes directory will show you the UUID of the datastores.

Compare these two hosts:

HOST1
~ # esxcfg-nas -l
<datastorename1> is <path1> from <nas.domain.com> mounted
<datastorename2> is <path2> from <Nas.domain.com> mounted
<datastorename3> is <path3> from <Nas.domain.com> mounted
<datastorename4> is <path4> from <Nas.domain.com> mounted
<datastorename5> is <path5> from <Nas.domain.com> mounted

UUID:  datastorename3 -> 3ba0562f-6ca841f9

HOST2
[root@tevp03187 root]# esxcfg-nas -l
<datastorename1> is <path1> from <nas.domain.com> mounted
<datastorename2> is <path2> from <nas.domain.com> mounted
<datastorename3> is <path3> from <nas.domain.com> mounted
<datastorename4> is <path4> from <nas.domain.com> mounted
<datastorename5> is <path5> from <nas.domain.com> mounted

UUID:  datastorename3 -> 961816a8-7064b2f7

TLDR Version:  Ensure that when mounting datastores you use the same case for the paths across all hosts.

{ 0 comments }

Info here: http://bit.ly/IkcYlQ

Download firmware-10.00-0.zip (1.2 GB)

 

{ 0 comments }

While a nice purple color, not a good way to start a Monday:


Generated on a HP DL580 G7 running ESXi 4.1 U1
Install patch here: HP Sourcing Driver

If patch is already applied, then possible hardware issue. Make sure latest firmware and drivers are installed.

{ 0 comments }

Nothing special, but might be handy.  Were having a few small issues with opening firewall ports and which ones today.  I threw together this doc to help a few other team members.  It is all the ports found in KB1012382 separated by product.

VMware Ports

{ 0 comments }

Just joined a twibe. Visit htt…

Tweet Just joined a twibe. Visit http://twibes.com/VMware to join

Read the full article →

Best Dilbert ever: http://bit….

Tweet Best Dilbert ever: http://bit.ly/aQSCjp

Read the full article →

Access Denied when trying to view Event Logs

Tweet Recently came across an issue where an “Access Denied” message would be given when trying to view the System or Application logs. The problem stemmed from a developer adding “Everyone” into the “Guests” group on the server.  Since Windows 2000, Guests are not allowed to view these logs. The fix was simple- remove “Everyone” […]

Read the full article →

VMware end of Availability

Tweet Some older versions will not be available for download soon: Virtual Infrastructure products being removed by May 2010: ESX 3.5 versions 3.5 GA, Update 1, Update 2, Update 3 and Update 4 ESX 3.0 versions 3.0 GA, 3.0.1, 3.0.2 and 3.0.3 ESX 2.x versions 2.5.0 GA, 2.5.1, 2.5.2, 2.1.3, 2.5.3, 2.0.2, 2.1.2 and 2.5.4 […]

Read the full article →

Cleaning up after a P2V

Tweet After converting a physical to a virtual, there is some clean-up that should be done. Non-existing hardware devices should be removed. Software which controlled the legacy hardware should be uninstalled. Here’s how to uninstall the old hardware: 1) Open a command-prompt and type: “set devmgr_show_nonpresent_devices=1” (without quotes), hit Enter now type: “start devmgmt.msc” Leave […]

Read the full article →