Lab 1: Installing a Hyper-V 2 Node Cluster - Google Sites

1 downloads 80 Views 576KB Size Report
Iscsi target configured with 500mb Witness disk and 150gb Data disk (Starwind free version was used for this) . ... Sele
Lab 1: Installing a Hyper-V 2 Node Cluster Objectives This lab will show you the steps needed to create a 2 Node hyper-v Cluster with Cluster shared storage. Using the cluster and shared storage you will then go on to create your first virtual machine and Live migrate it from one node to another without ever loosing connection to your virtual machine. Exercise 1 – Core Server Installation and features. Exercise 2 – Cluster Creation Exercise 3 – Cluster Shared Volumes Exercise 4 – Create your first Hyper-V Virtual machine. Exercise 5 – Live Migrate your Virtual Machine. Exercise 6 – Quick Migrate your Virtual Machine.

Pre-requisites a.

1 x Server running Active Directory services, DNS, DHCP, Iscsi Target Software

b.

2 x Hyper-v Cluster Servers

i. LabDc001,192.168.1.1 i. LabC01N01, 192.168.60.98 ii. c.

LabC01N02, 192.168.60.99

Iscsi target configured with 500mb Witness disk and 150gb Data disk (Starwind free version was used for this) . Melio Scala could also be used. i. Witness001 500mb ii.

Clustershared001 150 Gb

Page 1 of 11

1. Core Server Installation and Features. Complete this Task on:

Labc01N01 and Lab01N02 Labc01n01 192.168.1.98 Labc01n02 192.168.1.99

Pre-requisites Windows 2008 R2 Enterprise Full Install

Objectives To install the hardware and software components that makes up a Hyper-V Cluster.

High-level task Start Server Manager Configure Server Name

Details On the Start menu, point to Administrative Tools, and then click Server Manager. Select Change System Properties Select the change button Change the computer name to LabC01N0x Allow the system to restart

Add Server to domain

Select Change System Properties Select the change button Add computer to domain Hyperlab.local

Configure Server Ip

Enable Remote Desktop

1.

On the Start menu, point to Administrative Tools, and then click Server Manager.

2.

Select View Network Connections

3.

Select Properties of your network adapter

4.

Select Properties of TCP/IP Version

5.

Configure IP settings below a.

Ip Address – 192.168.1.x

b.

Subnet Mask 255.255.255.0

c.

DNS Server – 192.168.1.1

d.

Default Gateway 192.168.1.1

1.

On the Start menu, point to Administrative Tools, and then click Server Manager.

2.

Select Configure Remote Desktop

3.

Select “Enable Connections from computers running any version of Remote Desktop.

4.

Ok to continue.

Page 2 of 11

Connect to ISCI Targets

5.

On the Start menu, point to Administrative Tools, and then click ISCSI Intitiator

6.

When prompted to start the ISCSI service select yes.

7.

On the targets windows enter the ip address of you host running the ISCSI target, in our case this is running on 192.168.1.1

8.

Enter 192.168.1.1 and select Quick Connect

9.

This will bring up the 2 targets you created on the ISCSI Target

10. ClusterShared001 11. Witness001 12. Highlight Wintess001 and select connect 13. Select Done 14. From the top menu select the “volumes and Devices Tab” 15. Select Autoconfigure. 16. Close the Iscsi Initiator 17. View Graphic

Initialise and Format Witness Disk

Perform on labc01N01 18. On the Start menu, point to Administrative Tools, and then click Server Manager. 19. Expand the Storage Node on the left hand side 20. Select Disk Management 21. This will list all your disks and you should now see your witness disk you just added as a iscsi target. For this we will assume it is disk 2 but this may very from system to system. 22. View Graphic 23. Right click “disk 2” and select online 24. Right click “disk 2” and select Initialize Disk 25. Select MBR and Ok 26. Right Click the new disk and select new Simple Volume 27. Select Next 28. Select 497MB 29. Select Drive e: Next 30. Quick format the disk with NTFS, label the disk Witness Perform on labc01N02 31. Repeat steps 18 – 22 We now have a witness disk to use to create the cluster

