Virtual Machine Backup and Recovery: Five Critical Decisions

Posted on May 6, 2013 by Thomas Maurer

Together with Symantec, Mahmoud Magdy (Microsoft MVP for Exchange Server) and Mikko Nykyri (VMware vExpert) we produced a whitepaper called “Virtual Machine Backup and Recovery: Five Critical Decisions”. This whitepaper covers an overview about virtualization and the challenges which come with the new workloads in terms of backup and recovery.

Because of the outstanding economy, flexibility, and service levels it offers, virtualization is transforming data centers at breakneck speed: by 2016, an estimated 80 percent of the world’s x86 servers will be virtual machines (VMs).1 But the speed of this transformation, along with the high resource utilization, ease of cloning, moving workloads, and other ways virtualization works its magic, raise challenges for “traditional” IT services and the teams that deliver them. Nowhere is the complexity that virtualization creates for traditional IT services more apparent than in backup and recovery, which participants in a recent Symantec survey ranked among their least-successful IT initiatives. This paper addresses five critical decisions organizations must make when building a backup and recovery plan to:

Maintain protection, visibility, and control of applications and data.

Maximize utilization of established infrastructure, processes, staff, and budget.

Use virtualization to improve backup and recovery processes.

Create an efficient, scalable, future-prepared backup and recovery environment.

Each issue is presented first in general terms that apply across IT environments, and then add comments for specific platforms, applications, or industries based on our individual experience as VMware® vExperts and Microsoft® MVPs.

You can download the whitepaper here: Symantec Virtual Machine Backup and Recovery: Five Critical Decisions

Make also sure you checkout the Google Hangout event on Fri, May 10, 7:00 PM – 8:00 PM.

Join a panel of virtualization experts including Microsoft MVPs Mahmoud Magdy & Thomas Mauer and VMware vExpert Mikko Nykyri as they discuss the white paper they co-authored and offer their thoughts on the most important things to consider for a virtualized server environment.

How to install System Center 2012 SP1 Update Rollup 2 for VMM

Posted on April 29, 2013 by Thomas Maurer

System Center Logo

Microsoft last week released the Update Rollup 2 for System Center 2012 SP1 – Virtual Machine Manager which includes a lot of fixes and improvements. If you want to update you can do this by using the Windows Update scenario or install it manually.

You have to uninstall the Update Rollup 1 for SCVMM (you can find more on the reason on Carmen Summers blog post). Windows Update will not show you the Update Rollup to before you have uninstalled UR1.

If you have downloaded the Update Rollup 2 via the Windows Update Catalog and have installed it manually, it’s recommended that you uninstall UR2 first, after that uninstall UR1 and finally install UR2 on a System Center 2012 SP1 installation without any Update Rollups installed.

After you have installed the Update Rollup 2 for Virtual Machine Manager, make sure you also update the Agents on the Hyper-V hosts.

VMM Agent Versions:

Update Rollup 1: 3.1.6011.0
Update Rollup 2: 3.1.6020.0

Btw. Remember to do this not only for the VMM management server, don’t forget the hosts where the VMM console is installed, like System Center App Controller.

Cannot remove Hyper-V Host from SCVMM

Posted on April 18, 2013 by Thomas Maurer

System Center Logo

Today I run in to the problem where I could not remove a Hyper-V Hosts from System Center Virtual Machine Manager. The Hyper-V host was reinstalled before he was removed from SCVMM and the host was showing has HOSTNAME (pending) in the SCVMM Management Console. If you did a right click to remove the host, the Remove option was greyed out.

But don’t worry Windows PowerShell came to the rescue, with the following command you can remove the Hyper-V host from Virtual Machine Manager.


Get-SCVMHost <HOSTNAME> | Remove-SCVMHost -force

Migrate Hyper-V Cluster to Windows Server 2012 Hyper-V via Cluster Migration Wizard

Posted on April 17, 2013 by Thomas Maurer

Windows Server 2012 Logo

If you have already an existing Windows Server 2008 R2 Hyper-V cluster and you want to upgrade to Windows Server 2012 you have two options. The first one is by moving all virtual machines via System Center Virtual Machine Manager from the old Cluster into a new cluster. The second way to do it, is to use the Cluster Migration Wizard which is part of Windows Server 2012.

In my case I have two clusters one “old” Windows Server 2008 R2 Hyper-V cluster and my new Windows Server 2012 Hyper-V cluster. Both Clusters are fully configured and both have access to the same disks/LUNs. The disk and all the VMs are running on the old cluster.

On the new cluster you can start the Cluster Migration Wizard.

This will bring up the Cluster Migration Wizard. The wizard will ask you about the old cluster.

The Cluster Migration Wizard will scan the old cluster for CSVs and Cluster roles. You have to select the Cluster Shared Volume you want to migrate to the new cluster. Note: you can only migrate CSVs including all virtual machines running on this CSV and not just single virtual machines. If you want to migrate single virtual machines you could do a Hyper-V Export/Import or using System Center Virtual Machine Manager.

Since the Cluster Migration Wizard detects the roles as Hyper-V virtual machines he also asks for the new Hyper-V Virtual Switch.

You get a quick summary with all the information what the Migration Wizard will do, and you can migrate all roles. This means the Migration Wizard will create all cluster roles on the new cluster but will not take the existing VMs offline the VMs at this point are still running on the old cluster. You also get a Failover Cluster Migration Report at the end.

This report also shows you what’s next:

