Reading Time: < 1 minute

For the vExpert 2012 program there are some big changes, starting from the new paths:

  • Evangelist Path: The Evangelist Path includes book authors, bloggers, tool builders, public speakers, and other IT professionals who share their knowledge and passion with others with the leverage of a personal public platform to reach many people. Employees of VMware can also apply via the Evangelist pathway.
  • Customer Path: The Customer Path is for internal evangelists and community leaders from VMware customer organizations. They have contributed to success stories, customer references, or public interviews and talks, or were active community contributors, such as VMUG leaders.
  • VPN (VMware Partner Network) Path: The VPN Path is for employees of our partner companies who lead with passion and by example, who are committed to continuous learning and to making their technical knowledge and expertise available to many. This can take shape of event participation, video, IP generation, as well as public speaking engagements.

Although there will be three explicit paths, there will be only a single vExpert designation. The exact requirements for becoming a vExpert in each path are in applications (open on February the 15th). You will find all the details at vmware.com/go/vexpert2012

Reading Time: 2 minutes

As written in the previous post related to the upgrade to vSphere 5, the old VCB framework can still be used also with latest version, but is a not supported configuration (I’ve made the test only with a Windows Server 2008 R2 for the VCB proxy, but I suppose that works also with previous OS). Of course the SAN transport mode could not work (or not if you use VMFS5), but the NBD works as on the old vSphere 4.x.

The only issue that I get (but honestly I’ve make only few tests) is on VM with Windows Server 2008 or 2008 R2, both with virtual hardware 7 or 8. The error message is quite strange and generic:

The workaround is to set the disk.EnableUUIDparameter in the virtual machine settings to False by performing the following steps:

  1. Power off the Windows Server 2008 virtual machine through vSphere Client.
  2. Click Settings > Options >General > Configuration Parameters.
  3. Set disk.EnableUUID to False.
  4. Save the settings.
  5. Power on the virtual machine.

Note that the option is exactly the opposite that the default one and also is not the same that you may find in VM backup troubleshooting for most backup programs (for example see the VDR note).

By the way, if you have at least the Essential Plus license you can use VDR instead of VCB. Or could be the right time to choose a real backup program.

Reading Time: 2 minutes

Some days ago I found a strange issue with vSphere 5 where some VMs was not movable with Storage vMotion with a strange error: The method is disabled by ‘SYMC-INCR dd-mm-yyyy hh:mm’.

From the name SYMC my first though went on Symantec Backup Exec (the 2010 R3 version) and may on some corrupted snapshots: but the VM file where good, and there was nothing to be consolidate.

I’ve looked in the VMware KB and I found the KB 2008957 (Storage vMotion fails with the error: The method is disabled by ‘SYMC-INCR dd-mm-yyyy hh:mm’) with the symptoms and an a possible explanation: seems that Backup Exec (but probably also NetBackup) add an information (_DP-VEPA_BACKUP_RESTORE_LOCK_) to the VM before the backup that it will removed after the job. This info seems stored in the vCenter Database.

In fact, the suggested workaround for issue is:

  1. Power off the virtual machine.
  2. In the vSphere Client, right-click the virtual machine and click Remove from Inventory.
  3. Browse to the datastore where the virtual machine resides.
  4. Right-click the .vmx file of the virtual machine and click Add to Inventory. This gives the virtual machine a new ID.
  5. Power on the virtual machine and retry the Storage vMotion.

Unfortunately is not a good solution because it temporally stop the VM. In some cases (but not in all) a full backup could fix the issue.

But probably the best solution is fix it in the vCenter Database. The KB 1021265 (Manually enable vSphere solutions) explain how works the extensible framework and probably by removing the entries in the related table the issue can be fixed.

Reading Time: 4 minutes

PHD Virtual Monitor is a comprehensive virtualization monitoring solution that gives you complete visibility across your entire virtual IT infrastructure at all levels including virtual, physical and application. So it not only a multi-hypervisors monitor tool (as described in the previous post), but also a multi-environments tool.

This could be really interesting with Citrix XenServer environments where the monitoring feature are quite minimal (and without simple notification in the free edition): CPU and Memory, both for hosts and VMs; and from latest version also networking and disks (but disk only for VMs). Also the graphs are quite limited and basic:

continue reading…

Reading Time: 3 minutes

One trend in the last year(s) is that the virtualization ecosystem is growing outside the boundary where was born: historical partner vendor of VMware now are extending their solution to other hypervisors, and also also new products are designed to managed a more complex virtual environment. This was also called “Hypervisor Agnosticism” in a VKernel post.

We do not talk about interoperability across different hypervisors, but simple use same tools, especially for management, monitoring and data protection, for more type of products.

Does it make sense? For a single customer maybe not… have multiple environment could be an extra cost (also if some tools may be the same, VM format, knowledge, admin tasks will be different for each product) that could be a non sense for small and medium company. But for system integrator  this could really be useful because you can push on few products and re-use part of your knowledge and practices. And of course it make sense for the vendor of this multi-platform solutions because they can extend their business to new market.

continue reading…

Reading Time: < 1 minute

During the upgrade to Workstation 8.0.2 (on 64 bit Windows 7 OS) I’ve got a curios issue that I want to share.

Basically for some strange reason the previous version was not removed correctly and the new one was not able to install itself because the setup program fail during the old version check. Also from control panel was not possible remove the old package.

The documented (from the command line prompt) option in the exe file does not resolve this issue (also with the /clean option). And the manual remove of previous version was not possible in a fast way (delete files, registry entries and device drives was not enough…).

The solution was on Ulli Hankeln web site in the Workstation FAQ area:

Error message: “The MSI fails”
this only applies to new installations of Workstation 7 or VMplayer 3 – not updates run setup like this

Although the description does not match may issue one of the error message was the same and using this command I’ve fixed the system and install the new version of Workstation:

VMware-workstation-full-8.0.2-591240 /z “action”=”install”

Reading Time: 4 minutes

One common question is “which certification should I get?” or “which is the best one?”… As usual it depends and is not a simple “objective” choice because it also depends on your needs and on what is required (in the IT field), that could also depends year by year.

For the first question IMHO I really suggest to check your skills, think on what you would like to do and related to jobs offers. Which is the right certification could not be defined with a simple objective criteria. One criteria could simple choose a certification according on your kind of job.

continue reading…

© 2025-2011 vInfrastructure Blog | Disclaimer & Copyright