Archive

Archive for the ‘VMWare’ Category

Nice article about VMWare storage acronyms, concepts and terminology.

11/07/2012 1 comment

Today i found a nice blog artible describing the working of VMWare Storage.

This article helped me finding an answer to the following question:
Why it takes a while for a returned IO path to actually process IO?

The answer: The PSP check every 300 seconds if the path is active again. SATP is responsible for doing the failover.

You can find the article here

Thanks Didier

Advertisements
Categories: Storage, VMWare Tags: , , , ,

“Cannot change the host configuration” when adding an existing VMFS

01/07/2010 Leave a comment

Today i have experienced a weird problem with vCenter. I was adding an existing VMFS lun to our vSphere cluster. Adding the VMFS to the first node worked flawlessly but all other nodes fails with the error “Cannot change the host configuration”

After some googling i found out that i was not the only one with this problem. It seems to be a bug in vCenter. You can work around this problem by connecting to the ESX server directly with the viclient. Adding the VMFS works perfect this way.

also see:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015986

Categories: VMWare, vSphere

VMWare Data Recovery 1.1 released.

20/11/2009 Leave a comment

VMWare has released VMWare Data Recovery 1.1.

Some of the changes are:

  • GUI File Level Restore (FLR) client for Windows virtual machines.
  • Integrity Check Stability and Performance Improved
  • Integrity Checks Provides Improved Progress Information
  • Enhanced CIFS Shares Support
  • Support for backing up Windows 2008 R2 and Windows 7 virtual machines (requires upgrading to vSphere 4.0 Update 1)
  • Datarecovery.ini – this file allows customization of the VDR parameters such as how frequent integrity check and reclaim operations run, maximum concurrent backups allowed and disabling any file level restore operations.
  • Ability to add network shares using fully qualified domain name or IP address.

The updated version can be downloaded here
Documentation can be found here

I hope this release fixes all my integrity check errors which made VDR unasable so far. I’m going to try in right away and let you know!

23-11 Update: Tried i for a few days now. All went ok but now i have one backup job stuck at 99% for two days.

12-12 Update2: Backups are running ok. Only one W2K VM backup keeps getting stuck at 99%

Categories: VDR Tags: , , ,

Changing the block size of the local VMFS during install..

12/11/2009 Leave a comment

Finally someone (PatrickD) found out a way to change the block size of the local VMFS during install. I remembered i had tried to increase before. Nowadays i create a dedicated VMFS for the service console.

 

There isn’t an easy way of doing that right now. Given that a number of people have asked for it we’re looking at adding it in future versions.
If you want to do this now, the only way to do it is by mucking around with the installer internals (and knowing how to use vi). It’s not that difficult if you’re familiar with using a command line. Try these steps for changing it with a graphical installation:

  1. boot the ESX installation DVD
  2. switch to the shell (Ctrl-Alt-F2)
  3. ps | grep Xorg
  4. kill the PID which comes up with something like “Xorg -br -logfile …”. On my system this comes up as PID 590, so “kill 590”
  5. cd /usr/lib/vmware/weasel
  6. vi fsset.py
  7. scroll down to the part which says “class vmfs3FileSystem(FileSystemType):”
  8. edit the “blockSizeMB” parameter to the block size that you want. it will currently be set to ‘1’. the only values that will probably work are 1, 2, 4, and 8.
  9. save and exit the file
  10. cd /
  11. /bin/weasel

After that, run through the installer as you normally would. To check that it worked, after the installer has completed you can go back to a different terminal (try Ctl-Alt-F3 since weasel is now running on tty2) and look through /var/log/weasel.log for the vmfstools creation command.

Hope that helps.
–Patrick.

Categories: VMWare, vSphere Tags: ,

HP Compatibility matrix

15/04/2009 Leave a comment

HP has a nice compatibility matrix which shows what HP hardware is supported with VMWare ESX version.

Check http://h71028.www7.hp.com/enterprise/cache/505363-0-0-0-121.html

Categories: VMWare

Newly created VM’s created from templates don’t show up in WSUS

17/02/2009 Leave a comment

After creating new VM’s from a template, the VM’s could not show up all in your WSUS server.
This is caused by a SusClientId being the same on all VM’s created from the template even if sysprep is used.

To fix this problem you can stop de Automatic Update service, delete the SusClientId key from the registry and start the Automatic Update service again

See http://msmvps.com/blogs/athif/pages/66376.aspx for some scripts to do this automatically.
See also http://msmvps.com/blogs/athif/archive/2005/09/04/65174.aspx

To fix this problem in the template do the following: 

  • Convert the template back to a virtual machine.
  • Boot the virtual machine
  • Stop the WUAUSERV
  • Delete the SusClientID from the registry
  • Shut down the VM (do not restart the WUAUSERV!!)
  • Convert the VM back to a template
Categories: VMWare