Sie sind auf Seite 1von 29

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System

Center Lab Manual

2010 Microsoft Deutschland GmbH

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 2-1: Installing Hyper-V Role


Install Hyper-V Role on Both Physical Computers In this lab you will install and configure the Hyper-V role on your already installed Windows Server 2008 R2 Enterprise Edition. Pair up with a partner from the class. You will be working with this person throughout the course of the labs to ultimately build a working cluster. Note that some steps are being done on both machines and do not necessarily reflect a real-world work scenario. In these cases, the steps are written in a way so that both students may experience the setup. To distinguish between the two physical computers in your team we will refer to one as the primary machine and the other as the secondary machine. Although lab exercises will include both computers, the role of the primary machine will be slightly more involved because it will provide the SCVMM server role. The Primary Machine The primary machine is named HOSTM00 and is a fresh installation. Credentials for this machine are: User name: Administrator Password: Pa$$w0rd (All passwords in this course are Pa$$w0rd) The Secondary Machine The secondary machine is named HOSTM01 and is a fresh installation. Credentials for this machine are: Username: Administrator Password: Pa$$w0rd (All passwords in this course are Pa$$w0rd) *NOTE: The M character represents the table number where the students are located Perform the following steps on both the primary and the secondary machine. Step 1: Log on to the computer 1. Log on using the appropriate Admin credentials provided in the lab introduction. Step 2: Add the Hyper-V role 1. Open Server Manager (ServerManager.msc). 2. From the Roles pane, click Add Roles. 3. From the Add Roles Wizard, click Next. 4. On the Select one or more roles to install on this server page, select Hyper-V, and click Next. 5. On the Introduction to Hyper-V page, click Next. 6. On the Create Virtual Networks page, select the physical network adapter (LanInternal), and click Next. 7. On the Confirm Installation Selections page, click Install. 8. Click Close, and then click Yes to restart. Log on using your Admin credentials. 9. On the Installation Results page, click Close. 10. Open Hyper-V Manager (virtmgmt.msc).

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Step 3: Create virtual network 1. Select your host machine in the left pane. 2. On the Action pane, click Virtual Network Manager 3. A default External Virtual Network with external network device has been created. 4. Select this default External Virtual Network and change the name to Internal Connection. Do not enable VLAN. Click Apply. 5. Click OK. Step 4: Change Hyper-V server default settings 1. On the Action pane, click Hyper-V Settings. 2. The default virtual hard disks and virtual machines settings are created. 3. Change the default folder location for both hard disks and machines to C:\LocalVM, and click Apply. 4. Click OK.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 2.2: Create the Virtual Environment


In this lab you will create a Virtual Machine, a domain controller in Windows Server 2008 R2, and join your physical servers to this domain. Perform the following steps on the primary machine. This machine will now host the Domain Controller virtual machine. Step 1: Install and Configure Windows Server 2008 R2 in a Virtual Machine For this step you will create a new virtual machine using the ISO file that is located in your server 1. Log on to the primary machine as Administrator with the password Pa$$w0rd. 2. Open Hyper-V Manager (virtmgmt.msc). 3. In the Hyper-V Manager console, at the actions panel, select New, and then Virtual Machine 4. In the Before to Begin screen select Next 5. In the Specify Name and Location change the Name to DCVMM and click Next 6. In the Assign Memory change the default for 1024 and then click Next 7. In the Connect Virtual Hard Disk, let the default value and click Next 8. In the Installation Options, select the Install an operating system from a boot CD/DVD-ROM option, and the Image file (.iso) option use the file located at C:\Course\WindowsServer2008R2.iso and click Next 9. To complete the creation of this Virtual Machine click Finish 10. In the Hyper-V Manager, verify that DCVMM0X is selected and the click Start in the Actions panel. 11. Follow the Wizard to install Windows Server 2008 R2 Enterprise Edition in the Virtual Machine Step 2: Configure the Virtual Machine to Install the Domain Controller After the installation of Windows Server 2008 R2, configure the virtual machine with the next characteristics: 1. IP Settings: a. IP Address: 192.168.21.M b. Subnet Mask: 255.255.0.0 c. Default Gateway: 192.168.0.200 d. Primary DNS: 192.168.21.M e. Secondary DNS: 10.1.1.11 2. Name: DCVMM 3. When prompted restart the server. *NOTE: M is the table number where the students are located and X is the number of Student

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Step 3: Add the Active Directory Domain Services server role and install the Domain Controller In this step you will to prepare the domain controller for the environment. 1. After be restarted log in again to the server, close the Initial Configuration Tasks windows (you can select the Do not show this window at logon at this time) 2. The Server Manager console appears, select the Roles node, and in the Details panel select Add Roles 3. In the Before you Begin window, click Next 4. In the Select Server Roles, select Active Directory Domain Services, the Add Roles Wizard appears, click Add Required Features and click Next twice 5. To add the Active Directory Domain Services server role, click Install 6. When the Installation Progress ends, click Close. 7. To promote this machine as a Domain Controller, in the Server Manager expand the Roles node and then click in the Active Directory Domain Services role. 8. In the details panel click in the Run the Active Directory Domain Services Installarion Wizard (dcpromo.exe) link. 9. When the wizard opens, click Next in the Welcome window. 10. Click Next again in the Operating System Compatibility window. 11. In the Choose a Deployment Configuration click in the Create a new domain in a new forest option, and then click Next. 12. Type contosoM.com for the FQDN of the forest root domain field,, and then click Next

