Lab Exercise 7

Protecting Hyper-V Virtual Machines with ASM/ME

Purpose: Upon Completion of this lab exercise the student will be able use the Dell EqualLogic Auto-Snapshot Manager tool to create application-consistent snapshots of Microsoft Hyper-V Virtual Machines Goals and tasks: Import a previously exported Virtual Machine using Hyper-V Manager Use ASM/ME to create a consistent Smart Copy of the new VM Delete system files from the VM. After damaging the VM, recover the VM from the Smart Copy Create a new volume on the PS Series SAN, and Export the VM to the new volume Import the new VM from the exported VM. Create a new volume, create a VM on that new volume, and install an OS onto the VM Hardware and software requirements: 1. 2. 3. 4. 5. PS Series Storage Array. Active Gigabit Switch Necessary cables to connect the PS Series Storage Array to the network. Host Integration Tools CD PC running GUI.

Terminal Console SQL Server

Lab Exercise 7 Version 3.3

Protecting Hyper-V Virtual Machines with ASM/ME

Page 7-1

I.

Import a previously exported Virtual Machine using Hyper-V Manager

This section of the lab describes the steps needed to import a previously exported Hyper-V VM to a Windows 2008 R2 server running Hyper-V 1. Use Windows Remote Desktop to log in to your assigned server. 2. Close any system configuration screens that may launch automatically when you log in. 3. Run the EqualLogic Remote Setup Wizard, and select Configure this computer to access a PS Series SAN. 4. Create an entry for the production array as follows: Group name: IP Address: VSS CHAP username: VSS CHAP password: GroupC2 172.168.10.81 vssuser eqleqleqleql

1. Open the Microsoft software iSCSI initiator, and select the Configuration tab. Highlight the initiator name (IQN), and copy onto your clipboard (ctrl-c). 2. Log in to the production array. (username: grpadmin, password: eql). 3. Locate your VMs volume a. Server7-VM1, Server8-VM1, etc. 4. Create a new Access Control record for your assigned volume. Select Limit access to iSCSI initiator name and paste the IQN into the entry field (ctrl-v). Press OK to finish. 5. If its not still open, open the iSCSI initiator. Select the Targets tab, and select Refresh. Highlight the volume that contains your VM, and select connect then OK. Close the iSCSI Initiator. 6. Select Start, then right-click on Computer, and select Manage. When the Server Manager window opens, select Disk Management. Locate your new disk (it should be a 35GB volume), and right-click on the Disk n section, and set the disk online. . Windows 2008 should automatically assign the disk a drive letter. Close Server Manager. 7. Press Start, Administrative Tools, and open Hyper-V Manager. (NOTE: The Hyper-V Role has previously been enabled on your system). 8. Make sure that your server name is highlighted, and in the Actions pane on the right side of the window, select Import Virtual Machine... 9. Browse to the disk that you just connected to, and highlight the folder named w2k8r2 -template and press Select Folder. 10. On the Import Virtual Machine window, select the option to Copy the virtual machine (create a new unique ID) and select Import. Ignore any warnings they are due to the fact that the originating (exporting) machine had a slightly different network configuration. 11. Highlight the newly imported VM, and select Start. After the VM has started, double click on its image in the lower part of the Hyper-V Manager window. When the VM window opens, select Action Ctrl-Alt-Del from the pull-down menus. NOTE: It might be a good idea to change the background screen color of the VM to Raspberry Red or Grape Purple, so that you can easily distinguish it from your hardware servers desktop.

Lab Exercise 7

Protecting Hyper-V Virtual Machines with ASM/ME

7-2

12. Give the new VM a unique system name. On the VM, right click on Computer, select Properties, then select Change Settings. Press Change to rename to computer, and give it a new name as follows: Server7-VM1, Server8-VM1, etc. Press OK then Close then Restart to rename and restart your VM. 13. On the VM window pull-down menu, select Actions, then select Insert Integration Services Setup Disk. Installation of the services will automatically start on the VM. Choose the option to Install Hyper-V Integration Services. If Integration Services are already present, the system will not to re-install them, and the process will terminate. 14. In Hyper-V Manager, right-click on the VM name, and rename it too ServerN-VM1, where N is your server number (e.g. Server7-VM1). II. Use ASM/ME to create a consistent Smart Copy of the new VM