Add Failover cluster Feature

32. On the Start menu, point to Administrative Tools, and then click Server Manager. 33. From the left hand side select Features. 34. Select Add Features, Next 35. Select Failover Clustering, Next 36. Select Install

Page 3 of 11

Add Hyper-V role

1.

On the Start menu, point to Administrative Tools, and then click Server Manager.

2.

From the left hand side select Roles

3.

Select Add Roles

4.

Select Next

5.

Select the Hyper-V Role

6.

Select next

7.

Select the Local Are Connection network adapter

8.

Select Install

9.

Restart The computer when prompted

Page 4 of 11

2. Cluster Creation Complete this Task on:

Labc01N01

Pre-requisites All previous exercises must be complete.

Objectives Create a Hyper-v cluster. Windows Server 2008 R2 includes a Best Practices Analyzer (BPA) for all major server roles, including Failover Clustering. The Cluster Validation tool examines the best practices configuration settings for a cluster and cluster nodes. High-level task Start Failover Cluster Manager

Validate Cluster Configuration

Create Cluster

Details 1.

On the Start menu, point to Administrative Tools, and then click Failover Cluster Manager.

2.

Right Click Failover Cluster Manager on the right hand side and select validate configuration.

3.

Select Next

4.

Enter – Labc01n01,labc01n02 and add

5.

Select Next

6.

Select Run all test

7.

Select Next

8.

Once complete open the Validation Report and confirm there are no serious issues.

9.

Right Click Failover Cluster Manager on the right hand side and select create cluster.

10. Select Next 11. Enter – Labc01n01,labc01n02 and add 12. Cluster name enter : Labc01v01 13. Ip Address enter 192.168.1.100 14. Select next 15. Select Finish 16. Explore your new cluster by expanding the nodes on the left hand side

Page 5 of 11

3. Cluster Shared Volume Creation One of the marquee features in Windows Server 2008 R2, Live Migration, uses the new Cluster Shared Volumes (CSV) feature within the failover clustering role in Windows Server 2008 R2. Server virtualization is provided by a new version of Hyper-V. With CSV, any node in a failover cluster can access the shared storage and any node can host virtual machines, regardless of which node “owns” (or manages NTFS on) the storage Complete this Task on:

Labc01N01 and Labc01N02

Pre-requisites All previous exercises must be complete.

Objectives To configure Cluster Shared volumes to support Live Migration. One of the marquee features in Windows Server 2008 R2, Live Migration, uses the new Cluster Shared Volumes (CSV) feature within the failover clustering role in Windows Server 2008 R2. Server virtualization is provided by a new version of Hyper-V. With CSV, any node in a failover cluster can access the shared storage and any node can host virtual machines, regardless of which node “owns” (or manages NTFS on) the storage

High-level task Connect to ISCI Target

Details 1.

On the Start menu, point to Administrative Tools, and then click ISCSI Initiator

2.

On the targets windows select the Refresh button.

3.

You should see both your ISCSI targets

4.

Highlight ClusterShared001 and select connect

5.

Select Done

6.

From the top menu select the “volumes and Devices Tab”

7.

Select Autoconfigure.

8.

Close the Iscsi Initiator

Initialise and Format

a.

HyperData Disk 9.

Perform on labc01N01

On the Start menu, point to Administrative Tools, and then click Server Manager.

10. Expand the Storage Node on the left hand side 11. Select Disk Management 12. This will list all your disks and you should now see your cluster shared disk you just added as a iscsi target. For this we will assume it is disk 4 but this may vary from system to system. 13. Right click “disk 4” and select online 14. Right click “disk 4” and select Initialize Disk

Page 6 of 11

15. Select MBR and Ok 16. Right Click the new disk and select new Simple Volume 17. Select Next 18. Select 150000 MB 19. Select Drive q: Next 20. Quick format the disk with NTFS, label the disk ClusterSharedData a.

Perform on labc01N02

21. Repeat steps 9-13

Add Disk to cluster

1.