13. In the Set Forest Functional Level select Windows Server 2008 R2 from the menu and then click Next. 14. For the Additional Domain Controler Options windows, leave the default selection and then click Next, if a message appears saying that you have a Dynamic Address in your IP configurations, click Yes to accept this and continue. 15. Leave the default paths for the, Location for Database, Log files and SYSVOL, and then click Next 16. In the fields Password and Confirm Password, type Pa$$w0rd as the password, ant then click Next twice 17. Wait until the wizard complete the action to promote de server as the Root forest domain controller and then click Finish 18. To restart the server click Restart Now 19. When the computer restarts, Login as CONTOSOM\Administrator whit password Pa$$w0rd Step 4: Join the Host to the ContosoM.com domain You need to join the HOSTM00 to the domain Perform the following steps on both the primary machine and the secondary machine. First you need to check the communication with the domain. 1. In a Command Prompt ping to the ContosoM.com domain If the ping is not successful ask to your instructor about this problem. 2. Go to the Server Manager and then click the Change System Properties link

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

3. In the System Properties window, click the Change button 4. The windows Computer Name/Domain Changes appears, under Member of choose the Domain option and type contosoM.com in the field, and then clic OK. 5. When ask for credentials type the next: Username: Administrator Password: Pa$$w0rd Click OK 6. A window that gives you the welcome to the ContosoM.com domain appears, click OK twice 7. Click the Close button at the System Properties window, and then click the Restart Now button 8. Wait until the system restarts. Check that although the Domain Controller be a Virtual Machine, the Host can login to domain.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 3-1: Implementing Microsoft System Center Virtual Machine Manager 2008 R2
In this lab you will install SCVMM 2008 R2 Server on one of the cluster nodes and the Administrator Console on both physical Hyper-V hosts. Perform the following steps on the primary machine. This machine will now be the SCVMM server. Step 1: Install and configure SCVMM 2008 R2 server In this beta release, the WAIK prerequisite must be installed manually before the installation of SCVMM Server. 1. Log on to the primary machine as Administrator with the password Pa$$w0rd. 2. Start setup.exe C:\Course \SCVMMR2\setup.exe 3. If a Security Warning prompt pops up, click Run. On the Windows Internet Explorer prompt, click Add and then Add again and then Close. 4. Under Setup, click Server. 5. Accept the license terms, and click Next. 6. Click Next on the next two dialogs. 7. Type a user name and company, and click Next. 8. The Prerequisites Check will verify the present software and hardware components. Click Next. 9. Leave the default Installation Path and click Next. 10. Select Install SQL Server 2005 Express Edition, and click Next. 11. Ensure that Create a new library share is selected and then click Next. 12. Click Next to use default ports for SCVMM 2008 R2 connections (8100, 80, 443). 13. Review the summary of settings and click Install. Click Close when the installation is done. 14. Allow the installer to restart the Virtual Machine Manager service, if not occurred, restart it please. 15. Launch Services and verify that the Virtual Machine Manager service has restarted. If not, manually restart the service.

Perform the following steps on both the primary and secondary machines. Step 2: Install SCVMM 2008 R2 Administrator Console 1. Start setup.exe at C:\Course\SCVMMR2\setup.exe 2. If a Security Warning prompt pops up, click Run. On the Internet Explorer prompt, click Add and then Add again and then Close. 3. Click Administrator Console. 4. Accept the license terms, and click Next. 5. Click Next.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

6. The Prerequisites Check will verify the present software and hardware components (if Microsoft .NET Framework 3.0 and Windows PowerShell 1.0 are not already installed, setup installs the software automatically). Click Next. 7. Leave the default Installation Path, and click Next. 8. Click Next to use the default port setting (8100) for the VMM Administrator Console to communicate with the VMM server. 9. On the Summary of Settings page, click Install. 10. Click Close. 11. Click Exit.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 3-2: Install and Configure Self Service Portal


Perform the following steps on the primary machine. Step 1: Install Self Service Portal on the SCVMM 2008 host 1. In Server Manager, navigate to the Web Server (IIS) role and install the following role services:

Common HTTP features o Static content o Default documents o Directory browsing o HTTP errors

Application development o ASP.Net o Net extensibility o ISAPI extensions o ISAPI filters

Security o Request filtering Management tools o IIS Management Console o IIS Management Scripts and Tools o Management Service o IIS 6 Management Compatibility

2. Open IIS Manager, remove the Default Web Site (port 80). 3. Start the setup.exe at C:\Course\SCVMMR2\setup.exe 4. If a Security Warning prompt pops up, click Run 5. Click Self-Service Portal under Setup. 6. Accept the license terms and click Next. 7. The Prerequisites Check will verify the present software and hardware components. Click Next. 8. Leave the default Installation Path, and click Next. 9. Verify that your hostname is correct in the Virtual Machine Manager server field. This should be HOSTM00.contosoM.com. Click Next. 10. On the Summary of Settings page, click Install. 11. Click Close. 12. Click Exit.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

13. Test the installation. Start Internet Explorer and type http://hostM00. You wont be able to log in yet because access has not been configured. Note: The Virtual Machine Manager Server, Console, and other hosts like Library Server, Microsoft Virtual Server or other Hyper-V Server must all be joined to the Active Directory domain, although the hosts may be in a separate domain from the Virtual Machine Manager server if desired. If separate domains are used, there must be a trust relationship established between the Virtual Machine Manager Server domain and the host domain. The SCVMM server must be a member server. Installation on a Domain Controller is possible but not recommended. (Note: First you have to install a Domain Controller, then SCVMM 2008 R2). Step 2: Import your own Hyper-V Host into Microsoft SCVMM 2008 R2 Server 1. Launch the SCVMM Admin Console from the desktop and connect to your local machine. 2. From the Actions pane, click Add hosts. 3. Verify that the user name is your Admin account, enter the password and then click Next. 4. Type your Hyper-V host FQN or click Hosts server name... and search for the host in the contosoM.com domain. 5. Select your host and click Add and OK. 6. Click Next. 7. In Configuration Settings, select a host group, if required, and then click Next. 8. You do not have to define any new Virtual Machine Paths. Click Next. 9. On the Summary tab, review your specifications and then click Add Hosts. 10. Back in the Virtual Machine Manager, find your server and make sure the Status reads OK.

