Archive

Archive for July, 2010

HowTo monitor the NIC used by a Virtual Machine in a Hyper-V cluster

July 29, 2010 Leave a comment
 
Let’s say you are using Hyper-V Cluster and you have the VM clustered. What happens is that your machine does not failover when the NIC used for that machine has a problem. E.g. Network cable unplugged. Have you noticed that? Have you tested your cluster for this yet? 

The best approach is to use NIC Teaming. But in case your solution(Hyper-V Host Clusters) does not support  don’t support NIC Teaming, then one approach to workaround this, is to add a cluster resource script to the Cluster Group.

Interested? Clique the link below to get the script, with short instructions.

http://blogs.msdn.com/b/robertvi/archive/2008/12/05/howto-monitor-the-nic-used-by-a-virtual-machine-in-a-hyper-v-cluster.aspx

Advertisement
Categories: Virtualization

Windows 7 and Windows Server 2008 R2 SP1 : New Features

July 29, 2010 Leave a comment
 
 
Have you downloaded the Windows 7 and Windows Server 2008 R2 SP 1 Beta yet?  Make sure you check out the new SP1 Beta Resource page on Microsoft.com as well as the TechNet SP1 page — and don’t forget to grab the download here. 
 
For Windows Server 2008 R2, SP1 Microsoft will be introducing two new features: Microsoft RemoteFX and Dynamic Memory. These features are designed to meet the increasing needs of customers as they utilize virtualization in their environments with Windows Server 2008 R2. You can read more about RemoteFX and Dynamic Memory on the Windows Server Division WebLog.
 
Dynamic Memory is an enhancement to Hyper-V in R2 and allows IT administrators to pool all the memory available on a physical host and dynamically distribute it to virtual machines running on that host as necessary. That means based on changes in workload, your VMs will be able to receive new memory allocations without a service interruption. For a deeper look at Dynamic Memory check here.
 
RemoteFX is the latest addition to Microsoft’s desktop virtualization stack. Using this new feature in Windows Server 2008 R2, you’ll be able to deliver an even richer and more user-transparent desktop virtualization experience. RemoteFX functions independently of any graphics stack and supports any screen content, including rich content like Silverlight or Flash. It also enhances the end-user’s hardware experience with support for USB redirection. Because it uses virtualized graphics resources, RemoteFX works on a wide array of target devices, which means you can deploy it over both thick and thin client hosts and a wide variety of network configurations. For some more information on RemoteFX check here.
 
So don’t wait – go ahead and deploy… you know you want to! 😉
 

The Windows 7 and Windows Server 2008 R2 SP1 Beta helps keep your PCs and servers on the latest support level, provides ongoing improvements to the Windows Operating System (OS), by including previous updates delivered over Windows Update as well as continuing incremental updates to the Windows 7 and Windows Server 2008 R2 platforms based on customer feedback, and is easy for organizations to deploy a single set of updates.

The public beta is best suited for IT pros, tech enthusiasts and developers who need to test the service pack in their organization or with the software they are developing.

In order to download and install the Windows 7 and Windows Server 2008 R2 SP1 Beta you must currently have a Release to Manufacturing (RTM) version of Windows 7 and Windows Server 2008 R2 already installed. The Beta is available in English, French, German, Japanese and Spanish.

To learn more about piloting, deploying and managing Windows 7, visit the Springboard Series on TechNet.

 

Categories: Virtualization

Tips and Recomendations for DPM 2010 to protect Hyper-v/CSV

July 16, 2010 Leave a comment
 

Based in my experience here are some recomendations and tips for SCDPM in a Hyper-v/CSV environment.

With live migration, pro-tips in SCVMM and virtualization admins, the placement of a virtual machine will never be fixed.  SCDPM will know where the virtual machines is, and will protect it from there.  If a machine is moved, then SCDPM will follow it to its new path.

 

Recommendations :

 

  • Install SCDPM in a x64 physical server always with the OS installed in a Raid 1. I recommend at least 8GB of Ram and 2×4 cores
  • Ensure that ALL prerequisites software’s are installed on all the nodes in the cluster(IMPORTANT)
  • Ensure the SCDPM Server is updated. All patches should be installed
  • Have Installed a Raid 10 for the Storage Pool, as you cannot have the OS not the DPM installed on the disk that is dedicated to the storage pool, which is a set of disks on which the DPM server stores the replicas and recovery points for the protected data.
  • Check if the Tape library is compatible/recognized by Windows 2008 R2 ( VERY IMPORTANT!). Don’t try to use non signed drivers. The server will freeze when you most needed it.
  • Use a hardware VSS writer as you are using a CSV(IMPORTANT)
  • Have System Center Monitor in place
  • Install the Hyper-V role in your SCDPM Server from a command line instead of using Server Manager.  This will enable DPM to manage/automate Item Level Recovery(ILR)
  • Install the SCOM agent to monitor your SCDPM server. Install the SCDPM Management pack. Monitor the SCDPM SQL Databases
  • Backup the SCDPM SQL  Databases ( IMPORTANT )
  • Enable the SCDPM Alerts

Tips :

  • Tapes : By default you are unable to restore data from a expired tape. Also the recatalog option is disabled for expired tapes
  • Page File : 0.2 percent of the combined size of all recovery point volumes, in addition to the recommended size (generally, 1.5 times the amount of RAM on the computer)

 

Categories: Virtualization

Backing Up Virtual Machines on CSV with Hardware VSS Providers, Set to Register KEY

