Yellow Bricks

by Duncan Epping

VMware

Snapshot Manager for VI3 – NetApp

· ·

On the Storage Nuts & Bolts Blog on the NetApp website there’s a sneakpreview on the Snapshot Manager for VI3 by NetApp. Here a couple of outtakes from the original article. Be sure to check the original article because there are also a couple of screenshots in there.

Although from the sound of it, it appears that SMVI is related to other SnapManager products like SnapManager for Exchange, SQL, SharePoint and Oracle, SnapManager for VI is not related to specific applications. SVMI rather serves as a medium to streamline the backup and restores of Virtual Machines and/or Datastores in a VMware environment. It interacts with VC or the ESX server and NetApp Storage devices and creates instantaneous backups and near-instantaneous restores of Virtual Machines and/or Datastores.

What can you backup and Restore?
You can backup at the Datastore level and Restore at the VM level or the Datastore level.

Where can you restore a VM?
You can restore it on the original Datastore or a different Datastore. SVMI provides a listing of all existing datastore and you basically get to choose the one you want.  Furthermore, you have the option to mount the backup and verify its contents. 

How does it backup?
SMVI temporarily leverages VMware’s snapshot which makes calls to the LGTO_sync (lgtosync.sys) driver part of the VMware tools which is responsible for flushing dirty buffers to disk for filesystem consistency and creates a Redo Log (Redo Log is a misnomer, it’s actually a bitmap) for storing disk changes. We keep the VMware snapshot around until we complete our Snapshot (NetApp) on the array side, which takes no more than a few seconds, at which point we delete the vmware snapshot, thereby merging the changes in the “redo log” with the original VMDK.

One thing that surprised me is that NetApp didn’t develop this cool add-on as a VirtualCenter Plugin… but within time this will probably happen.

New 3.5 Patches!

· ·

VMware just uploaded a whole bunch of patches for ESX 3.5:

ESX350-200802301-BG : Update to the bnx2 Driver
ESX350-200802303-SG : Security Update to the util-linux Package
ESX350-200802304-SG : Security Update to the Perl Package
ESX350-200802305-SG : Security Update to the openssl Package
ESX350-200802306-BG : VMware ESX Server 3.5, Patch ESX350-200802306-BG: Daylight Saving Time Update
ESX350-200802401-BG : Updates to vmware-hostd
ESX350-200802403-BG : Improved Statistics Collection for Support Scripts, Fix for Patch Issue Seen After Upgrading from ESX Server 2.5.x to 3.5.0
ESX350-200802404-BG : Resolves DMA Issues on LSI 1078 and 106XE HBAs
ESX350-200802405-BG : Update to MegaRAID SCSI Driver to Fix Dell PowerEdge 6650 Boot Issue
ESX350-200802406-SG : Updated aacraid Driver
ESX350-200802408-SG : Security Updates to the Python Package
ESX350-200802409-BG : Fix for Reset Issue with CD-ROM Controller
ESX350-200802410-BG : Unexpected Reboot of Virtual Machines Configured to Automatically Start or Stop
ESX350-200802411-BG : Enhanced Validation Checks, and Fixes for Storage VMotion and Lab Manager
ESX350-200802412-BG : Updates to the VMkernel to Fix Networking and Hardware Issues
ESX350-200802413-BG : Sunfire X4200 Host Hangs Because of HBA Timeouts Due to DMA Problems
ESX350-200802414-BG : Discrete Sensors Report Wrong Information to Monitors
ESX350-200802415-SG : Security Update to Samba Packages

And there’s also an update for 3i available:

ESXe350-200802401-I-BG : Update to the bnx2 Driver

Good luck with patching those hosts, I will be testing these patches later this day so if I encounter any problems you will be the first to know

Powershell Toolkit beta coming up and VMworld lab PDF!

· ·

Eric Sloof just pointed us out to the Blog on the VMware website about the upcoming Powershell Toolkit Beta. I have been playing around with this toolkit for a while but had a hard time figuring out how to actually make useful scripts. The PDF that was also released has some cool examples of useful scripts for instance these:

Change the number of virtual CPUs configured for “Email VM 1” from 1 to 2:
get-vm “Email VM 1 User N” | `
set-vm –numcpu 2

Read the last 10 lines of the hostd log file from ESX1:
(get-log –host (get-vmhost esx1) `
hostd).Entries[-10..-1]

Identify which VMs have network adapters that are not automatically connected:
get-vm | where { `
$_ | get-networkadapter | where { `
$_.ConnectionState.StartConnected -eq 0 `
} `
}

Cool stuff!

VMReference Card 1.1!

· ·

Forbes just uploaded a brand new version of the VMReference Card. Download it, print it and keep it close!

Source: http://vmreference.com/

Here is version 1.1 in all its shining glory.

I’ve made several corrections (thanks everyone), added a few extra snippets and dusted it with a sprinkling of handy tips and tricks.

The biggest change is a small 3i section. I have been wanting to do this for a while, but I haven’t had a chance to play with it since its beta. There is quite lot of information around about 3i now, but I just wanted to add the sort of stuff people would actual use.