10

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 3-3: Implement Access Control for Hyper-V Hosts and SCVMM 2008
Access Control with Hyper-V Manager and SCVMM 2008 R2 Server Perform the following steps on both the primary and secondary machines. Step 1: Authorization roles in Hyper-V Note: After the default installation of Hyper-V, only users in the Administrators or Domain Administrators group are able to manage or create Hyper-V and virtual machines. Change the default authorization for a standard domain user (ask the trainer for the standard user account). 1. Start the Authorization Manager Console (azman.msc). 2. Click Action and select Open Authorization Store. 3. Select XML file and select the InitialStore.xml file from %systemdrive%\programdata\microsoft\windows\Hyper-V directory Note: By default this folder is hidden but it can be accessed by typing the path in manually. 4. Click OK. 5. Expand the tree to Hyper-V services, Role Assignments, and select Administrator. 6. Right-click Administrator and select Assign Users and Groups, then From Windows and Active Directory. 7. Select your domain user account (user<X>) and click OK. 8. Close Authorization Manager. 9. Start Local Users and Groups (lusrmgr.msc) and put your domain user account into the Distributed COM Users group. 10. Start WMI control (wmimgmt.msc). 11. Right-click WMI Control and select Properties. Switch to the Security tab. Expand the tree and select the Root\CIMV2 namespace node. 12. Click the Security button. Use Add and add your user<X> account. 13. Back in the Security for ROOT\CIMV2 dialog, click the Advanced button. 14. In the Permissions tab, select your domain user account and click the Edit button. 15. Change the Apply to field to This namespace and subnamespaces and for Remote Enable, select Allow. 16. Choose Apply these permissions to objects and/or containers within this container only and click OK until you are back in the Security tab. 17. Expand the namespace tree and select the Root\virtualization namespace node. 18. Repeat the steps used above. 19. Browse to C: and ensure that your domain user account has full control to LocalVM. 20. Reboot your host machine.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

11

21. Log on as your domain user account (user<X>) . 22. Start Hyper-V Manager and verify that it launches. Due to known issues with Hyper-V, the access control does not function properly. Success with this exercise may be intermittent. 23. Log off from user<X>. Perform the following steps on the primary machine. Step 2: Authorization roles in SCVMM 2008 In SCVMM 2008R2 Server, there are three authorization roles:

Administrator (all SCVMM 2008 R2 actions allowed) Delegated Administrator Role (specialization of the tasks and functions that administrators are assigned) Self Service User (Administrator can delegate this provisioning role to authorized users through a self-service Web portal while maintaining precise control over the management of virtual machines)
1. Log on to the host machine as your domain administrator (Admin<X>). 2. Start the SCVMM Admin Console. 3. On the Connect to Server prompt, connect to HOSTM00:8100. Note: If you are unable to connect with Admin<X> it may be necessary to use ContosoM\Administrator. 4. In Administration, click User Roles and start New user role action. 5. Create a User role name called DelAdmin and then set the Profile to Delegated Administrator and click Next. 6. In the Add members page, add members Admin<X> of your group and click Next. 7. In the Object Scope, select all library and host groups, and click Next. 8. On the Summary page, Create the user role. 9. Click New user role again. 10. Enter a user role name of Selfservice<M>, select Self Service User as the Profile, and click Next. 11. Add the User<X> account and Domain Admins group as user role members, and click Next. 12. Select All Hosts, click Next. 13. Select All task, click Next. 14. Allow users to create new virtual machines, click Next. 15. Do not allow users to store virtual machines, click Next. 16. Click Create. 17. Launch Server Manager and in the right pane under Security Information, click Configure IE ESC.

12

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

18. Turn Off ESC for Administrators and Users. 19. Log off and log on as nwtraders\user<X>. 20. Using Internet Explorer, log on to your self service portal at http://hostM00 with the ContosoM\user<X> or domain administrator account. 21. Notice you can create a New Computer on the left pane. 22. Log off User<X>.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

13

Lab 4-1: Setting up iSCSI Target


For this lab, import and start the iSCSI-Target Server WSSVM in the Hyper-V MMC on the first cluster node. Perform the following steps on the primary machine. Step 1: Import the iSCSI-Target virtual machines 1. Log on as your domain administrator (Administrator). 2. Browse to C:\LocalVM. 3. Right-click the WSSVM and go to Properties. 4. Clear the Read-only check box and click OK. 5. Open Hyper-V Manager (virtmgmt.msc). 6. From the Action pane, click Import virtual machine, and then click Browse. 7. Specify the location of the exported file (C:\LocalVM\WSSVM), and then click Import. 8. From the Action menu in the Virtual Machine Connection window, click Start. 9. Right-click the VM and select Connect. 10. Log on to the WSSVM using wSS2008!. 11. Change the network adapter IP address to 192.168.22.200+M 12. Switch back to the Hyper-V Manager, right-click the WSSVM, and select Settings. 13. Select Network Adapter, change it to Lan-Internal, and click OK. 14. Rename the machine as WSSVMM. 15. Reboot the VM. 16. Switch back to the WSSVMM, log on, and join the machine to the contosoM.com domain. 17. Reboot the VM. Step 2: Disable the Windows Firewall Perform the following steps on HOSTM00, HOSTM02 and WSSVMM. 1. Go to the Control Panel 2. Double click on Administrative Tools 3. Open Windows Firewall with Advanced Security 4. In the root (Windows Firewall with Advanced Security on Local Computer) right click and select Properties 5. On each tab (Domain profile, Private profile, Public profile) in the Firewall State, select Off 6. Click OK to close the window 7. Close the Windows Firewall with Advanced Security window

