Home > SCVMM > VMM Disaster recovery and High Availability

VMM Disaster recovery and High Availability

System Center virtual machine Manager become a very important part of the virtual environment.  Although that down time for this service is acceptable as it will not interrupt the current services or the running VMs. Maybe we will lose some functionality during any downtime like SSP or the integration with SCOM (PRO) but that maybe acceptable for some companies.

But considering the high availability in designing new VMM deployment will be a great thing. So to design VMM in highly available environment we must first think about VMM component:

  1. VMM Server
  2. VMM Database
  3. Library Servers
  4. Self Service Portal

VMM Server:

Clustering of the VMM application, which enables failover of VMM itself, has not been tested and is not supported. So basically there is not a direct high availability for the services .

The workaround for that as mentioned by Microsoft is to Run the VMM server inside a highly available virtual machine which is supported.

The only recommendation for this is not to do Quick migration for this HAVM using VMM as this may cause interruption for the service.

Another workaround is to use multiple VMM environment. This is a good solution to scale out your VMM deployment by adding more virtual machine hosts and library servers as your virtual environment grows. The whole idea behind this is not to keep all your eggs in one basket.

VMM Database:

VMM is using SQL as database to store all VMM configuration information, which you can access and modify by using the VMM Administrator Console.

The VMM database requires a supported version of Microsoft SQL Server. You can either specify a local or remote instance of an existing Microsoft SQL Server database or have the Setup Wizard install SQL Server 2005 Express Edition SP2 on the VMM server.

To make the VMM database highly available, you can deploy the SQL Server instance on a failover cluster created in either Windows Server 2008 or Windows Server 2003.

VMM library:

VMM 2008 supports using highly available file servers and shares hosted by a failover cluster created in Windows Server 2008 Enterprise Edition or Windows Server 2008 Datacenter Edition as highly available library servers and library shares. VMM 2008 is not aware of failover clusters created in Windows Server 2003.

Self Service Portal:

For Self-Service Portals  it is recommended that you maintain multiple portals on multiple Web servers. Virtual Machine Manager does not support Network Load Balancing (NLB) clusters in Windows Server 2008, which are required in order to distribute the network traffic among self-service users on multiple Web sites.

Disaster Recovery for VMM:

The Virtual Machine Manager (VMM) database is a SQL Server database that contains all VMM configuration information.

To backup VMM SQL database


  1. No comments yet.
  1. September 21, 2010 at 11:18 am
  2. September 21, 2010 at 11:21 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: