mcts training kit 70 - 652 server virtualization phần 2 doc

Lesson 3: Implementing Windows Server 2008 for Hyper-V CHAPTER 1 43 REQUIREMENT DESCRIPTION Virtual Hard Disks Fixed and dynamically expanding virtual hard disks are limited in size to 2,040 GB each. The total amount of storage per VM using virtual hard disks is 512 terabytes. The size of pass-through disks—physical disks that are directly linked to virtual machines—is only limited by the operating system running in the VM. Virtual Storage Controllers Up to four IDE connections per VM. At least one IDE device must be assigned to each VM to boot. Up to 4 SCSI connections per VM and up to 64 devices per SCSI connection for a total of 256 possible disk connections. Virtual Machine Snapshots Each VM can have up to 50 snapshots. Virtual CD/DVD Up to three virtual CD/DVD devices can be assigned to each VM. One IDE controller must be reserved for the boot device. Only one VM can access the physical or pass-through CD/DVD device at a time for security reasons. Hyper-V can also access .iso files as virtual CD/DVD devices. Virtual Serial (COM) Ports Each VM can access up to 2 virtual COM ports to communicate with physical devices either locally or remotely through a serial named pipe. Virtual floppy drive Each VM supports up to 1 virtual floppy drive. Hyper-V does not support access to physical floppy devices. Floppy devices must be in the form of .vfd files. Resource pool Resource pools link host servers together to provide high availability for the VMs they run. Because Hyper-V relies on Windows Server 2008 to create resource pools, the maximum number of hosts in a given resource pool is 16 or 16 nodes in a cluster. exaM tIp HYPER-V CHARACTERISTICS Pay close attention to the items in Table 1-6—they are definitely part of the exam. Update alert HYPER-V CHARACTERISTICS Microsoft is constantly updating Hyper-V and other virtualization offerings as they compete with other virtualization vendors. Because of this, many of the values in Table 1-6 have been updated to reflect current Hyper-V capabilities. Yet the exam was created based on the original features of Hyper-V. Pay special attention to the original values cited in this table. For example, the number of supported logical processors and the maximum number of concurrent running VMs are both values that have changed since the creation of the exam and these values have also changed with Hyper-V R2. 44 CHAPTER 1 Implementing Microsoft Hyper-V More Info HYPER-V RAM CALCULATOR Aidan Finn, an MVP in System Center Configuration Manager, put together a handy spreadsheet outlining how to calculate RAM for host servers running Hyper-V. Find it at http://joeelway.spaces.live.com/Blog/cns!2095EAC3772C41DB!952.entry. Note that although there is a significant performance difference between SCSI and IDE disks on physical systems, there is little difference in a virtual environment running on Hyper-V. The VSC running in enlightened guest operating systems provides highly similar throughput for both storage protocols. Therefore, you can configure virtual machines to boot and operate through virtual IDE drives and expect a higher level of performance than on a physical machine configuration. Keep the information in Table 1-6 in mind when selecting host hardware. Ideally, you will configure your hosts so that they will support an appropriate number of virtual machines. Although this number is difficult to determine under most circumstances, you can rely on the rule of thumb that many organizations aim for up to 10 VMs per host; or, you can rely on an assessment tool to assist you in determining how many VMs you should assign to each host server. Using this assessment tool is the next topic in this lesson. Host Server Resource Usage Given the various characteristics of Hyper-V and given the results of your MAP assessments, you can begin to plan for resource usage of your Hyper-V systems. Although Hyper-V can run up to 192 single-processor virtual machines on a host server configuration that includes 24 logical processors, it is highly unlikely that you will actually do so. This is because you must take into consideration the potential overhead of the parent partition. Remember that the parent partition acts as the coordinating orchestrator for all child partition operations and because of this, it has some resource usage overhead of its own. Table 1-7 outlines considerations for the resource overhead of the parent partition. TABLE 1-7 Potential Parent Partition Overhead RESOURCE REQUIREMENT Logical processor core You should reserve at least one logical processor core per host server for the operation of the parent partition. This way, the parent partition will not have to content for processor resources with the child partitions it manages. After all, Hyper-V’s parent partition runs Windows Server 2008 and this operating system actually runs best with two logical processor cores when managing other server roles. Lesson 3: Implementing Windows Server 2008 for Hyper-V CHAPTER 1 45 RESOURCE REQUIREMENT Memory You should reserve at least 512 MB of RAM for the operation of the parent partition if it is running a Server Core installation of Windows Server 2008. 512 MB of RAM is the bare minimum RAM required for Windows Server 2008. If your parent partition is running the full installation, you should allocate between 768 and 1,024 MB of RAM. Once again, you do not want the parent partition to compete for resources with child partitions. However, Microsoft recommends allocating a minimum of 2 GB of RAM for the parent partition because it also hosts drivers and agents and may require more base RAM to operate. In addition, each child partition you run will require 32 MB of overhead memory as well as 8 MB of RAM for any additional memory it has access to. As a rule of thumb, allocate 2 GB of RAM to the parent partition plus 40 MB for each child partition. This will provide the best operation for your Hyper-V host. Hyper-V R2 can rely on Second Level Address Translation (SLAT) which allows it to leverage new processor features to improve performance and reduce the hypervisor load. This will reduce the hypervisor load to about 1 percent of total system memory, letting you allocate more RAM to VMs. Network adapters You should reserve one network adapter for management operations. The parent partition must be connected to this network. A second NIC is required to support virtual machine networking. A third is required if you rely on shared storage for VM storage and you use the iSCSI protocol to access this storage. In addition, if you create a failover cluster, you will need two NICs for the cluster itself: one for public traffic and one for private heartbeat traffic. The public traffic NIC can double as the VM networking NIC. Storage The parent partition is installed as the boot operating system for a Hyper-V server. You can choose from two strategies here. If you use DAS, you should at least mirror two local hard disks to provide a first line of protection for the parent partition. Using DAS, however, means that you must use traditional installation procedures to prepare a new server. With Windows Server 2008, you can also boot the parent partition from remote storage. In this case, you can use your remote storage’s utilities to generate new parent partitions—through duplication technologies—when a new host server is required. 46 CHAPTER 1 Implementing Microsoft Hyper-V Keep the considerations in Table 1-7 in mind when you plan for resource usage on your Hyper-V hosts. Reserving some core resources for the parent partition is a good practice that will hold in good stead over time. Host server operation is critical if you want your VMs to remain stable and in good operational health. Hardware, Software, and Driver Compatibility Ideally, your host server hardware will be listed in the Windows Server Hardware Catalog (http://windowsservercatalog.com). In fact, one of your first preoccupations should be whether you intend to run fault-tolerant host servers to ensure virtual machine availability. If so, you should look to hardware that has been validated for the Failover Clustering service in Windows Server 2008. Fortunately, Microsoft has introduced the Failover Cluster Configuration Program (FCCP) with Windows Server 2008. This program changes the way customers procure hardware for clustering solutions. In this case, manufacturers list validated cluster configurations on their own sites instead of on the Windows Server Catalog site. This helps customers more easily access configurations that have already been completely validated to run Windows Server 2008. A list of partners with validated configurations can be found at http://www.microsoft.com/ windowsserver2008/en/us/clustering-partners.aspx. Partner configurations range from low-cost two-node clusters to more expensive multi-node datacenter configurations. In addition, Windows has historically had instability issues related to driver and software design. In an effort to ensure that Windows Vista and Windows Server 2008 are even more stable than any previous releases of Windows, Microsoft has tightened the driver and software signing requirements for this operating system. Driver and software signing ensures the quality of the components administrators install on their servers and workstations. In fact, the following Windows components now require digital signatures: n x64 versions of Windows Vista and Windows Server 2008 require all components that are loaded into the operating system kernel—the core part of the operating system that runs at ring 0—to include Kernel Mode Code Signing. This ensures that when components operate in the core of the operating system, they are known to behave properly. n Boot start drivers or drivers that load at boot time must all contain an embedded signature. n Any components that are downloaded through Internet Explorer for installation must also be digitally signed. n Any unsigned component requires administrative approval—read operating system procedure override—to install. Therefore, when you choose to install unsigned and potentially unstable software or drivers, you become responsible for making this choice. Digital signing relies on Public Key Infrastructure (PKI) certificates that are embedded within the component. These certificates must originate from a trusted publisher or a publisher that is included in the default Windows and Internet Explorer list of trusted entities. Self-signed and potentially untrusted certificates are not supported. Lesson 3: Implementing Windows Server 2008 for Hyper-V CHAPTER 1 47 Because Hyper-V runs on x64 hardware, it benefits from trusted kernel and other components. Therefore, host servers running Hyper-V should provide stable and robust operation, but only as long as you comply with the guidelines Windows Server 2008 provides. If you opt to install unsigned drivers on your host servers, you can destabilize your host servers. You’ll agree that with host servers running multiple VMs in child partitions, introducing any element that can potentially destabilize them is a pointless exercise. exaM tIp DIGITAL SIGNATURES Watch out for questions related to driver and software signing in the exam. Creating potentially unstable host servers is a pitfall that should be avoided at all costs. Installing Windows Server 2008 As an IT professional focused on Microsoft technologies, you are already familiar with the Windows installation process, and if you have experience with installing Windows Vista, you are also familiar with the installation process for Windows Server 2008. Both use the same installation engine. Windows Server installations are based on the Windows Preinstallation Environment (Windows PE) engine, which is a scaled-down version of Windows that can boot from removable media—CDs, DVDs, or USB disks—and load into RAM to perform bare-metal installation operations. In addition to moving the installation process to integrate with Windows PE, Microsoft has modified the Windows Vista and Windows Server 2008 installation to remove all barriers to installation completion. In previous versions of Windows, administrators were required to provide input into the installation at various stages of the process. Today all input is provided at the beginning of the installation. As soon as all input data is provided, the installation completes on its own. Administrators only need to provide very basic information: n Language to install n Time and currency format n Keyboard or input method Then, after you’ve selected Install Now, you provide the product key for the installation. This product key determines which product will be selected for installation. You then select whether you want to perform a full installation or a Server Core installation, choose the location of the installation—you may have to use advanced functions to create disk partitions—and you’re off and running. Windows now uses an image-based setup (IBS) that copies an installation image to the system disk and then decompresses it to begin the actual configuration based on the discovered devices on the system. Then, when the operating system is installed, you proceed to the actual system configuration: changing administrative passwords, setting firewall configurations, and much more. 48 CHAPTER 1 Implementing Microsoft Hyper-V Identifying Deployment Options As you can see, this installation process is fairly basic. But as a resource pool administrator, you need to delve deeper into the installation process. Basically, resource pool administrators need to determine which process they intend to rely on to create host servers when they are required. In the dynamic datacenter, host servers are provisioned on an as-needed basis when the existing pool of servers can no longer provide adequate resources for the virtual machines you run. Because of the dynamic nature of the datacenter, this provisioning process must be as smooth and as efficient as possible. It may be adequate for a small organization to create new host servers manually because the need seldom arises, but it is unacceptable to do so in larger datacenters. Dynamic systems provisioning must rely on some form of automation. Windows Server 2008 supports four different installation modes: n Manual installation, which must be used at least once to discover how the installation process actually works. This process is then followed with a manual post-installation system configuration. n Unattended installation through automated response files. Windows now relies on a single Unattend.xml file for input into all automated installations. This file can be edited and prepared through the Windows System Image Manager which is part of the Windows Automated Installation Kit (WAIK), a downloadable installation support tool. The advantage of using answer files is that they can provide both pre- and post-installation input and configuration settings, making the process simpler for administrators. n Disk imaging with the System Preparation Tool (SysPrep.exe). This process relies on the creation of a reference computer that is completely configured, then depersonalized through the SysPrep tool. Then, you capture an image of this computer. This image is then used as the installation point for other servers. This process relies on the new Windows image-based installation, but in this case, you use a custom image instead of the default image included in the Windows distribution DVDs. Once again, you rely on the WAIK to create the custom image and an Unattend.xml file or a manual process to customize it each time you deploy it. n Remote installation through the Windows Deployment Services (WDS), one of the 17 default server roles in Windows Server 2008. WDS also relies on custom images, but can remotely deploy them to bare-metal systems. WDS also relies on Windows PE to boot into the installation process for any server that does not already include an operating system. WDS includes several additional features, such as multicast image deployment, distributed deployment structures for complex environments, and granular distribution control, but in most cases, these features are not required for resource pool creation. One additional deployment option is available. If the parent partition for a server is hosted on a SAN and the system is configured to boot remotely from SAN, you can use the SAN’s logical unit duplication tools to create and depersonalize an image of this parent partition. Lesson 3: Implementing Windows Server 2008 for Hyper-V CHAPTER 1 49 Then, when you need to add a new host server, you create a copy of this image, attach it to the new host, customize it, and you have a new host server. In large organizations, this may be the best method to use because it can provide very fast host server provisioning. Resource pool administrators therefore need to identify which process works best for their environments. Smaller organizations may work well with the Unattended installation process, but medium-sized and larger organizations have to look to either the system image or remote deployment process because of the speed of the deployment. Identifying Required Host Server Configurations Resource pool administrators also need to determine how they intend to configure their host servers. Traditionally, host servers are configured in resource pools—or in the case of Windows Server 2008, in failover clusters—so that they can provide high availability for the virtual machines they run. It makes sense: If your host servers run 10 or more virtual machines, you want to make sure that the virtual machines continue to operate no matter what happens to the host server. Using failover clusters, you can move all of these VMs from one cluster node to another through Hyper-V’s Quick Migration feature. Some downtime is associated with this move, but it is better to have a few seconds of downtime than to have all virtual machine services fail. The Windows Server 2008 Failover Cluster service supports two modes (see Figure 1-15): n Single-site clusters Failover clusters use shared storage in a single site to provide high availability. Because all nodes of the cluster are tied to the same shared storage containers, they can provide failover for each other in the event of a hardware failure on a cluster node. n Multi-site clusters Failover cluster nodes are located in different sites and provide multi-site failover services for each other. In this case, each node hosts its own copy of the data and relies on this copy to provide continuity services. Because of this, there is no requirement for shared storage and each node can in fact rely on DAS to host data. Because each node in the cluster must have duplicate data, multi-site clusters must also rely on a replication engine to ensure that all node data is synchronized at all times. This replication engine must be able to duplicate data while it is being used and must therefore be able to replicate open data objects. Right now, multi-site clusters must rely on third-party replication tools. Multi-site clusters can provide better failover support than single-site clusters because if an entire site fails, your services will continue to operate. In addition, multi-site clusters provide simpler host server configuration designs because they can rely on DAS instead of shared storage. DAS is faster and much easier to implement than shared storage. However, multi-site clusters also require the acquisition and implementation of a third-party replication tool and therefore may be cost-prohibitive for certain organizations. 50 CHAPTER 1 Implementing Microsoft Hyper-V Single-Site Cluster Multi-Site Cluster Cluster VLAN Direct-Attached Storage Witness File Share Third-Party Replication Engine Shared Storage FIGURE 1-15 Single- versus multi-site cluster configurations. note LIVE MIGRATION The first iteration of Hyper-V requires downtime to move a VM from one node of the cluster to another. In Windows Server 2008 R2, Microsoft introduces Cluster Shared Volumes (CSV) which will provide support for live migration, or the ability to move a virtual machine from one node to another without downtime. CSVs are a function of shared storage, which means that they will only support single-site clusters. However, resource pool administrators must also take into consideration the support policy for the product they intend to virtualize. Many products find it quite acceptable to rely on host server clustering to provide high availability for the services running in the virtual machine, but some do not. For example, the Microsoft Exchange Server team has posted its official support policy for configuring high availability in virtual machine environments. Remember that virtual machines emulate all of the features of a physical machine and because of this, Windows Server workloads such as Exchange Server can also take advantage of failover clustering within the virtual machines themselves. This is the strategy the Exchange Server team has opted for. They do provide support for both Hyper-V and validated server virtualization platforms, but they do not provide support for host server clustering, nor do they provide support for live migration features. Instead, they provide support for creating a combination of a multi-site cluster in a single site through the Cluster Continuous Replication (CCR) feature of Exchange. CCR provides the replication engine required for the multi-site cluster and all failover processes are maintained by Exchange itself. This strategy limits the Lesson 3: Implementing Windows Server 2008 for Hyper-V CHAPTER 1 51 possibility of losing e-mail data. Host clusters that perform a failover are never aware of the state of an application contained in a VM during the transfer and therefore may cause some data loss. When you rely on Exchange to perform the failover, it will always be aware of the latest state of the Exchange mailbox database. More Info SUPPORTED VIRTUALIZATION FOR EXCHANGE SERVER For more information on the supported Exchange virtualization strategy, look up http://go.microsoft.com/fwlink/?LinkId=124624. Because of these support policies, resource pool administrators will find that they need to create and maintain three different types of host server configurations: n Stand-alone hosts will be required to support certain products when virtualized. n Single-site clusters will be the most common host server configuration. n Multi-site clusters can provide entire site failure protection. Take the time to analyze the support policy for the products you want to virtualize before you make your final recommendations on host server configurations. If you decide—as you should—that you want to create single-site clusters for some of your host server configurations, keep in mind that single-site clusters must use shared storage and that clusters in general must be designed to have spare resources so that they can provide failover for other nodes in the event of a hardware malfunction (see Figure 1-16). In addition, take the time to determine the best method to automate Hyper-V deployment given the needs of your organization. Quorum Disk (Q:) Volume 1 (Service 1) Volume 2 (Service 2) Resources Service 1 Service 2 Service 1 Resources Workloads Service 2 Node 1 Node 2 Workloads FIGURE 1-16 Single-site clusters rely on shared storage. Clusters in general require spare resources in order to provide failover services. 52 CHAPTER 1 Implementing Microsoft Hyper-V More Info CLUSTERING HOST SERVERS AND VIRTUAL MACHINES Fault-tolerance strategies for host servers are covered in Chapter 3, “Completing Resource Pool Configurations,” as you finalize your host server infrastructure. Fault-tolerance strategies for virtual machines are covered in Chapter 10, “Ensuring Virtual Machine High Availability,” as you look to business continuity strategies for your virtualization environment. Practice Prepare for Hyper-V Deployment This practice consists of two exercises. The first exercise looks at the full installation of Windows Server 2008 in preparation for the installation and configuration of the Hyper-V role. The second exercise looks at the installation of Server Core on another server in preparation of the installation and configuration of Hyper-V in a Server Core environment. You will rely on these two machines to perform further exercises as you move through the lessons in this guide. exerc ise 1 Install Windows Server 2008 In this exercise you will install Windows Server 2008 as a full, graphical installation on a host machine. The host machine should be a physical machine and should be configured according to the recommendations outlined in the Introduction. 1. Obtain an installation DVD for Windows Server 2008. Insert this DVD into the drive of your computer system. Ideally, no pre-existing operating system will be found on this server, but if there is one, use the installation to replace it. Note: You can download an evaluation version of Windows Server 2008 from http://www.microsoft.com/ windowsserver2008/en/us/trial-software.aspx. 2. Boot the server and select to boot from the DVD at the prompt. 3. When the Windows Setup screen appears, select English as the language to install, English (United States) as the time and currency format, and US as the keyboard or input method. Click Next. 4. Click Install Now. 5. Do not enter a product key at the product key page. This will let you evaluate Windows Server for up to 60 days and can be extended to 240 days, which should be sufficient for the purposes of preparing for the exam. Click Next. Answer No to the product key insertion prompt. 6. Select Windows Server 2008 Enterprise (Full Installation) and select I Have Selected The Edition Of Windows That I Have Purchased. Click Next. 7. Select I Accept The License Terms and click Next. 8. Choose Custom (Advanced). 9. The next screen lets you prepare custom partitions to host the installation. Because this machine should be linked to shared storage, you can use the entire local partition for the installation. Click Next. 10. The installation proceeds and will reboot the server until the installation is complete. [...]... http://blogs.msdn.com/taylorb/archive /20 09/01/ 12/ ­ yper-v-v2-guesth only-external-networks-add-roles-wizard-changes.aspx for more information Figure 2- 8   Creating a virtual network 6 Review your settings and click Install when ready 7 Click Close when the installation is complete After a dialog box appears, click Yes to restart the computer The Hyper-V role has been installed on this server As soon as the server reboots,... on a Server Core installation? If it is running on a Windows Server 20 08 full installation? Quick Check Answers 1 The server processor must support hardware-assisted virtualization, such as Intel VT or AMD-V, and this setting must be enabled in the BIOS before performing a Hyper-V installation Lesson 3: Implementing Windows Server 20 08 for Hyper-V CHAPTER 1 53 2 Hyper-V can run up to 1 92 single-processor... version of Hyper-V named Microsoft Hyper-V Server 20 08 This version is based on the Standard edition of Windows Server 20 08 and it is ­imited l to 32 GB of RAM Hyper-V Server relies on the Server Core interface Microsoft r ­ ecommends using this version in test and development environments, for basic server consolidation, or in branch office consolidation scenarios n To move to a server virtualization. .. installation of the Hyper-V role However, because the original release of Windows Server 20 08 was shipped 72 CHAPTER 2 Configuring Hyper-V Hosts with a beta version of Hyper-V, you must download and install the appropriate version of update number 950050 Two updates are available The x64 update supports host servers running the Hyper-V role as long as the host server configuration meets Hyper-V requirements... Microsoft Hyper-V,” the Hyper-V installation is a multi-part process Hyper-V was in beta when it shipped with Windows Server 20 08, and as such it needs to be updated before you can run the release to manufacturing (RTM) version of the product This will no longer be necessary when Service Pack 2 for Windows Server 20 08 is released, but for any copies of the original, RTM version of Windows Server 20 08 released... available in the ICT interface As soon as you close the ICT, the Server Manager interface will be launched (see Figure 2- 3 ) 64 CHAPTER 2 Configuring Hyper-V Hosts Figure 2- 3   Using the Server Manager console You can perform additional activities from this console: n Server activation is one of the only activities that is not performed through Server Manager Instead, it is performed in Control Panel by... it relies on the Microsoft NET Framework, which cannot be installed on Server Core because it has GUI d ­ ependencies Note that Microsoft is changing this for Windows Server 20 08 R2, but for now, Windows PowerShell can only perform remote operations on Server Core Lesson 1: Installing the Hyper-V Role CHAPTER 2 67 Figure 2- 4   Server Core requires the old password to change the default Administrator... configuration of the servers as well as the installation of the Hyper-V role After this lesson, you will be able to: n Perform the initial configuration of Windows Server 20 08 This configuration must address both the full and the Server Core installation n Obtain the Hyper-V update n Install and enable the Hyper-V role This lesson also covers the installation and initial configuration of Hyper-V Server, although...E xercise 2 Install Windows Server 20 08 Server Core I n this exercise you will install Windows Server 20 08 as a Server Core installation on a host machine The host machine should be a physical machine and should be configured according to the recommendations outlined in the Introduction 1 Obtain an installation DVD for Windows Server 20 08 Insert this DVD into the drive of... deploying the host servers, preparing the host server and VM management infrastructure, securing and protecting the host servers, and moving on to resource pool and virtual machine administration n The fully functional Hyper-V role can be found in Windows Server 20 08 Standard, E ­ nterprise, and Datacenter x64 editions This role must run on a 64-bit system with both hardware-assisted virtualization and . of Hyper-V named Microsoft Hyper-V Server 20 08. This version is based on the Standard edition of Windows Server 20 08 and it is limited to 32 GB of RAM. Hyper-V Server relies on the Server Core. and will reboot the server until the installation is complete. Lesson 3: Implementing Windows Server 20 08 for Hyper-V CHAPTER 1 53 exerc ise 2 Install Windows Server 20 08 Server Core In this. Microsoft Hyper-V Single-Site Cluster Multi-Site Cluster Cluster VLAN Direct-Attached Storage Witness File Share Third-Party Replication Engine Shared Storage FIGURE 1-1 5 Single- versus multi-site cluster