In this section of the lab, well use Auto-Snapshot Manager to create a consistent copy of the VM.

1. On the Hyper-V server (not the VM), select Start, All Programs, EqualLogic, and launch AutoSnapshot Manager. (NOTE: if ASM reports No control volume for IP address 172.168.200.x, disregard the message. We are only concerned about the group that holds our Hyper-V VMs, located at 172.168.10.81). 2. In the left-hand column, expand the Applications node, expand the Hyper-V VSS Writer node, and highlight your VM. 3. In the Actions pane on the right-hand side of the ASM window, select Create Smart Copy Set. Accept all the defaults and create a Smart Copy of your Hyper-V VM. 4. Verify that the Smart Copy completes successfully before proceeding. It may take a minute or two to complete the process. III. Delete system files from the VM. Recover the VM from the Smart Copy

This section of the lab we will damage the VM, and then recover it from the previously captured Smart Copy. 1. Shut down the VM, and close Hyper-V Manager. 2. On the host server, navigate to the volume that holds your VM, and delete the .vhd file for the VM. 3. Launch Hyper-V Manager, and attempt to start the VM. Of course, it should fail. 4. If necessary, open Auto-Snapshot Manager. In the left-hand column, under Smart Copies, expand the node for your Hyper-V VM, and select the Smart Copy that you made earlier. 5. Right-click on the Smart Copy and observe the different options. Note that if you select to restore a single machine by name, rather than choosing Restore All, then ASM will clone the Smart Copy and copy all the files related to the VM from the clone back to the production volume. This could take a very long time for a VM with large vhds. For this lab, well use the Restore all function. Do that now. 6. After the restore is complete, start the VM (if necessary) and log back in. Ensure that it functions correctly.

Lab Exercise 7

Protecting Hyper-V Virtual Machines with ASM/ME

7-3

III.

Create a New VM

This section of the lab we will create a brand new VM. Do the following tasks on your Hyper-V server (not your VM): 1. Log in to the production group and create a new volume called Server N-VM2, where N is your server number: a. Name: ServerN-VM2 b. Size: c. 35GB

Access control: the IQN of the Microsoft iSCSI Initiator.

2. Launch the iSCSI initiator, and connect to the new volume. 3. Use Server Manager, Disk Management to: a. Set the new volume Online b. Initialize the new volume c. Create a new Simple Volume 4. In Hyper-V Manager, select New Virtual Machine from the Actions pane on the right -hand side of the window. a. On the Before You Begin screen, choose Next b. On the Specify Name and Location screen: i. Give the new VM a name of ServerN-VM2 (N = server number) ii. Check the box Store the Virtual Machine in a Different Location. Browse to your newly-created volume, and create a new directory called ServerN-VM2. Highlight the new directory, and press Select Folder. When you return to the Specify Name and Location screen, select Next. iii. On the Assign Memory screen, leave the default of 512MB iv. On the Configure Networking screen, leave the default of Not Connected. v. On the Connect Virtual Hard Disk screen, verify that Create a Virtual Hard Disk is selected, and that the disk will be placed on your newly created SAN volume. vi. Set the size of the Virtual Hard Disk to 32GB. vii. On the Installation Options screen, select Install an Operating System from a Boot CD/DVD ROM, then select image file. Browse to the OS image located on your desktop Classfolder. viii. Begin installation of the operating system. Follow the screen prompts until the new VM is operational. 5. Launch ASM (if its not already running). In the upper left corner, right-click on Auto-Snapshot Manager and select refresh. Verify that the new VM is shown, and that you can create a Smart Copy of the VM.

Lab # 7 is completed

Lab Exercise 7

Protecting Hyper-V Virtual Machines with ASM/ME

7-4