Last year VeeamON took place for the first time in Las Vegas.

Reading the blog posts published about Veeam’s new flagship event, it proved to be a new “try the best to go there”-event on the training schedule.

Unfortunately, there seems to be no plan for a VeeamON Europe at the moment.

Because looking at the travel expenses/travel time I guess it will be a “Mission impossible” for some of the European customers to visit this interesting event :-( .

For those who can convince their boss to attend VeeamON – save the date:

Time & Place: October 26th – 29th 2015 in the Aria Resort, Las Vegas!

Learn more about the event and pre-register here: Go VeeamON

Here are some blogposts about VeeamON 2014 that may be of interest for you:



pernixdata_pocketbooksIn case you missed it – PernixData is still offering free copies of Frank Denneman’s vSphere Design Pocketbooks as a pdf download.

The first book (published 2013) contains different design suggestions in tweet-sized chunks from major contributers like Frank Denneman, Duncan Epping and Cormac Hogan (to mention a few) along with many others from the VMware community (me, too :-) ).

The second book (published 2014) is a compellation of top blog posts from virtualization and storage bloggers from around the globe.

The book’s title is “vSphere Design Pocketbook 2.0 Blog Edition – major contributers are eg. Duncan Epping, Cormac Hogan, Josh Odgers, William Lam, Michael Webster and more.

At VMworld 2013 and 2014 PernixData distributed printed versions of the books as great give-aways for attendees. I was lucky enough to catch a copy.

Here are the links where you can get your electronic copy of this great ressources:

It is possible to exclude a dedicated virtual disk (vmdk) from snapshot operations.

A usecase for this is eg. an IO intensive SQL server you want to backup, but where there are so many changes that it is not possible to close the snapshot within a reasonable time after the backup completed. In this case you can exclude the partition with the database from snapshots and backup the SQL DB with other tools (eg. with TSM TDP SQL).

To exclude a virtual disk from snapshot operations, you have to set it to independent mode:

  • power off the virtual machine
  • delete any existing snapshots before you change the disk mode
  • right-click the virtual machine and select “Edit settings”
  • select the hard disk you want to exclude from snapshots
  • change the mode to “Independent”


You have two options when you change the disk mode to independent:

Independent Persistent:
Changes are written permanently to the disk (same behaviour like conventional disks)

Independent Nonpersistent:
When you power off, reset or revert the virtual machine to a snapshot all changes to the disk are discarded! Using the nonpersistent mode enables you to restart a virtual machine with a virtual disk in the same state every time.

So if you do not want to loose data when changing the power state of the virtual machine, you should take care to use the Independent Persistent mode!

When you use the independent disk mode option you can of course still use features like vMotion and Storage vMotion.

One feature that is no longer available when using the independent mode is to take a memory snapshot when triggering a snapshot creation. You will notice the following error:

Cannot take a memory snapshot, since the virtual machine is configured with independent disks.



One hint if you are using Tivoli Storage Manager (TSM) for Virtual Environments for backup:

Ensure that you include the following option into your dsm.opt file:

vmprocessvmwithindependent yes

If you do not set the option to yes, the entire virtual machine is bypassed by the backup operation if it contains one or more independent disks!


With vSphere 6 VMware introduced a new virtual hardware version, too – vHW11.

This new hardware version enables new maximum configurations and features listed below. Below you can find a list with enhancements and a compatiblity list showing vSphere Version to supported virtual hardware versions.

New configuration maximums for virtual machines with vHW11:

  • 128 vCPUs
  • 4 TB vRAM
  • 32 serial ports

New features with vHW11:

  • vNUMA aware hot-add RAM
  • WDDM 1.1 GDI acceleration
  • USB 3.0 xHCI controller
  • extended support for virtual graphics incl. Nvidia vGPU

Expanded Guest OS Support:

  • Solaris 11.2
  • Oracle Unbreakable Enterprise Kernel Release 3 Quaterly Update 3
  • Asanux 4 SP4
  • Ubuntu 12.04.5 and 14.04.1
  • Oracle Linux 7
  • FreeBSD 9.3
  • Mac OSX 10.10

Compatibility list virtual hardware version to ESXi/vCenter Server version:

vCenter Server 6
ESXi 6
vCenter Server 5.5
ESXi 5.5
vCenter Server 5.1
ESXi 5.1
vCenter Server 5.0
ESXi 5.0
vCenter Server 4.x
ESXi 4.x
vCenter Server 2.x and later
ESXi 3.x

supported = compatible: create, edit and run