There are 3 VMware KBs related to this type of error:

• KB1009872
• KB1010172
• KB1013877

Unfortunately none of these solved my problem.

In virtual center U1 the configuration of the performance charts database has changed location. It’s now located in C:\Program Files\VMware\Infrastructure\tomcat\conf\Catalina\localhost\statsreport.xml.

VMware updated the KB article (KB1013877) in the mean time to reflect the changes in Update 1.

Now you can backup your complete VMware infrastructure in seconds without putting any load on your storage or ESX servers. No need to have any additional hardware, your existing VMware and Storage infrastructure is sufficient. SMVI supports all types of storage connectivity, FC, iSCSI and NFS are all supported. It’s much easier then using VCB and much quicker as well

Kostadis Roussos is writing a series of blog posts about the technical background of SMVI. Check out his blog.

I’m not going in to detail about the installation of SMVI as it isn’t rocket science.

The SMVI client login screen to connect to the SMVI server. There is also a CLI to administer your SMVI server.

The getting started screen, with all steps to do in order to configure snapmanager.

The Setup screen. First you have to add the Virtualcenter server of your VMware environment. At the moment you can only configure one VC server in SMVI. Hopefully this will change in future releases, especially in conjunction with Site Recovery Manager this would be usefully.

Secondly you have to add your storage systems. If there are snapmirror relations for your VMFS/NFS datastores configured you need to add the destination Netapp as well. Then you can initiate consistent snapmirror replication of your datastores.

Once finished configuring SMIV it’s time to add some backup jobs.

Give the backup job a name and description.

Select the datastores which you want to backup. You can also tick the checkbox to “Initiate snapmirror update” then you replicate the consistent snapshot to your remote netapp.

Configure the backup schedule.

Add the user which will be used to do the backup. This user needs access to the VC server as it will need to create VMware snapshots on the VMs.

Configure the retention scheme of your backups.

The email notification settings screen.

The backup job configuration is finished.x

The backup schedule overview screen with our previously configured job.

The backup job finished successfully, now we can do a restore.

When I tried restoring a VM which I deleted using the VI client SMVI wasn’t able to restore it. After some more testing I found that SMVI needs the VM’s directory to restore the VM files. It should be possible to restore the VM without that the original directory is necessary.

It’s also not possible to restore a VM to another datastore then it’s original datastore through SMVI. You can bypass this by mounting the backup and then copying the VM manually. Another possibility is to restore it to the original location and the use storage VMotion or cold migration to move the VM to another location.

Once the directory is recreated manually SMVI is able to restore the backup. If the VM isn’t in VC inventory anymore you need to manually register the VM in the VC once it’s restored.

On the backup screen you can manually take backups off complete datastores or VMs. When backing up individual VMs SMVI takes a Netapp snapshot of the whole datastore but only the backup of this VM will be consistent trough a VMware snapshot.

VMware recently released a free version of ESXi. Ideal for people that are running their own little home-datacenter ;-)

Rich over at VM /ETC blog wrote a nice article discussing the limitations of this free version.

As for me, the hard disk controller on the motherboard of my test machine is not recognized. I could obviously buy an external one to build myselves an ESX whitebox but I’m sticking with Hyper-V for my virtualization needs for now.

This makes managing your VMware environment using  Powershell even more easier. PowerGUI lets you write your own Powershell scripts and the VMware PowerPack is also compatible with the VI client plugin. The plugin uses your current connection to the VC. You don’t need to make a separate connection for every script.

The Thinapp welcome screen.

Some info on how to use Thinapp. Make sure to always run it on a clean PC so you’re sure that you include all necessary files in your package. Under advanced settings you can select which drives you want to scan during the prescan.

Before installing the application Thinapp needs to scan your system to take a baseline snapshot.

The prescan is finished. Time to install and configure your application.

Once the application installation is finished, Thinapp does a postcan. It looks for differences on the file system as well as in the registry, all these changes become part of package.

Select the entry point you want to use.

Configure the security settings for the package and also the sandbox location. The user’s settings are configured in the sandbox.

Now it’s time to configure the isolation settings. Merged isolation lets you access the local user settings e.g. Firefox bookmarks. WriteCopy isolation all files are newly created and the application has no access to the local file system.

Select MSI generation when you want to distribute the package using any software distribution tool.

Thinapp copies all files and registry settings to the project location.

The final screen. Here we’re going to browse the project as we have to change some settings in the package.ini file.

As the Java JRE is packaged separately we have to edit the package.ini file and remove the ; from the OptionalAppLinks line.

We can now build the Firefox project.

Repeat the same steps for the Java JRE. Once that’s build create a “plugins” folder in the location of the Thinapped Firefox and copy the Java package to it. When Firefox is executed it will look for any exe file in the plugin folder and will link it.

No need to use a separate VM for administering Clariions anymore.

PS:  Marrs posted an excellent post on the VMware forum on packaging Firefox to run several versions of Java at the same time.

• They replaced get-viserver with connect-viserver. get-viserver is now an alias for connect-viserver.
• disconnect-viserver was added which allows you to do a clean disconnect. Hence the rename of the get-viserver cmdlet.
• VMware also added cmdlets for managing the VMware Update Manager.