Virtual Architect

SCOPE Your Infrastructure

Targeting the right servers to virtualize can be challenging the first time around. Using SCOPE can make that process easier and more efficient.

Virtualization is on everyone's mind today-especially vendors'-as a plethora of new products are being released into the virtualization space. With more and more organizations moving into server virtualization, an important and obvious question arises: Which servers should I virtualize?

Ideally, the answer will be every single one of your production servers. The dynamic data center is one where all user-facing resources are virtualized and can be moved from one host server to another to ensure the very highest levels of service. However, you have to start somewhere, and identifying which servers to start with can be challenging.

In production, you'll want to get the best performance from both hosts and virtual machines (VMs). After all, even if your main goal is to improve physical resource utilization, you'll still want to make sure all systems perform at their best. That's why you'll need to look at each virtual service offering, or each workload you'll be virtualizing, one by one.

Where to Begin
The best way to do this is with a structured approach. Begin by performing a comprehensive server inventory in which you identify resource usage, server workload, application configurations and more for each server. Some of the tools for performing this analysis were discussed in the September/October issue ("Roundup: Capacity Planning Tools") and in the July/August Virtual Architect column ("Which Servers Should You Virtualize?"). Once you have the data, look at the workloads themselves to determine where to start.

One good way to do this is to rely on SCOPE, a conceptual tool shown in Figure 1. SCOPE lets you quickly identify which workloads to start with. Begin in the lab-maybe even with the lab machines themselves-and slowly move your virtual workloads into production.

Figure 1
[Click on image for larger view.]
Figure 1. The SCOPE Curve helps determine which servers to virtualize first.

SCOPE is simple to use. It begins with the easiest workloads to convert, then moves upward through the most complex and critical to your business. It divides workloads as follows:

  • systems such as Dynamic Host Configuration Protocol (DHCP) servers. Web servers are ideal in this category because they often run stateless workloads or workloads that are Read-only.
  • Productivity workloads include systems that run printers, file shares, collaboration services such as Office SharePoint Server and other servers that act as front-ends to n-tier applications. Also included is any system used to share applications centrally, such as Terminal Servers.
  • Operational workloads include any system designed to manage your infrastructure. These are often complex implementations, but are still relatively easy to migrate because they often include the capability of transferring a role from one server to another, making the transition from physical to virtual-known as P2V-simpler.
  • Complex workloads include systems that run high-availability or load-balancing services, as well as those that have high I/O throughputs, such as databases. If a system is load balanced, migration is simplified because you can add new VMs with the role and integrate them into the load-balancing cluster. When enough machines have been virtualized, you can decommission the physical nodes. Clustered machines also use this model. For example, with Windows Server 2008, you must migrate clusters from previous versions of Windows Server. Migrating to a cluster made of VMs is just as easy as migrating to a physical cluster. High I/O workloads present a trickier migration, but by the time you get to these workloads, you should be very familiar with the capability of your virtualization infrastructure and with VMs in general.
  • Special workloads are reserved for last, giving you the opportunity to gain experience in the process. These workloads are usually fewer in number and will include items such as business-critical, manufacturing and legacy apps. Here you have to look to special procedures for virtualizing the workload to make sure it still runs properly once converted.
Three Ways to P2V

When you move your workloads, you'll need to convert the physical to the virtual. This can be done in one of three ways:

  • Manual P2V (physical-to-virtual). The first and often the best approach relies on the creation of brand-new virtual machines (VMs) running a stable and standard OS configuration. Depersonalize a machine to use it as the seed machine for workload migrations. Copy the machine and then use a rebranding process to personalize it. Once the new machine is ready, use the workload's own migration process to move the service from the physical machine to the new VM. This creates new and compliant VMs.
  • Semi-Automated P2V. Another approach relies on using a free P2V conversion tool to move the workload as is and move the operating system from within the physical machine to a VM. This process is riskier than the first approach because you need to rely on the operating system's plug-and-play capabilities to update device drivers during the conversion. Unfortunately, this method is sometimes necessary because the workload the machine runs does not include a migration strategy of its own. In many cases, these tools rely on offline conversions where the source machine is taken offline during the conversion process. Because the tool does not offer a fully automated conversion process, some manual operations may be required once the conversion is complete.
  • Fully Automated P2V. The last approach relies on tools that migrate servers over the network without user interaction. These tools provide completely automated conversions and will sometimes support conversion while the target machine is running. Enterprise tools such as these are more expensive, but if you have a lot of systems to convert and you're satisfied that the source OS is stable, they may be the best solution.
P2V is a complex process. Make sure you test it out in the lab before you move any machines into production.

-D.R, N.R.

End Goal
At some point in time, you'll hit the value to business barometer-the point at which conversion takes more effort than normal and you begin to wonder if it's worthwhile. We would argue that conversion of 100 percent of your infrastructure is the goal. Once all systems are converted, you'll have a truly dynamic data center; one where all end user-facing workloads are virtualized, and the only role hardware has in your network is to act as host servers running virtual workloads.

About the Author

Danielle Ruest and Nelson Ruest, both Microsoft MVPs, are IT professionals focused on technologies futures. They are authors of multiple books, including "Microsoft Windows Server 2008: The Complete Reference" (McGraw-Hill Osborne Media, 2008), which focuses on building virtual workloads with Microsoft's new OS.


Virtualization Review

Sign up for our newsletter.

I agree to this site's Privacy Policy.