14

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 4-2: Installing VDS/ VSS Hardware Provider


The purpose of this lab is to install the VDS/VSS Hardware Provider for iSCSI disks for both team computers. Perform the following steps on both the primary and secondary machines. 1. Log off of the host machine. This is required to bypass a problem installation. 2. Log on as ContosoM\Administrator, Pa$$w0rd. Normally this would not be necessary, but this is to avoid a problem with the beta software that follows. 3. To test if a Hardware Provider is installed, open a Command Prompt and then type: DISKRAID If no VDS Hardware Provider is installed on this computer, the output will be: DiskRaid was unable to find any VDS hardware providers installed on this computer 4. To install the VDS Hardware Provider, run the Microsoft iSCSI Target Hardware Providers for Clients setup on both host machine student computers. (Maybe youll need to change the compatibility mode to Run this program in compatibility mode for: Previous version of Windows C:\Course\iscsitargetHw Providers for Clients-x64.msi The typical option will install both hardware providers (VDS and VSS). 5. You then need to specify the user credentials to be used by the providers. These will be used to authenticate with the iSCSI Software Target. The account must have administrator privileges in both servers involved. User Name: ContosoM\Administrator Password: Pa$$w0rd

6. Specifying iSCSI targets: If both the storage and iSCSI-Initiator client are in the same domain, share the same subnet, and have the ability to talk via UDP, the provider will discover the target automatically via mailslots. However, there is a chance that the Microsoft iSCSI Software Target VDS Hardware Provider service may not detect all iSCSI Software Target servers on the network if one or more of the conditions above are not met. To work around the issue, you need to manually add the iSCSI Software Target to be managed by the Microsoft iSCSI Software Target VDS Hardware. 7. To avoid problems in this lab environment, perform the following steps on both host machines: Open Registry Editor and navigate to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WTVDSProv\ WTServers Create a string (REG_SZ) value where the value name is the iSCSI Software Target server name (WSSVMM) and the value is blank. Each partner should have this VM in their list.

8. Restart the VDS service. If VDS is running, you need to restart VDS service so it can use the newly installed hardware provider (you do not need reboot the server, just stop and start the VDS service). You can do this using the Services MMC or using the SC command line:

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

15

> sc stop vds > sc start vds

In command prompt, type: DISKRAID If the hardware provider is loaded, it should load and give you a command prompt. DISKRAID>

Show installed Hardware Provider version: DISKRAID> list providers To list available iSCSI Target SubSystem, type: DISKRAID> list subsystem Select a iSCSI Target: DISKRAID> sel subsystem 0 Show details to iSCSI Target: DISKRAID> detail subsystem End Diskraid: DISKRAID> exit

16

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 4-3: Configure and connect iSCSI-Initiator to iSCSI-Target


Step 1: Install the iSNS server at DCVMM 1. Log on in DVCMM as ContosoM\Administrator, Pa$$w0rd 2. Start the Server Manager console 3. Under Features, right click and select Add Features 4. In the wizard select Internet Storage Name Server and click Next and the Install 5. Wait until the installation complete, and then close all windows. Step 2: Start the iSCSI-Initiator (first configuration) Perform the following steps on both the primary and secondary machines. 1. Each student will launch iSCSI Initiator from Administrative Tools on their host machine. 2. When prompted, click Yes to start service automatically. Also allow it through the firewall. 3. Click the Discovery tab. 4. Under iSNS servers click Add Server and enter the IP address of the iSNS server on your DCVMM, click OK Note: If a message appears, click OK to unblock the service of Microsoft iSCSI to communicate with an iSNS server through Windows Firewall 5. Close the iSCSI Initiator Properties Step 3: Configure the iSCSI-Target 1. On the WSSVMM log on as ContosoM\Administrator, Pa$$w0rd 2. Launch the Microsoft iSCSI Software Target from Administrative Tools 3. In the root (Microsoft iSCSI Software Target) right click and select Properties 4. Under iSNS tab add the ip of DCVMM, click OK to close Properties

1. Right click at iSCSI Targets, and select Create iSCSI Target 2. In the Create iSCSI Target Wizard, in the Welcome screen, click Next 3. Type iSCSI4HA for the iSCSI target name field and for HAVM for the Description field and then click Next 4. In the iSCSI initiators identifiers click the Advanced button 5. In the Advanced Identifiers click the Add button 6. Click Browse button in the Add/Edit Identifier and select the first IQN in the list and click OK 7. Repeat the steps 9 and 10 to add the second IQN 8. In the Advanced Identifiers click OK to close this window 9. Click Next and Finish to close the wizard

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

17

1. Right click in the iSCSI4HA (the new iSCSI Target) and select Create Virtual Disk for iSCSI Target 2. Click Next in the Welcome screen 3. Type C:\forHAVM.vhd in the File: field and then click Next 4. In the Size screen type 1024 in the Size of virtual disk (MB): field, and then click Next 5. Give a description for the virtual hard disk, and click Next 6. Click Finish to ends the wizard Step 4: Start the iSCSI-Initiator (last configuration) Perform the following steps on both the primary and secondary machines. 1. Each student will launch iSCSI Initiator from Administrative Tools on their host machine. 2. In the Targets tab, under the Discovered targets appears two entries, click in the entry that ends with iscsi4ha-target, and click the Connect button. 3. In the Connect to Target, click OK Note: If the connection fails, make sure that all IP addresses are entered correctly. Mistyped IP addresses are a common cause of connection problems.

18

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 4-4: Install Storage Manager for SANs


Install SANs storage manager feature for use with Virtual Disk Service. Perform the following steps on both the primary and secondary machines. 1. Log on as ContosoM\Administrator 2. To add the feature, in Server Manager, click the Features node, and then click Add Features to launch the Add Features Wizard. 3. Select Storage Manager for SANs and install it. The storage subsystems that you want to administer using Storage Manager for SANs must support Virtual Disk Service (VDS). For more information about VDS, see http://go.microsoft.com/fwlink/?linkid=93546 The VDS hardware provider for each storage subsystem must be installed on the server (see Lab 4-2). The storage subsystems must be directly attached to your server or must be accessible over the network.

To use Storage Manager for SANs with an Internet SCSI (iSCSI) subsystem, an iSCSI software initiator such as Microsoft iSCSI Initiator must be installed on the server (see Lab 4-3).
For more information about iSCSI, see http://go.microsoft.com/fwlink/?LinkId=102299

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

19

Lab 4-5: Creating the Cluster


Step 1: Install the failover cluster feature In this step, you will install the failover cluster feature on your machine. Perform the following steps on both the primary and the secondary machine. 1. On the host machine, in Server Manager, under Features Summary, click Add Features. 2. In the Add Features Wizard, click Failover Clustering, click Next and then Install. 3. Follow the instructions in the wizard to complete the installation of the feature. When the wizard finishes, close it. Step 2: Validate the cluster configuration Before you create the cluster, we strongly recommend that you run a full validation test of your configuration. Validation helps you confirm that the configuration of your servers, network, and storage meets a set of specific requirements for failover clusters. Perform the following steps on both the primary and secondary machines. 1. To open the failover cluster snap-in, click Start, Administrative Tools, then Failover Cluster Management. 2. Click Validate a Configuration. 3. Follow the instructions in the wizard to specify the two host machines belonging to your partner and yourself. 4. On the Testing Options page, select Run Only tests I select and click Next. 5. On the Test Selection page, deselect all tests except the Storage tests and click Next. 6. Click Next on the Confirmation page. 7. The Summary page appears after the tests run. To view Help topics that will help you interpret the results, click More about cluster validation tests. 8. While still on the Summary page, click View Report and read the test results. Or, to view the results of the tests after you close the wizard, see SystemRoot\Cluster\Reports\Validation Report date and time.htm where SystemRoot is the folder in which the operating system is installed (for example, C:\Windows). 9. Notice that we have many warnings about storage. 10. Close the report and click Finish. Step 3: Create the cluster We will now create the cluster. Note that all the following steps will be completed on only one of the student machines. So pick one machine and follow through the rest of the steps together.

20

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Perform the following steps on only on the primary machine. 1. In Failover Cluster Management, click Create a Cluster. 2. Click Next on the Before You Begin page. 3. Type both your host machine name and your partners host machine name, and click Next. 4. On the Validation Warning page, select No. I do not require support and click Next. 5. Specify a Cluster name of CFullM. 6. Specify an IP address for the cluster as 192.168.17.22+M and click Next. 7. Click Next to confirm. 8. After the wizard runs and the Summary page appears, to view a report of the tasks the wizard performed, click View Report. 9. Note we receive a warning about the quorum disk. This goes hand-in-hand with our previous warnings about storage. We will now create these disks. Click Finish. 10. Right-click the newly created cluster and select More Actions, Shutdown Cluster, then click Yes.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

21

Lab 4-5: Create Shared LUNs for Both Cluster Nodes


Perform the following on both the primary and secondary machines. 1. Run the Storage Manager for SAN by clicking Storage Manager for SANs from Administrative Tools. 2. To list available iSCSI Target SubSystems, click Subsystems. 3. To create a new iSCSI Target, click LUN Management, in the Actions pane click Manage iSCSI Targets.


Note:

To create a new iSCSI Target, select your iSCSI-Target Server in the drop-down list, and click Add Enter the Target friendly name of iSCSiT<n>. Click Enable for the IP address of your iSCSI-Target server. Click OK.

Ignore the warning: Storage Manager for SANs was able to create the target, but could not add the portal(s) to the target because the operation is not supported by the provider. This is an error in the beta software of VDS hardware provider 3.1.

Click Close Click Refresh in the Actions pane and open the Manage iSCSI Targets... action. The new iSCSI Target should be available. Click Close. Wait until your partner has caught up with you. Launch iSCSI Initiator from Administrative Tools. Click the Targets tab. You should see two machines in the list. Click Log On for both. If you do not see both machines, ensure Lab 4-1 Step 2 has been done correctly. On the Log On to Target dialog box, leave the defaults and click OK. Click OK again.

22

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Perform the following steps only on the same machine used to create a cluster in Lab 4-4 Step 3. 4. Create an iSCSI LUN for the quorum shared cluster disk with the Provision Storage Wizard:

Click Create LUN in the Actions Pane. Click Next on the Before You Begin page. Select your iSCSI subsystem WSSVMM, click Next. Select a LUN type: Simple, click Next. Type a LUN name: Q<M> and specify a LUN size: 1GB, click Next. Select the Friendly iSCSi target. Ensure that both host machines are connected in the bottom pane and click Next, If prompted, ignore the warning from the Provision Storage Wizard and click Yes. Volume Creation: Assign drive letter Q:, click Next. Format - Volume label: Q<M>_Quorum, click Next. Click Create. Click Close.

5. Create an iSCSI LUN for the virtual machine shared disk with the Provision Storage Wizard:

Click Create LUN in the Actions Pane. Click Next on the Before You Begin page. Select your iSCSI subsystem WSSVMM, click Next. Select a LUN type: Simple, click Next. Type a LUN name: V<M> and specify a LUN size: 20GB, click Next. Select the Friendly iSCSi target and click Next. If prompted, ignore the warning from the Provision Storage Wizard and click Yes. Volume Creation: Assign drive letter V:, click Next. Format - Volume label: V<M>_VM, click Next. Create LUN. Confirm that it finished successfully and click Close. Open Computer Management on both host machines and notice the newly created drives in Disk Management. Note: On the host where the LUNs were not created, the disks are not active.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

23

Configure the Quorum and Virtual Machine shared disks Perform the following steps on the same machine used to create the above LUN.

1. Switch back to Failover Cluster Management.


2. Right-click CFullM.contosoM.com and select Start Cluster Service 3. Expand the cluster and select Storage. 4. Under Actions, select Add a disk. 5. You should see both your drives selected. Click OK. 6. Right-click the cluster and select More Actions, Configure Cluster Quorum Settings. 7. Click Next on the Before You Begin page. 8. Select Node and Disk Majority and click Next. 9. Expand both the Cluster Disks and select the quorum disk, Volume: (Q:) and click Next. 10. Click Next on the Confirmation page, and then click Finish.

24

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Lab 5-1: Create a High Availability VM


Perform the following steps on the machine used to create the LUN and the cluster. Step 1: Check which machine is the owner of the storage 1. Launch the Failover Cluster Manager from Administrative Tools 2. Expand the CfullM.contosoM.com node and select Storage 3. In the Details panel, check the name of the owner for the storage. Step 1: Make the virtual machine highly available To make the virtual machine highly available, execute these steps in the machine that is the owner of the storage at this time. 1. Launch Hyper-V manager console. 2. Create a new Virtual Machine. 3. Name the machine HAVM and select Store the virtual machine in a different location. 4. In the Location textbox browse to V: 5. Click Next through the rest of the wizard using the defaults. Step 2: Failover cluster management 1. In Failover Cluster Management, expand your cluster, right-click Services and Applications, and click Configure a Service or Application. 2. The High Availability Wizard opens. Click Next. 3. On the Select Service or Application page, select Virtual Machine from the list and then click Next. 4. On the Select Virtual Machine page, put a check next to HAVM and click Next. 5. Confirm your selection and then click Next again. 6. The wizard configures the virtual machine for high availability and provides a summary. To see the details of the configuration, click View Report. To close the wizard, click Finish. 7. To verify that the virtual machine is now highly available, you can check in either one of two places in the console tree: Expand Services and Applications: The virtual machine should be listed under Services and Applications. Expand Nodes: Select the node on which you created the virtual machine. The virtual machine should be listed under Services and Applications in the Results pane (the center pane).

8. To bring the virtual machine online, under Services and Applications, right-click the virtual machine and then click Bring this service or application online. This action will bring the virtual machine online and start it.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

25

Lab 5-2: Test Failover Cluster with Hyper-V and VM


Step 1: Test an unplanned failover 1. In Failover Cluster Management, select the Node that currently hosts the HAVM. 2. Right-click this node and select More Actions and then click Stop Cluster Service. 3. Click Stop the cluster service to confirm the action. 4. Wait a few moments until you see this node is down. 5. Click the other Node. Notice that the HAVM has switched nodes and is still online.

Technical Deep-dive: Set Up, Migrate, and Maintain a Virtual Environment using Windows Server Hyper-V and System Center Lab Manual

Appendix: Network Configuration


Start IPs: 192.168.22.X IP Host201 HOST2 Storage Host101 Host201 Host301 Host401 Host501 Host601 Host701 Host801 Host901 Host1001 Host1101 Host1201 52 54 56 58 60 62 64 66 68 70 72 74 WSSVM1 WSSVM2 WSSVM3 WSSVM4 WSSVM5 WSSVM6 WSSVM7 WSSVM8 WSSVM9 WSSVM10 WSSVM11 WSSVM12

Mesa 1 2 3 4 5 6 7 8 9 10 11 12

Asiento 1 3 5 7 9 11 13 15 17 19 21 23 2 4 6 8 10 12 14 16 18 20 22 24

Dominio Contoso1 Contoso2 Contoso3 Contoso4 Contoso5 Contoso6 Contoso7 Contoso8 Contoso9 Contoso10 Contoso11 Contoso12

IP DC 151 152 153 154 155 156 157 158 159

HOST1 Host100 Host200 Host300 Host400 Host500 Host600 Host700 Host800 Host900

IP HOST1 51 53 55 57 59 61 63 65 67 69 71 73

IP Storage 201 202 203 204 205 206 207 208 209 210 211 212

IP Cluster 221 222 223 224 225 226 227 228 229 230 231 232

HAVM 121 122 123 124 125 126 127 128 129 130 131 132

160 Host1000 161 Host1100 162 Host1200

Das könnte Ihnen auch gefallen