A. Mikkelsen VMware ESX scripts, commands, tools and other nice to know things that will make your virtualization days easier!!!!

Tuesday, October 21, 2008

PowerShell script – List snapshots

Filed under: PowerShell,Scripting,Tools — Tags: , , , , — A. Mikkelsen @ 11:54 am

I have created at PowerShell script that obtains a list of VM’s that have snapshots attached. The output is then converted to a html file using the cmdlet ConvertTo-HTML.
And just to make it easier to obtain the html file, the script mails the html file to me as an attachment.

Ths script has been updated thanks to Ryan, to be able to handle multiable snapshots on each VM.

Get the script from the Downlaod section.

Friday, October 10, 2008

Two free tools for Securing and auditing VM’s and ESX hosts

Filed under: Security,Tools,vSphere (ESX) — Tags: , , , , , — A. Mikkelsen @ 19:39 pm

Today i came across an article from techtarget.com about securing and auditing VM’s and ESX hosts.

There are a few free tools that can help you audit your host servers. Tripwire’s ConfigCheck and Configuresoft’s Compliance Checker for ESX, both of which are lite versions of each company’s enterprise-level product.

Read the full article here.

Thursday, October 2, 2008

Compare the installation og ESXi and HyperV

Filed under: ESXi,Microsoft — A. Mikkelsen @ 10:58 am

VMware has released a video comparing the two installations.
The video is worth watching

http://www.vmware.com/technology/whyvmware/resources/esxi-hyper-v-installation.html

Comparing ESXi and HyperV

Recreating a missing VMDK descripter file

Filed under: Disaster Recovery,ESXi,vRanger,vSphere (ESX),White Papers — Tags: , , , , , , , , — A. Mikkelsen @ 8:47 am

A few weeks ago we were conducting a vRanger DR test of a VM (new host and new LUN).

The VM was restored succesfull, but when we powered it on we discovered that it for some unexplaned reason had lost the SCSI0:1 (100GB) and SCSI0:2(300GB) VMDK’s.
It had created two new 20GB VMDK’s instead.
We searched the LUN and found the two orginal *-flatvmdk files but not the descripter files.

Use Putty to identify the size of the *-flatvmdk file. ex. 100GB

ls -lah

From a VM (not running) create a new disk with the same size as the one you are missing. The name is not important.

Locate the newly created *.vmdk and *-flat.vmdk file. Copy the new *.vmdk file to the folder that contains the orginal *-flat.vmdk file.

cp rescue_me.vmdk /vmfs/volumes/mysan/rescued/rescued.vmdk

Use VI or NANO to change the following line as below from:
RW 419426200 VMFS “rescue_me-flat.vmdk”

To:
RW 419430500 VMFS “rescued-flat.vmdk”

Make sure that the name of the .vmdk file correspond to the SCSI*:*.fileName in the vmx file.
Now just power on the VM and the orginal disks are intac.

UPDATE
Today I found out that esXpress has created a website that can create a VMDK descriptor file.
http://www.esxpress.com/tools/wrapgen.php

Below is an exampel for the rescure_me-flat.vmdk file with a size of 100GB (107374182400 bytes)
esXpress WMDK descriptor file creator

Powered by WordPress