July 12, 2010 Leave a comment

If you are using a hardware VSS provider, you can back up multiple virtual machines from the same CSV/node in the cluster.

To allow a maximum of three backups to run concurrently on each node, specify the number of concurrent backups that can run from a node.

Set the following registry key:

Key
HKLMSoftwareMicrosoftMicrosoft Data Protection Manager2.0ConfigurationMaxAllowedParallelBackups

Value Microsoft Hyper-V

Data 3

Type DWORD

Microsoft does not recommend that you do not use a value greater than 3 for optimal performance

Categories: Uncategorized

Backing Up Virtual Machines on CSV with the System VSS Provider : Recommendations

July 12, 2010 Leave a comment

If your SAN vendor does not have hardware VSS providers, you can use software snapshots to back up your virtual machines.

We recommend that virtual machines deployed on CSV should be backed up serially.

There are two aspects to serialization of backup jobs in a CSV environment:

  • Serializing virtual machine backups on a per node basis.

To ensures that only one backup job will run at a time on a Hyper-V host, create the following registry key on the DPM server:

Key

HKLMSoftwareMicrosoftMicrosoft Data Protection Manager2.0ConfigurationMaxAllowedParallelBackups

Value

Microsoft Hyper-V

Data

1

Type

DWORD

 

  • Serializing virtual machine backups on a per CSV LUN basis.

This form of serialization limits the number of virtual machine backups happening on a single CSV LUN. This is done by creating a DataSourceGroups.xml file and placing it in the DPM server at %PROGRAMFILES%Microsoft DPMDPMConfig. This file provides DPM with information about the CSV virtual machine deployment configuration/distribution on the various CSV LUN so as to serialize the backups that happen per CSV LUN.

For more information about how to generate the file http://technet.microsoft.com/en-us/library/ff634192.aspx

Categories: Uncategorized

Number of Hosts and Virtual Machines Supported by SCVMM 2008 R2

July 7, 2010 Leave a comment

The maximum number of hosts and virtual machines tested with and supported by VMM on the highest recommended hardware configuration is 400 hosts and 8,000 virtual machines.

If your VMM implementation has over 150 hosts, we strongly recommended that you enable server-optimized garbage collector (GC) on the VMM server instead of the default workstation garbage collector. This can significantly reduce the CPU utilization on the VMM server and improve your performance for parallel VMM operations.

To enable server-optimized garbage collector (GC) on the VMM server, create a file that is named vmmservice.exe.config by using the following code, and then for VMM 2008, place it into the %SYSTEMDRIVE%\Program Files\Microsoft System Center Virtual Machine Manager 2008\Bin directory on the VMM server, or for VMM 2008 R2, place it into the %SYSTEMDRIVE%\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Bin directory on the VMM server..


<configuration>
   <runtime>
      <gcServer enabled="true"/>
   </runtime>
</configuration>

The number of virtual machines that can be run on a host is primarily limited by the configuration of the host and of the virtual machines on the host.

Categories: Virtualization

SCVMM 2008R2 Hardware Requirements

July 7, 2010 1 comment
Some folks asked me about the requirements to install SCVMM 2008R2. So, based on SCVMM 2008R2 documentation, recently updated :
 

 

The minimum and recommended hardware requirements for the VMM server depend on the number of hosts that you manage and whether you use the same computer for the VMM server, the VMM database, and as a library server.

 

 

The minimum and recommended hardware requirements to install and operate all VMM components on a single computer are listed in the following tables based on the number of hosts that you manage.

From 5 to 10 hosts

 

Hardware component

Minimum

Recommended

Processor

Pentium 4, 2 GHz (x64)

Dual-Core Pentium 4, 2 GHz (x64) or greater

RAM

2 GB

2 GB

Hard disk space

10 GB

40 GB

 

From 11 to 20 hosts

 

Hardware component

Minimum

Recommended

Processor

Pentium 4, 2.8 GHz (x64)

Dual-Core Pentium 4, 2.8 GHz (x64) or greater

RAM

2 GB

4 GB

Hard disk space

10 GB

50 GB

 

Managing up to 150 hosts

 

Hardware component

Minimum

Recommended

Processor

Pentium 4, 2 GHz (x64)

Dual-Processor, Dual-Core, 2.8 GHz (x64) or greater

RAM

2 GB

4 GB

Hard disk space (without a local VMM database)

2 GB

40 GB

Hard disk space (with a local SQL Server 2005 Express Edition database)

10 GB

50 GB

Note

For the SQL Server 2005 Express Edition, the database size is limited to 4 GB.

Hard disk space (with a local, full version SQL Server 2005 database)

80 GB

150 GB

 

Note

If you also use the VMM server as a library server, you need to provide additional hard disk space for storing objects. For more information about the hard disk space requirements for the VMM library, see System Requirements: VMM Library Server.

Managing more than 150 hosts

 

Hardware component

Minimum

Recommended

Processor

Pentium 4, 2.8 GHz (x64)

Dual-Processor, Dual-Core, 3.6 GHz or greater (x64)

RAM

4 GB

8 GB

Hard disk space

10 GB

50 GB

 

Note

For better performance, when you are managing more than 150 hosts, it is recommended that you use a dedicated computer for the VMM server and do the following:

·      Add one or more remote computers as library servers and do not use the default library share on the VMM server.

·      Use a remote, full version of SQL Server for the VMM database.

 

Categories: Virtualization