On the Start menu, point to Administrative Tools, and then click Failover Cluster Manager.

Enable cluster shared volumes.

Add Disk to cluster shared volumes

2.

Select the storage node of the cluster right click and select add disk

3.

Select Disk 4 When prompted.

4.

Highlight labc01v01.hyperlab.local on the left hand side.

5.

Select Enable cluster shared volumes from the right hand side

6.

Tick the box and select ok

7.

Select the cluster shared volumes node on the left hand side

8.

Right click and select add storage

9.

Tick the box for cluster disk 2 and select ok

Page 7 of 11

4. Create your first Hyper-v Guest on a Cluster shared volume Complete this Task on:

Labc01N01

Pre-requisites All previous exercises must be complete.

Objectives To create a Virtual guest to demonstrate live Migration and quick Migration features.

High-level task Start Failover Cluster Manager

Create Virtual Machine

Details 17. On the Start menu, point to Administrative Tools, and then click Failover Cluster Manager.

18. Select the Service and Applications Node on the left hand side 19. Right click and select Virtual Machines, New Virtual Machines, labc01n01 20. View Image 21. Select Next 22. Machine name - labscvmm001 23. Tick the box to store the virtual machine in a different location 24. Browse to C:\ClusterStorage\Volume1 (this is the clustered shared volume) 25. Select next 26. Memory Select 1024mb 27. Connections select local area connection from drop down box. 28. Create Virtual disk, change disk size to 55gb 29. Accept path defaults (These should be on C:\ClusterStorage\Volume1) 30. Select Install from ISO and browse to the location of your windows 2008 R2 ISO 31. A warning about the path to the iso for clusters can be ignored.

Start Virtual machine and install OS

32. In the Service and Applications Node you should now see your newly created Virtual machine. 33. Right click on the virtual machine and select “Start Virtual Machine” 34. Right click on the virtual machine and select “Connect” 35. Use this console to install Windows 2008 R2 Enterprise full. 36. Name the machine LabSCVMM001 and join it to the hyperlab.local domain.

Page 8 of 11

5. Live Migration Complete this Task on:

Labc01N01

Pre-requisites All previous exercises must be complete

Objectives Migrate a virtual machine from one node to another, without dropping the connection between client and server.

High-level task Start Failover Cluster Manager

Live Migrate Your VM

Details: 37. On the Start menu, point to Administrative Tools, and then click Failover Cluster Manager.

1.

Open a remote desktop connection to the Virtual Machine you created in Exercise 4 labscvmm001.hyperlab.local

2.

If your Virtual machine has access open the following internet site and play the video: http://www.iis.net/media/experiencesmoothstreaming.

3.

In the Service and Applications Node you should now see your newly created Virtual machine.

4.

Select this machine and right click

5.

Take note of the “Current Owner” this should be labc01n01

6.

Select “Live Migrate Virtual machine to another Node, select labc01n02.

7.

While this running notice that your Remote desktop session is not dropped your session remains connected, the video may skip but continue on.

8.

Once complete take note of the “Current Owner” it should now be labc01n02.

Page 9 of 11

6. Quick Migration Complete this Task on:

Labc01N01

Pre-requisites All Previous exercises must be complete

Objectives Migrate a virtual machine from one node to another by saving its state and restoring its state on another node.

High-level task Start Failover Cluster Manager

Live Migrate Your VM

Details 38. On the Start menu, point to Administrative Tools, and then click Failover Cluster Manager.

9.

Open a remote desktop connection to the Virtual Machine you created in Exercise 4 labscvmm001.hyperlab.local

10. In the Service and Applications Node you should now see your newly created Virtual machine. 11. Select this machine and right click 12. Take note of the “Current Owner” this should be labc01n01 13. Select “Quick Migrate Virtual machine to another Node, select labc01n02. 14. While this is running notices that your Remote desktop session is interrupted. 15. Once complete take note of the “Current Owner” it should now be labc01n02.

Page 10 of 11

Appendix – Screenshots

Disk Layout

ISCSI

New Virtual Machine

Page 11 of 11