All the clustered services and applications selected for migration were migrated successfully. You may now take the clustered services and applications offline in your old cluster. Also take offline Cluster Shared Volumes used by any migrated roles, as well as storage pools for virtual disks used by any migrated roles. Then these disks, Cluster Shared Volumes, and clustered services and applications can be brought online in your new cluster.

In the new cluster you can now see the roles which are all turned of because there are still running on the old cluster. And you can also see the CSV which is offline on the new cluster and online on the old cluster.

As already mentioned we had no downtime until now. Now you can go and shutdown all the virtual machines running on your old cluster and take the migrated CSV offline.

Take the CSV offline

On the new cluster bring the CSV online

Bring the virtual machines on the new cluster back online.

And this is more how you can migrate a cluster. Remember there are still some tasks left.

Upgrade the Integration Components of all the virtual machines to the newest version.
Convert all VHDs to the new VHDX format to dynamic disks.
I also recommend that you use CSV Block Cache

There is also a great video from Symon Perriman and Rob Hindman, a Program Manager on the Windows Server Clustering & High-Availability team, in which they explain how you can upgrade to Windows Server 2012 Hyper-V.

Microsoft Server Posterpedia Windows 8 App

Posted on March 29, 2013 by Thomas Maurer

I know for a lot of people this is not something new, but in the courses I presented in the past weeks I always mentioned this great Windows 8 App called Server Posterpedia.

Server Posterpedia is an interactive app that uses technical posters as a reference for understanding Microsoft technologies. This app includes all the reference posters from different Microsoft Server Technologies such as Windows Server 2012 Hyper-V, Exchange or Windows Azure. The great thing about this App, you can not only checkout the different posters and zoom in, if you click on a specific topic for you get directly linked to the right TechNet article. This can help find some TechNet references really easy and fast.

You can get Server Posterpedia for free in the Windows Store: Server Posterpedia

Add drivers to Windows Server 2012 ISO Image

Posted on March 16, 2013 by Thomas Maurer

Windows Server 2012 Logo

I already did a post how you can add drivers to a Windows Server 2008 R2 installation image with the command line tools dism and imagex. With Windows Server 2012 you cannot use the command line tool imagex anymore but you have a new Windows PowerShell module for dism which allows you basically the same with. In this tutorial I will add drivers to a Windows Server 2012 ISO image or a Microsoft Hyper-V Server Image.

First I created three new folders:

Drivers – which includes all the extracted drivers for Windows Server 2012 (I removed all the drivers which are not related to Windows Server 2012)
ISO – This includes the extracted Windows Server 2012 ISO image
Mount – This is a empty folder which will be used to mount the WIM files

First we have to check in which Windows edition we want to add drivers. We can do this by using the Get-WindowsImage cmdlet:

 Get-WindowsImage -ImagePath .\ISO\sources\install.wim

This will show you all the Images which are included in this WIM file.

After we have seen the Index numbers we can now mount the Windows Image our Mount folder. In my example I use Image Index 3 which is the Windows Server 2012 Datacenter Core Edition

 Mount-WindowsImage -Path .\Mount -ImagePath .\ISO\sources\install.wim -Index 3

After the image is mounted we can now add the drivers from the Drivers folder.

 Add-WindowsDriver -Path .\Mount -Driver .\Drivers -Recurse

When all drivers are added to the Image you can dismount the image and save it.

 Dismount-WindowsImage -Path .\Mount -Save

We have now added the drivers to the Install image, you should also added the drivers to your boot image. To do this just do the same steps to the .\ISO\sources\boot.wim.

After that you can create a ISO file


oscdimg -n -m -bc:\temp\ISO\boot\etfsboot.com C:\temp\ISO C:\temp\mynew.iso

SCVMM 2012: Add Logical Network to all Hyper-V Hosts in HostGroup via PowerShell

Posted on November 7, 2012 by Thomas Maurer

System Center Logo

To use the Logical Networks in System Center Virtual Machine Manager 2012 on a specific Hyper-V Host or Hyper-V Cluster you have to add the Logical Network to the network interface which the logical network is available. In the GUI you can do this in the properties of the Hyper-V host under Hardware.

if you have a lot of Hyper-V hosts this can take some time. This Windows PowerShell script will help you. It will add the logical network on each Hyper-V host. It chooses the network adapter based on the network adapter name which is given on the Hyper-V host.


Import-Module virtualmachinemanager
$LogicalNetworkName = "LogicalNetwork"
$vmHostGroup = Get-VMHostGroup "HostGroupName"
$HostNetworkAdapterName = "Network Adapter Name"
$vmHosts = $vmHostGroup.AllChildHosts

foreach ($vmHost in $vmHosts) {

$guid = [guid]::NewGuid()
$logicalNetwork = Get-SCLogicalNetwork -Name $LogicalNetworkName
$vmHostNetworkAdapter = Get-SCVMHostNetworkAdapter -VMHost $vmHost | where-object {$_.ConnectionName -eq $HostNetworkAdapterName }

Set-SCVMHostNetworkAdapter -VMHostNetworkAdapter $vmHostNetworkAdapter -AddOrSetLogicalNetwork $logicalNetwork -JobGroup $guid
Set-SCVMHostNetworkAdapter -VMHostNetworkAdapter $vmHostNetworkAdapter -Description "" -JobGroup $guid -VLanMode "Trunk" -AvailableForPlacement $true -UsedForManagement $false

Set-SCVMHost -VMHost $vmHost -JobGroup $guid -RunAsynchronously

}

With the release of Service Pack 1 for System Center 2012 Virtual Machine Manager this is gone if you use the Logical Switch.