Implementing Microsoft Hyper-V on Data ONTAP · PDF fileMODULE 7: MANAGING THE ... – One Active Directory Domain Controller with DNS Server ... E-7 Implementing Microsoft Hyper-V

Exercise GuideContent Version 1.0

Implementing Microsoft Hyper-V on Data ONTAP

NETAPP UNIVERSITY

Implementing Microsoft Hyper-V on Data ONTAP

Exercise Guide Course ID: STRSW-ILT-IMPMSHV-REV01 Catalog Number: STRSW-ILT-IMPMSHV-REV01-EG

NetApp University - Do Not Distribute

E-2 Implementing Microsoft Hyper-V on Data ONTAP: Welcome

© 2016 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.

ATTENTION

The information contained in this course is intended only for training. This course contains information and activities that, while beneficial for the purposes of training in a closed, non-production environment, can result in downtime or other severe consequences in a production environment. This course material is not a technical reference and should not, under any circumstances, be used in production environments. To obtain reference materials, refer to the NetApp product documentation that is located at http://now.netapp.com/.

COPYRIGHT

© 2016 NetApp, Inc. All rights reserved. Printed in the U.S.A. Specifications subject to change without notice.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of NetApp, Inc.

U.S. GOVERNMENT RIGHTS

Commercial Computer Software. Government users are subject to the NetApp, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

TRADEMARK INFORMATION

NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Clustered Data ONTAP, Customer Fitness, CyberSnap, Data ONTAP, DataFort, FilerView, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity, Simulate ONTAP, SnapCenter, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries.

Other product and service names might be trademarks of NetApp or other companies. A current list of NetApp trademarks is available on the Web at http://www.netapp.com/us/legal/netapptmlist.aspx.


http://www.netapp.com/us/legal/netapptmlist.aspx



TABLE OF CONTENTS

WELCOME ........................................................................................................................................................................... E-1

MODULE 1: OVERVIEW OF MICROSOFT HYPER-V ..................................................................................................... E1-1

MODULE 2: INTRODUCTION TO SNAPMANAGER FOR HYPER-V ............................................................................. E2-1

MODULE 3: SNAPMANAGER FOR HYPER-V WITH NAS AND SAN ............................................................................ E3-1

MODULE 4: INSTALLING SNAPMANAGER FOR HYPER-V ......................................................................................... E4-1

MODULE 5: CONFIGURING SNAPMANAGER FOR HYPER-V ..................................................................................... E5-1

MODULE 6: RESTORING VIRTUAL MACHINES WITH SNAPMANAGER FOR HYPER-V .......................................... E6-1

MODULE 7: MANAGING THE INTEGRATED VIRTUALIZED DATA CENTER .............................................................. E7-1




MODULE 0: WELCOME

EXERCISE 1: WELCOME TO IMPLEMENTING MICROSOFT HYPER-V ON DATA ONTAP

In this exercise, you familiarize yourself with your equipment, synchronize system time, and assign a

Network Time Protocol (NTP) time server.

OBJECTIVES

This exercise focuses on enabling you to do the following:

Ensure connectivity to a Data ONTAP cluster

Synchronize system time between the Data ONTAP clusters and the Windows domain controller

Assign a network time server IP address for the Data ONTAP clusters

STUDY-AID ICONS

These four icons are used throughout the exercise to identify steps that require your special attention.

Warning

You should follow all of the exercise steps, but misconfiguring steps labeled with this icon

might cause later steps to not work properly. Check this step carefully before continuing to

the next step.

Attention

Steps or comments labeled with this icon should be reviewed carefully to save time, learn a

best practice, or avoid errors.

Information

Comments labeled with this icon provide additional information about the topic or

procedure.

Knowledge

Comments labeled with this icon provide reference material that gives additional context

that you might find useful.




EXERCISE EQUIPMENT DIAGRAM

Your exercise environment contains the following virtual machines:

Four Windows 2012 R2 Servers

– One Active Directory Domain Controller with DNS Server

– One Windows Server running System Center Virtual Machine Manager (SCVMM) and System Center

Operations Manager (SCOM)

– Two Windows Servers that you will configure as a Windows failover cluster and Hyper-V Servers

Data ONTAP cluster1, a two-node cluster

To connect to the Windows 2012 Server jump host, use the connection information that was assigned to

you by your instructor. From this Windows desktop, you connect to the other servers in your exercise

environment.

Machine Host Name IP Addresses User Name Password

Windows 2012 R2 Server jump

host w2k12 192.168.0.11 LEARN\Administrator Netapp123

Data ONTAP cluster

management logical interface

(LIF)

cluster1 192.168.0.50 admin (case-sensitive) Netapp123

node 1 cluster1-01 192.168.0.51 admin (case-sensitive) Netapp123


SCVMM and SCOM Server SCVMM-

SCOM 192.168.0.6 LEARN\Administrator Netapp123

Windows 2012 R2 Server 1 HyperV-V1 192.168.0.100 LEARN\Administrator Netapp123





TASK 1: ENSURE CONNECTIVITY TO YOUR DATA ONTAP CLUSTER

In this task, you familiarize yourself with the Windows 2012 Server desktop. You ensure connectivity to

the Data ONTAP cluster and verify the health of the Data ONTAP cluster.

STEP ACTION

1. Normally, you see the Start page of your assigned Windows 2012 Server.

If you see the Windows Desktop instead, go to Step 3.

2. On the Windows 2012 Server Start page, scroll down and click the Desktop tile.




STEP ACTION

3. Verify that you see the desktop and that it contains the PuTTY program.

4. To connect to the Data ONTAP cluster UI, you can browse to the NetApp

OnCommand System Manager URL, which is built in to Data ONTAP 8.3.

To connect to the CLI of the Data ONTAP cluster, you use PuTTY. PuTTY is a UI

for the Telnet and Secure Shell (SSH) protocols.

5. Double-click the PuTTY shortcut.




STEP ACTION

6. In the PuTTY Configuration dialog box, verify that the cluster1-mgmt saved session is listed,

and double-click cluster1-mgmt.

7. You can also connect to the Data ONTAP cluster CLI by connecting to any node in

the cluster: cluster1-01 (node 1) or cluster1-02 (node 2).




STEP ACTION

8. The first time you connect, you might receive a PuTTY Security Alert.

If so, click Yes.

9. At the Data ONTAP cluster login prompt, provide the cluster1 credentials:

Log in as: admin

Password: Netapp123

The Data ONTAP cluster CLI prompt and cursor appear.

10. If you have any difficulty logging in to the Data ONTAP cluster CLI, refer to this

table. Ensure that you are using the correct user name and password in the correct

case (both are case-sensitive).

SYSTEM HOST NAME IP ADDRESS USER NAME PASSWORD

Data ONTAP cluster

management logical

interface (LIF)





STEP ACTION

11. Verify that both nodes of the Data ONTAP cluster are healthy and eligible:

cluster show

12. If the health or eligibility of either node is listed as false, alert your instructor.




TASK 2: SYNCHRONIZE SYSTEM TIME FOR WINDOWS DOMAINS

In this task, you manually synchronize the time zone, system date, and time on the Windows 2012 Server

to the system date and time in the Data ONTAP cluster.

STEP ACTION

1. Windows domains must be synchronized to within 5 minutes of all member servers.

If the time of the Data ONTAP cluster is not synchronized with a domain controller,

the Data ONTAP cluster cannot join or remain joined to the Windows domain.

Without synchronization, computers in the Windows domain cannot access resources in the Data

ONTAP cluster, and resources in the cluster cannot access the Windows domain.

In the next steps, you synchronize date and time between the Data ONTAP clusters and the

Windows domain controller. If you verify that the time synchronization is accurate, you might

not need to perform these steps.

2. Display the date and time on the Windows 2012 Server desktop by clicking the time and date

display in the lower-right corner of the desktop window.

3. To view the time zone, date, and time, click Change date and time settings.




STEP ACTION

4. Review the date, time, and time zone on the Windows 2012 Server.

5. In the following steps, you determine what time zone has been configured on your

Data ONTAP cluster and then, if necessary, you change the cluster time zone to

US/Pacific.

Etc/UTC Time Zone

UTC is the primary time standard by which the world regulates clocks and time. UTC is one of

several replacements for Greenwich Mean Time (GMT).

The zoneinfo database, which is a collaborative compilation of time zone information, has a

special area called “Etc.” The Etc area is for administrative zones, particularly for “Etc/UTC,”

which represents UTC.




STEP ACTION

6. Display the configured time zone on the Data ONTAP cluster:

timezone

7. Your Data ONTAP clusters might have a different time zone from the one displayed

in this example. However, your goal is to make the time zone of the Data ONTAP

clusters match the time zone of the Windows domain controller. In the next step,

verify the time zone of the Windows Server.

8. On the Data ONTAP cluster, change the time zone to US/Pacific by entering this case-sensitive

command:

timezone US/Pacific

9. Display the date, time, and time zone in the Data ONTAP cluster:

date




STEP ACTION

10. Compare the date and time on the Windows 2012 Server with the date and time in the Data

ONTAP cluster.

11. If the system date and time are not synchronized to within 5 minutes, correct the Data

ONTAP cluster date.

12. Enter the date command plus the accurate date and time, using the 24-hour time format with

the following syntax:

date [YYYY][MM][DD][HH][MM]




STEP ACTION

13. When you enter the date command on any node in the cluster, the date command

sets the date and time on all nodes in the Data ONTAP cluster.

NTP service synchronizes the date and time for all nodes in the cluster. If an NTP

time server has been configured, all nodes in the cluster remain in time synchronization with the

NTP time server.




TASK 3: ASSIGN AN NTP SERVER FOR CLUSTER1 AND CLUSTER2

In this task, you access the NetApp OnCommand System Manager built-in management program to

assign an NTP for cluster1 and cluster2.

STEP ACTION

1. NetApp OnCommand System Manager is not a separate application but a

management solution that is built in to the Data ONTAP 8.3 operating system.

To access the OnCommand System Manager, you open a browser, connect to the

cluster management LIF, and authenticate with the cluster admin user name and password.


Data ONTAP cluster

management LIF cluster1 192.168.0.50 admin (case-sensitive) Netapp123

2. From the Windows desktop, access OnCommand System Manager:

a. Open Internet Explorer.

b. In the address bar, enter the management LIF IP address of cluster1 as the URL.

3. Click the Continue to this website link.

4. Enter the administrator’s user name and password for cluster1, and then click Sign In.




STEP ACTION

5. In the left navigation pane, click Configuration > System Tools > Date and Time, and click

Edit.

6. In Data ONTAP, the NTP Service is enabled by default. However, you must add the

time servers, and you must also ensure that the hosts you add as time servers have

the NTP Service enabled.

In the next step, you configure the Windows domain controller as the NTP time server.


Windows 2012 Server w2k12 192.168.0.11 LEARN\Administrator Netapp123




STEP ACTION

7. Check the date and time configuration.

If the Time Zone and Time Servers are not configured, in the Edit Date and Time configuration

box, configure the NTP time server:

a. Enter the IP address of the Windows 2012 Server (domain controller) in your exercise

kit.

b. Click Add.

c. Click OK.




STEP ACTION

8. Verify that the domain controller’s IP address has been set as the time server for cluster1.

9. To avoid issues with the CIFS protocol, always assign one of the domain controllers

as the network time server for Data ONTAP clusters. The Data ONTAP cluster NTP

service setting keeps all nodes in the cluster synchronized with Windows domain

time.

END OF EXERCISE


E1-1 Implementing Microsoft Hyper-V on Data ONTAP: Overview of Microsoft Hyper-V


MODULE 1: OVERVIEW OF MICROSOFT HYPER-V

EXERCISE 1: INSTALLING HYPER-V ON WINDOWS SERVER 2012 R2

In this exercise, you install the Hyper-V role on the Windows Servers. You create several Hyper-V virtual

machines (VMs) and install operating systems in the guest VMs.

OBJECTIVES


Install the Hyper-V role on Windows Server 2012 R2

Create Hyper-V VMs

Install operating systems in the guest VMs

STUDY-AID ICONS

These four icons are used throughout the exercise to identify steps that require your special attention.

Warning

You should follow all of the exercise steps, but misconfiguring steps labeled with this icon

might cause later steps to not work properly. Check this step carefully before continuing to

the next step.

Attention

Steps or comments labeled with this icon should be reviewed carefully to save time, learn a

best practice, or avoid errors.

Information

Comments labeled with this icon provide additional information about the topic or

procedure.

Knowledge

Comments labeled with this icon provide reference material that gives additional context

that you might find useful.

EXERCISE EQUIPMENT DIAGRAM

Your exercise environment contains the following VMs:

Four Windows 2012R2 Servers

– One Active Directory Domain Controller with DNS Server

– One Windows Server running System Center Virtual Machine Manager (SCVMM) and System Center

Operations Manager (SCOM)

– Two Windows Servers that you configure as a Windows failover cluster and Hyper-V Servers

Data ONTAP cluster1, a two-node cluster

To connect to the Windows 2012 Server jump host, use the connection information that was assigned to you

by your instructor. From this Windows desktop, you connect to the other servers in your exercise

environment.




Machine Host Name IP Addresses User Name Password

Windows 2012 R2 Server jump

host w2k12 192.168.0.11 LEARN\Administrator Netapp123

Data ONTAP cluster

management logical interface

(LIF)




SCVMM and SCOM Server SCVMM-

SCOM 192.168.0.6 LEARN\Administrator Netapp123






TASK 1: INSTALL THE HYPER-V ROLE

In this task, you establish a Remote Desktop Connection to the jump host in the exercise environment and

install the Hyper-V role on the Windows Servers.

STEP ACTION

1. On the Windows Desktop, click the Start button to toggle the interface to the Windows Modern

UI interface.

2. On the jump host Start window, click the down-arrow icon in the lower-left corner.

3. Right-click the Remote Desktop Connection application.

4. Select Pin to taskbar.




STEP ACTION

5. Return to the Windows Desktop and launch the Remote Desktop Connection application from

the icon on the taskbar.

6. You can use the “Pin to taskbar” procedure to enable easy access to other programs

that you will use frequently in the remaining exercises.

7. Connect to the HyperV-V1 server and log in.




STEP ACTION

8. If you see a dialog box that asks about the trusted certificate, select the Don’t ask me again

checkbox and then click the Yes button.

9. If Server Manager does not start automatically, start Server Manager and click Add roles and

features.

The Add Roles and Features Wizard starts.




STEP ACTION

10. Begin using the wizard:

a. On the Before you begin page, click Next.

b. On the Select installation type page, accept the default setting of Role-based or feature-

based installation and click Next.

c. On the Select destination server page, select HyperV-V1, and then click Next.




STEP ACTION

11. Select the Hyper-V checkbox, click the Add Features button, and then click Next.

12. On the Select features page, click Next, and then click Next again.

13. In the next step, to avoid errors when the Windows failover cluster is created, the

virtual switches must be configured exactly the same way on both nodes.




STEP ACTION

14. On the Create Virtual Switches page, select the Ethernet1 checkbox, and then click Next.




STEP ACTION

15. You should not select Live Migration now, so click Next.

16. The server becomes part of a Windows failover cluster. You will configure live

migration when you create the cluster.

17. On the Default Stores page, click Next.

NOTE: You will change these paths later.

18. On the Confirmation page, select the Restart the destination server automatically if required

checkbox, and when a dialog box appears asking you to confirm the automatic restart, click Yes.




STEP ACTION

19. On the Confirm installation selections page, click the Install button.

20. When the server restarts, the Hyper-V functionality will be active.

Repeat Steps 1 through 19 on the HyperV-V2 server.

21. After the HyperV-V2 server restarts, access a Remote Desktop session on the HyperV-V1

server.

Server Manager starts automatically and displays the Hyper-V installation progress.




STEP ACTION

22. On the Add Roles and Features Wizard page, verify that the installation was successful, and then

click Close.

23. Perform the same step on the HyperV-V2 server.

24. On the HyperV-V1 server, start Server Manager:

a. Click Tools > Hyper-V Manager.

b. In the Hyper-V Manager interface, select Hyper-V Manager and click Action >

Connect to Server.

c. In the “Another computer” field, type the name of server HyperV-V2, and then click

OK.




STEP ACTION

25. Verify that your Hyper-V Manager window looks similar to this example.

26. Optional: You can complete this step on the HyperV-V2 server also, so that both interfaces

look the same.

27. For convenience, you can open a second Remote Desktop window by right-clicking

the Remote Desktop icon and selecting “Open a new window.”




TASK 2: CREATE HYPER-V VMS

In this task, you create Hyper-V VMs on each of the two Hyper-V servers.

STEP ACTION

1. On the HyperV-V1 server, open Hyper-V Manager, and then select HYPERV-V1 > New >

Virtual Machine.

2. When the New Virtual Machine Wizard starts, on the Before You Begin page, click Next.




STEP ACTION

3. On the Specify Name and Location page, name the VM CentOS6.7_V1, and then click Next.

4. The VMs are created on local storage first, then imported to the NetApp shared

folders in a later exercise.

5. On the Specify Generation page, select the Generation 1 option, and then click Next.

6. For more information about Generation 2 VMs, see the Microsoft TechNet article

“Virtual Machine Specifications for Hyper-V in Windows Server 2012 R2.”

https://technet.microsoft.com/en-us/library/dn592184.aspx




STEP ACTION

7. On the Assign Memory page, in the Startup memory configuration box, type 1024, then select

the Use Dynamic Memory for this virtual machine checkbox, and click Next.

8. On the Configure Networking page, from the Connection list, select vmxnet3 Ethernet

Adapter, and then click Next.




STEP ACTION

9. On the Connect Virtual Hard Disk page, accept the default settings and click Next.

10. On the Installation Options page, select the Install an operating system from a bootable

CD/DVD-ROM option.




STEP ACTION

11. Browse to the C:\CourseFiles\Implementing_Hyper-V\ISOs folder, select the

CentOS-7-x86_64.iso file, and then click Next.

12. This configuration enables you to install an evaluation version of Windows Server

2012 R2 in the VM in Task 3.




STEP ACTION

13. On the Summary page, click Finish.

14. Repeat Steps 1 through 13 on the HyperV-V2 server, but name the VM CentOS6.7_V2.




TASK 3: INSTALL OPERATING SYSTEMS IN THE VMS

In this task, you install a Windows Server operating system in each of the VMs that you created in Task 2.

STEP ACTION

1. Open the Hyper-V Manager application on the HyperV-V1 server.

2. This task can be performed simultaneously on both Hyper-V servers.

3. Right-click the CentOS6.7_V1 VM and select Start.

4. Right-click the VM again and select Connect.




STEP ACTION

5. A brief system check occurs before the CentOS 7 installer starts. You might see the

message “Fast TSC calibration failed,” but you can ignore this message. After the

system check, the installer installs CentOS.

6. On the Welcome to Centos 7 page, select the appropriate language and then click Continue.




STEP ACTION

7. On the Installation Summary page, click the Installation Destination icon.

8. On the CentOS installation pages, scroll to the edge of the pages as needed to find

some of the icons that you need to click.

9. On the Device Selection page, click the Msft Virtual Disk icon, and then click Done.

10. You configure the network settings for the VM in a later exercise.

11. When you are returned to the Installation Summary page, in the lower-right corner of the page,

click the Begin Installation button.

12. When the configuration page appears and the installation process begins, you need to set a root

password, so click the Root Password icon in the User Settings section of the page.




STEP ACTION

13. In the Root Password and Confirm boxes, enter the password Netapp123, and then click

Done.

14. The CentOS installation pages are larger than the Remote Desktop pages. Some

scrolling is required to find the buttons. Some of the buttons are located in the top-left

part of the page, and others are located in the bottom-right corner of the page.

15. When you are returned to the Configuration page and the installation is complete, click the

Finish configuration button.

16. Some final installation tasks are performed on the Configuration page.

When the tasks are finished, click the Reboot button in the lower-right corner of the page.

17. After the operating system reboots and a login prompt appears, you can disconnect from the

VM.

18. Close the connection to CentOS6.7_V1 and leave the guest operating system running.

19. If necessary, repeat Steps 1 through 18 to install the CentOS operating system on the

CentOS6.7_V2 VM on the Hyperv-V2 server.

END OF EXERCISE


E2-1 Implementing Microsoft Hyper-V on Data ONTAP: Introduction to SnapManager for Hyper-V


MODULE 2: INTRODUCTION TO SNAPMANAGER FOR HYPER-V

There is no exercise for this module.


E3-1 Implementing Microsoft Hyper-V on Data ONTAP: SnapManager for Hyper-V with NAS and SAN


MODULE 3: SNAPMANAGER FOR HYPER-V WITH NAS AND SAN

EXERCISE 1: PREPARING STORAGE AND NETWORKING FOR INSTALLATION

In this exercise, you verify that all necessary licenses on the clustered Data ONTAP controllers are installed.

You create a storage virtual machine (SVM), FlexVol volumes, SMB shares, and a network interface failover

group. You create the necessary records in DNS, create a Windows failover cluster, and configure the Hyper-

V virtual machines (VMs) to be highly available.

OBJECTIVES


Connect to the Data ONTAP system and verify that the licenses are installed correctly

Create aggregates, FlexVol volumes, and SVMs on the Data ONTAP system

Create necessary DNS records for the NetApp SVM

Create and configure a Windows failover cluster

Configure highly available VMs




TASK 1: VERIFY THAT THE CORRECT LICENSES ARE INSTALLED

In this task, you use OnCommand System Manager to verify the licenses that are installed on the Data

ONTAP controllers.

STEP ACTION

1. In the exercise environment, open a Remote Desktop Connection to your jump-host computer

and log in with the credentials provided by the instructor.

2. Click the Internet Explorer tile.




STEP ACTION

3. In the address bar, enter the management logical interface (LIF) IP address of cluster1 as the

URL, and then click the Continue to this website link.

4. Log in with the user name admin and the password provided by the instructor, and then click

Sign In.




STEP ACTION

5. Verify that the window looks similar to this example:

6. In next step, make sure that all six of the licenses are installed on both high-

availability nodes and that no risks are shown.

7. In the navigation pane, expand cluster1 > Configuration > System Tools > Licenses and

confirm that the following licenses are already installed:

Cluster Base License CIFS License

SnapRestore License SnapMirror License

FlexClone License SnapManagerSuite License

8. If necessary, obtain license codes from the instructor and add the license codes.




TASK 2: CREATE NETWORK SETTINGS AND CREATE AN SVM

In this task, you use OnCommand System Manager to create an IP subnet, an SVM on the NetApp cluster.

STEP ACTION

1. In OnCommand System Manager, expand the Cluster group.

2. In the navigation pane, click cluster1 > Configuration > Network.

3. On the Subnets tab, click Create.

The Create Subnet wizard starts.

4. Configure a new subnet as follows, and then click the Create button:

Name: HyperV_Subnet

Subnet IP/Subnet mask: 192.168.0.0/24

IP Addresses: 192.168.0.75-192.168.0.99

Gateway: 192.168.0.1

Broadcast Domain: Default

5. To create an SVM, in the navigation pane, expand the Storage Virtual Machines group and

click Create.

The Storage Virtual Machine (SVM) Setup wizard starts.




STEP ACTION

6. Complete the wizard with this information:

SVM Name: hv_svm

IPspace: Default

Volume Type: FlexVol volumes

Data Protocols: CIFS

Default Language: C.UTF-8

Security Style: NTFS

Root Aggregate: aggr1_node1

Search Domains: learn.netapp.local

Name Servers: 192.168.0.11

7. Click Submit & Continue.




STEP ACTION

8. When the Configure CIFS protocol configuration page appears, configure the CIFS protocol

with this information:

Subnet: HyperV_Subnet

IP address option: Auto-select the IP address from this subnet

Port: cluster1-01:e0d

CIFS Server Name: hv_storage

Active Directory: learn.netapp.local

Organizational Unit: CN=Computers

Administrator Name: administrator

Administrator Password: Netapp123





STEP ACTION

10. Configure the SVM Administration with this information:

User Name: vsadmin

Password: Netapp123

Select checkbox: Create a new LIF for SVM management


IP address option: Auto-select the IP address from this subnet

Port: cluster1-01:e0e





STEP ACTION

12. Verify that the New Storage Virtual Machine (SVM) Summary page appears, and then click

OK.

13. Expand the Cluster group and click cluster1 > Configuration > Network.

14. Click the Network Interfaces tab, and for reference, write down the IP address for the

hv_svm_admin_lif1 interface.

15. You will use this IP address when you install SnapDrive for Windows.




TASK 3: CREATE FLEXVOLS

In this task, you use OnCommand System Manager to create FlexVol volumes to be used for the Windows

failover cluster and the Hyper-V server’s VM storage. This task is performed on the jump-host server.

STEP ACTION

1. In OnCommand System Manager, expand the Storage Virtual Machines group, click cluster1

> hv_svm > Storage > Volumes, and then click Create.

The Create Volume wizard begins.

2. To create a FlexVol volume, enter these configuration settings:

Name: FileShareWitness

Aggregate: aggr1_node1

Storage Type: NAS

Size: 1 GB

Snapshot Reserve %: 5

3. Select the Thin Provisioned checkbox and click Create.




STEP ACTION

4. Using the information in the table, create three additional FlexVol volumes.

Name Aggregate Storage Type

Size Snapshot Reserve

Thin Provisioned

HyperV1_VMs aggr1_node1 NAS 16 GB 5% Yes

HyperV2_VMs aggr1_node2 NAS 16 GB 5% Yes

SMHV_SnapInfo aggr1_node1 NAS 16 GB 5% Yes

5. Verify that your window looks similar to this example:




STEP ACTION

6. To turn off the automatic Snapshot Copy schedule, perform these actions:

a. Select the HyperV1_VMs volume, and then click Snapshot Copies > Configure.

b. Clear the Enable scheduled Snapshot Copies checkbox.

c. Click OK.

7. Repeat Step 6 for volumes HyperV2_VMs and SMHV_SnapInfo.

8. To create an SVM export policy, on the jump host, open PuTTY, and open a session to cluster1-

mgmt.

9. Log in with the admin credentials.

10. At the command line, enter this command:

cluster1::> vserver export-policy create –vserver hv_svm

–policyname SMB




STEP ACTION

11. Create a rule for the SMB export policy:

cluster1::> vserver export-policy rule create –vserver hv_svm

–policyname SMB –ruleindex 1 –protocol cifs –clientmatch

<IP_address_of_HyperV-V1_Server> -rorule sys –rwrule sys

–superuser sys –allow-suid false

12. Create another rule for the SMB export policy:

cluster1::> vserver export-policy rule create –vserver hv_svm

–policyname SMB –ruleindex 2 –protocol cifs –clientmatch

<IP_address_of_HyperV-V2_Server> -rorule sys –rwrule sys

–superuser sys –allow-suid false

13. To assign the export policy to the SVM root volume, at the command line enter this command:

cluster1::> volume modify –vserver hv_svm –volume hv_svm_root

–policy SMB

14. In OnCommand System Manager, in the Storage Virtual Machines group, click cluster1 >

hv_svm > Policies > Export Policies.

15. In the Policy pane, select SMB and click the Assigned Objects tab.

You should see the hv_svm_root volume displayed as an assigned object to the SMB policy, and

your window should look similar to this example:




STEP ACTION

16. Click the Export Rules tab.

Your window should look similar to this example:

TASK 4: CREATE SMB SHARES

In this task, you create SMB shares for each of the volumes that you previously created.

STEP ACTION

1. In OnCommand System Manager, open the Storage Virtual Machines group and click cluster1

> hv_svm > Storage > Shares.

2. Click Create Share.

The Create Share wizard starts.




STEP ACTION

3. Click the Browse, expand the root folder, select the FileShareWitness folder, and then click

OK.

4. Select the Enable continuous availability for Hyper-V and SQL checkbox and click Create.

5. Repeat Steps 1 through 4 to create shares for the following folders:

HyperV1_VMs

HyperV2_VMs

SMHV_SnapInfo




STEP ACTION


7. Right-click the HyperV1_VMs share and select Edit.

8. It is very import to configure CIFS shares properties correctly.




STEP ACTION

9. Configure this share as follows:

Permissions tab: Everyone - Full Control

Options tab, Symbolic Links: Enable as read/write

Selected checkboxes: Enable Oplocks and Browsable only

10. Click Save and Close.

11. Repeat Step 9 for all the CIFS shares that were created in this task.

12. In task 9 you will modify the CIFS share permissions to include machine accounts.




TASK 5: CREATE NETWORK INTERFACE FAILOVER GROUP

In this task, you create a network interface failover group for the SVM data LIFs.

STEP ACTION

1. In OnCommand System Manager, expand the Cluster group, click cluster1 > Configuration >

Network, click the Network Interfaces tab, and click Create.

The Create Network Interface wizard starts.

2. Configure a new network interface as follows:

Name: hv_svm_cifs_lif2

Interface Role: Serves Data

SVM: hv_svm

Protocol Access: CIFS

Management Access: Enable Management Access


Autoselect the IP address from this subnet

Port: cluster1-02:e0d

Dynamic DNS: Enable Dynamic DNS




STEP ACTION

3. Click Create.

4. Open a PuTTY session to cluster1-mgmt and log in with the admin credentials.

5. At the command line, type:

cluster1::> network interface failover-groups create –failover-

group fg_hv_svm –vserver hv_svm –targets cluster1-

01:e0d,cluster1-02:e0d

6. Verify that the failover group was created correctly:

cluster1::> network interface failover-groups show

The output should look similar to this example:

Failover

Vserver Group Targets

------- --------- --------------------------------

hv_svm fg_hv_svm cluster1-01:e0d, cluster1-02:e0d

TASK 6: CREATE DNS RECORDS FOR THE SVM AND CIFS SERVER

In this task, you create DNS entries for the SVM admin LIF and the CIFS server LIF.

STEP ACTION

1. On the jump host, open Windows Server Manager and click Tools > DNS.

2. In the DNS interface, click DNS > W2K12 > Reverse Lookup Zones and then click Action >

New Zone.

The New Zone Wizard starts.

3. On the opening Welcome page, click Next.




STEP ACTION

4. On the Zone Type page, accept the default settings and click Next.

5. On the Active Directory Zone Replication Scope page, accept the default settings and click

Next.




STEP ACTION

6. On the Reverse Lookup Zone Name page, leave the IPv4 option selected and click Next.

Another Reverse Lookup Zone Name page appears.

7. In the Network ID field, type 192.168.0 and click Next.




STEP ACTION

8. On the Dynamic Update page, accept the default settings and click Next.

9. On the final page, click Finish.




STEP ACTION

10. In the DNS interface, expand DNS > W2K12 > Forward Lookup Zones > learn.netapp.local

and click Action > New Host (A or AAAA).

11. Complete the New Host configuration window as follows:

Name: hv_storage

IP address: 192.168.0.77 (IP address of the SVM CIFS server)

Selected checkbox: Create associated pointer (PTR) record

12. Click Add Host.

13. When a message window appears indicating that the host record was successfully created, click

OK.




STEP ACTION

14. On the New Host configuration page that remains open, configure another host record as

follows:

Name: hv_svm

IP address: 192.168.0.76 (IP address of the SVM admin LIF)

Be aware that the IP address used in this step is the SVM management LIF.

15. After adding the hv_svm host record, click Done and close DNS Manager.

16. These DNS entries allow forward and reverse lookups to be successful for Windows,

SnapDrive, and SnapManager.

TASK 7: PREPARING THE HYPER-V CONFIGURATION FOR FAILOVER CLUSTERING

STEP ACTION

1. The Hyper-V virtual switch names are required to be exactly the same for the

Windows failover cluster installation to succeed.

2. Open a Remote Desktop Connection, and open Hyper-V Manager on either the HyperV-V1 or

HyperV-V2 server, and select the HyperV-V1 server.

NOTE: If you are on the HyperV-V2 server, you must add the HyperV-V1 server to the Hyper-

V Manager interface.

3. In the Actions pane, select Virtual Switch Manager.

4. Select the vmxnet3 Ethernet Adapter.




STEP ACTION

5. In the Virtual Switch Properties pane, configure the virtual switch to use Ethernet Adapter #3,

change the name of the virtual switch to match, and click OK.

6. In the Apply Networking Changes window, click Yes.

7. In the Virtual Switch Manager for HyperV-V1 window, click OK.

8. Check the virtual switch configuration of the HyperV-V2 server.

The virtual switch configuration should match exactly with the HyperV-V1 server.




TASK 8: CREATE A WINDOWS FAILOVER CLUSTER

In this task, you create and validate a dual-node Windows failover cluster.

STEP ACTION

1. On the HyperV-V1 server, start Windows Server Manager.

2. In the Server Manager Dashboard interface, click Add Roles and Features.

The Add Roles and Features Wizard starts.

3. On the Before You Begin page, click Next, and on the Select installation type page, click Next.

4. On the Select destination server page, select HyperV-V1.learn.netapp.local and click Next.

5. On the Select server roles page, click Next.




STEP ACTION

6. On the Select features page, select the Failover Clustering checkbox and click the Add

Features button.

7. When the Select Features page reappears, click Next.

8. On the Confirmation page, click the Install button.




STEP ACTION

9. On the Installation progress page, verify that the installation was successful, and click Close.

10. Repeat Steps 1 through 9 on the HyperV-V2 server.

11. In the Remote Desktop Connection to the HyperV-V2 server, click Tools > Failover Cluster

Manager.

12. In the Actions pane, click Validate Configuration and, when the Validate a Configuration

Wizard starts, click Next.




STEP ACTION

13. On the Select Servers or a Cluster page, click the Browse button.

14. On the Select Computers page, type HyperV-V1 in the dialog box, click Check Names, and

then click OK.

The HyperV-V1 server name is underlined.

15. Repeat Steps 13 and 14 to add the HyperV-V2 server.




STEP ACTION

16. Verify that your window looks similar to this example, and then click Next.

17. Select the Run all tests option and click Next.

18. On the Confirmation page, click Next.




STEP ACTION

19. Review the Overall Result to verify that the configuration is suitable for clustering, and then

click the Finish button.

20. When the Create Cluster Wizard starts, on the Before You Begin page, click Next.




STEP ACTION

21. Enter the cluster name HVServerCluster and the IP address 192.168.0.102, and then

click Next.

22. It is important that the IP address for the cluster is a unique address on the network.




STEP ACTION


24. Click Finish.




STEP ACTION

25. In the Failover Cluster Manager interface, expand HVServerCluster.learn.netapp.local and

click Nodes.


TASK 9: COMPLETE THE PERMISSIONS LIST ON THE CIFS SHARES

In this task, you add permissions to the CIFS shares that you created in Task 4.

STEP ACTION

1. Open a PuTTY session to cluster1-mgmt and log in with the admin credentials.

2. At the command line, type:

cluster1::> vserver cifs share access-control create –vserver

hv_svm –share FileShareWitness –user-or-group hyperv-v1$ -user-

group-type windows –permissions full_control

3. Using the same command, add the HyperV-V2 server and the HVServerCluster to the share

permissions.

Remember to append the server name with a dollar ($) sign.

4. Repeat Steps 1 through 3 to add the same permissions to the shares with these share names:

SMHV_SnapInfo

HyperV1_VMs

HyperV2_VMs




STEP ACTION

5. To check your work, verify that OnCommand System Manager displays each share’s

permissions exactly like this example:

6. Usually, the SnapDrive for Windows service account is added to the share permissions

instead of the Everyone account.

TASK 10: CONFIGURE THE WINDOWS FAILOVER CLUSTER ON CLUSTERED DATA ONTAP

In this task, you configure the Windows failover cluster to use the CIFS shares that were created in Task 3.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server.

The Server Manager application might still be running from a previous task.

2. If necessary, start Server Manager and click Tools > Failover Cluster Manager.




STEP ACTION

3. Select HVServerCluster and click Action > More Actions > Configure Cluster Quorum

Settings.

4. On the Before You Begin page, click Next.

5. On the next page, select the Select the quorum witness option and click Next.




STEP ACTION

6. On the Select Quorum Witness page, select the Configure a file share witness option and click

Next.




STEP ACTION

7. On the Configure File Share Witness page, click the Browse button, type the server name

hv_storage, and click the Show Shared Folders button.

8. The server name that you are using is the CIFS server name on the Data ONTAP SVM.

9. Select the FileShareWitness share and click OK.




STEP ACTION

10. On the Configure File Share Witness page, click Next.





STEP ACTION

12. On the Summary page, verify that the configuration was successful, and then click Finish.

13. Leave the Failover Cluster Manager application open for the next task.

TASK 11: CONFIGURE HIGHLY AVAILABLE VIRTUAL MACHINES

In this task, you configure the previously created VMs to be highly available in the Windows failover cluster.

STEP ACTION

1. In Failover Cluster Manager, expand HVServerCluster, select Roles, and then click Action >

Configure Role.

The High Availability Wizard starts.





STEP ACTION

3. On the Select Role page, scroll down to the bottom of the list, select Virtual Machine, and then

click Next.

4. On the Select Virtual Machine page, select CentOS6.7_V1 and CentOS6.7_V2, and then click

Next.




STEP ACTION


6. On the Summary page, verify the success of the operation, and then click Finish.

7. A highly available VM can be migrated from one high-availability node to the other

without disruption. For more information about deploying this solution, see the

Microsoft TechNet article “Deploy Hyper-V over SMB.”

https://technet.microsoft.com/en-us/library/jj134187.aspx

END OF EXERCISE


https://technet.microsoft.com/en-us/library/jj134187.aspx

E4-1 Implementing Microsoft Hyper-V on Data ONTAP: Installing SnapManager for Hyper-V


MODULE 4: INSTALLING SNAPMANAGER FOR HYPER-V

EXERCISE 1: INSTALLING SNAPDRIVE FOR WINDOWS

In this exercise, you install a Windows hotfix, check the installed version of the .NET Framework, and install

the NetApp PowerShell Toolkit. You install and configure SnapDrive for Windows.

OBJECTIVES


Check for the Windows hotfixes that are necessary for SnapDrive for Windows and SnapManager for

Hyper-V (SMHV)

Check the .NET Framework version

Install the NetApp PowerShell Toolkit

Install SnapDrive for Windows

Configure SnapDrive for Windows in an SMB 3.0 environment




TASK 1: VERIFY WINDOWS HOTFIX AND .NET FRAMEWORK INSTALLATION

In this task, you use Windows PowerShell and File Explorer to verify the installation of Windows hotfixes

and the .NET Framework.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server and click the Windows

PowerShell icon in the taskbar.

2. In the Windows PowerShell command line, type get-hotfix.

Microsoft hotfix KB2903939 is missing.

3. Close Windows PowerShell.

4. In the CourseFiles\Implementing_Hyper-V folder, double-click the Windows8.1-

KB2903939-x64 file.




STEP ACTION

5. In the next confirmation window, click Yes.

6. When the installation is complete, click the Restart Now button.

7. After the server restarts, return to the Remote Desktop Connection on the HyperV-V1 server.

8. To check the version of .NET Framework, click the File Explorer icon in the taskbar.




STEP ACTION

9. Navigate to the path C:\Windows\Microsoft.NET\Framework.

These folders indicate that Microsoft .NET Framework versions 3.5 and 4.5 are installed.

10. Repeat steps 1 through 9 on the HyperV-V2 server.

11. See your instructor if the version of the .NET Framework that is installed on your

servers is not correct.




TASK 2: INSTALL THE NETAPP POWERSHELL TOOLKIT

In this task, you install the NetApp PowerShell Toolkit on both Hyper-V servers. The NetApp PowerShell

Toolkit contains several cmdlets aimed at storage administration on Windows hosts.

STEP ACTION

1. On the HyperV-V1 desktop, open the CourseFiles folder and the Implementing_Hyper-V folder,

and then double-click the NetApp_PowerShell_Toolkit_4.0.0 file.

2. On the opening setup page, accept the license terms, click the Install button, and click OK in

the WebServices Proxy window.




STEP ACTION

3. When the setup is complete, click Finish.

4. Repeat steps 1 through 3 on the HyperV-V2 server.

5. The NetApp PowerShell Toolkit is a Windows PowerShell extension module that

enables you to control Data ONTAP from a Windows PowerShell environment. It

provides more than 1,000 cmdlets that integrate with Microsoft System Center.

6. On both Hyper-V servers, open a Windows PowerShell window and type $host.version.

Your output should look like this example:

Major Minor Build Revision

----- ----- ----- --------

4 0 -1 -1

PS C:\Users\administrator.LEARN>




TASK 3: EXPLORING THE NETAPP POWERSHELL TOOLKIT

In this task, you load the Data ONTAP module in the NetApp PowerShell Toolkit and explore basic NetApp

PowerShell Toolkit commands to get information about the Data ONTAP cluster and Hyper-V environment.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server and then open a NetApp

PowerShell Toolkit window.

2. To check which modules are currently used in the NetApp PowerShell Toolkit session, type

Get-Module and notice that the Data ONTAP module is not shown.

3. To import the NetApp PowerShell Toolkit module, type these commands:

Import-Module DataONTAP

Get-Module

4. Display cmdlets included in the NetApp PowerShell Toolkit:

Get-NaHelp | more

5. To scroll through the output, press the Spacebar.




STEP ACTION

6. To display the list of categories, use the Get-NaHelp cmdlet with the -CategoryList option:

Get-NaHelp –CategoryList | more

7. To display the HTML Help, use the Show-NaHelp cmdlet:

Show-NaHelp

You can switch between clustered Data ONTAP and 7-Mode documentation.




STEP ACTION

8. To use the Get-Help cmdlet to check options and syntax for a cmdlet, type Get-Help Get-

NaVol and then answer [Y] Yes to the prompt to download the most current Help files.

9. To try another way to get syntax help, type Get-NaAggr -?, and explore the output.

You can simply type the cmdlet name followed by -?.

10. Use Get-NaHelp with a category name:

Get-NaHelp –Category cifs

11. To connect to the NetApp storage virtual machine (SVM), type Connect-NcController

192.168.0.77 –credential vsadmin, enter the vsadmin password in the credentials

window, and then click OK.




STEP ACTION

12. Notice that you are returned to the NetApp PowerShell Toolkit window.

13. To connect to the cluster management logical interface (LIF), type Connect-

NcController 192.168.0.50, enter the user name admin and the password

Netapp123, and then click OK.

14. Notice that you are returned to the NetApp PowerShell Toolkit window.

15. Acquire some information by running the following commands:

Get-NcVolSpace

Get-NcVserver

Get-NcNetSubnet

Get-NcLicense

Get-NcCifsShare

Get-NcNameMappingUnixUser

Get-NcNetDns

Get-VM

Get-VMSwitch




STEP ACTION

16. After using the commands in Step15, answer the following questions:

1) What command do you run to find out the name servers that are configured for the

NetApp SVM?

______________________________

2) What command shows the uptime for a Hyper-V virtual machine (VM)?

______________________________

3) What is the name of the Hyper-V virtual switch? What command did you use to find

this information?

______________________________

4) How many CIFS shares are shown on the HV_STORAGE server?

______________________________

5) Why did the Get-NcNetSubnet command fail?

______________________________

6) What command shows you the amount of Snapshot Reserve space that is taken on the

volume?

______________________________

7) What is the User ID of the “pcuser” user name?

______________________________

TASK 4: INSTALL SNAPDRIVE FOR WINDOWS

In this task, you install and configure SnapDrive for Windows on both Windows Hyper-V servers.

STEP ACTION

1. On the HyperV-V1 server desktop, open the CourseFiles folder, open the Implementing_Hyper-

V folder, and then double-click the SnapDrive7.1.1_x64 file to launch the installation wizard.

2. On the Welcome page, click Next.




STEP ACTION

3. On the SnapDrive License page, select the Per Storage System license type option and click

Next.




STEP ACTION

4. On the Customer Information page, in the Organization field, type NetApp, and then click

Next.

5. On the Destination Folder page, click Next.

6. Without making any changes to the next two pages, which are related to VirtualCenter and

Virtual Storage Console, click Next on each page.




STEP ACTION

7. On the SnapDrive Service Credentials page, click the Add button.

8. On the Select User or Service Account page, type Administrator, and then click the Check

Names button.

9. Verify that the Administrator user name is underlined, and then click OK.




STEP ACTION

10. In the Password fields, enter the administrator password, Netapp123, and then click Next.

11. Without making any changes to the SnapDrive Web Service Configuration page, click Next.




STEP ACTION

12. On the Preferred Storage System IP Address page, select the Enable preferred storage system

IP Address checkbox.

13. In the next two fields, enter the name of the SVM and the IP address of the SVM management

LIF, and then click Next.




STEP ACTION

14. On the Transport Protocol Default Setting page, select the HTTP option, enter the user name

vsadmin and the password Netapp123, then click Next.

15. In Step 14, you are using the vsadmin account for SnapDrive to communicate with

the Data ONTAP cluster.

16. Without making any changes to the Unified Manager Configuration page, click Next.

17. On the next page, click Install.




STEP ACTION

18. When the SnapDrive installation is complete, click Finish.

19. Perform Steps 1 through 18 on the HyperV-V2 server.

20. Stop here and notify the instructor that you are finished with the exercise.

EXERCISE 2: INSTALLING SNAPMANAGER FOR HYPER-V

In this exercise, you install and configure SnapManager for Hyper-V.

OBJECTIVES


Install SMHV

Configure SMHV




TASK 1: INSTALL SNAPMANAGER FOR HYPER-V

In this task, you install SMHV on both Windows Hyper-V servers.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server.

2. On the desktop, open the CourseFiles folder, then open the Implementing_Hyper-V folder, and

double-click the SMHV2.1.1_x64 file to launch the Installation Wizard.


4. On the SnapManager for Hyper-V License page, select the Per Storage System option and click

Next.

5. Without making any changes to the Destination Folder page, click Next.




STEP ACTION

6. On the SnapManager for Hyper-V Web Service Credentials page, click Add, enter the

administrator account credentials, and click Next.

7. Without making any changes to the Web Service Configuration page, click Next.




STEP ACTION

8. To begin the installation, on the next page, click Install.

9. When the InstallShield Wizard Completed page appears, click Finish.

10. Perform Steps 1 through 9 on the HyperV-V2 server, but in Step 2, double-click the

SMHV2.1._x64 file to launch the Installation Wizard.

11. You are installing an older version of SMHV on the HyperV-V2 server. You will

upgrade SMHV on the HyperV-V2 server to version 2.1.1 in a later exercise.




STEP ACTION

12. On both Hyper-V servers, pin the SnapDrive for Windows program to the Windows taskbar for

easy access.

You can find the program at C:\Program Files\NetApp\SnapDrive.




STEP ACTION

13. Repeat Step 12 for SMHV.

You can find the program at C:\Program Files\NetApp\SnapManager for

Hyper-V.

END OF EXERCISE


E5-1 Implementing Microsoft Hyper-V on Data ONTAP: Configuring SnapManager for Hyper-V


MODULE 5: CONFIGURING SNAPMANAGER FOR HYPER-V

EXERCISE 1: CONFIGURING SNAPMANAGER FOR HYPER-V FOR BACKUPS

In this exercise, you add hosts to SnapManager for Hyper-V (SMHV). You perform a Hyper-V export of

virtual machines (VMs) and import the VMs onto NetApp storage.

OBJECTIVES


Add hosts to SMHV

Perform Hyper-V VM export and import

TASK 1: ADDING HOSTS TO SMHV

In this task, you start SMHV on the HyperV-V1 server and add the HyperV-V2 server to the interface.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server, start SMHV, and select

Protection > Add Host.


3. In the Add Host / Enter Host information window, click the Browse button, type the name of the

Windows File Share Cluster in the object name box, and click the Check Names button.

4. Verify that the cluster name is underlined and click OK.

5.

In the Add Host / Enter Host information window, enter the user name

learn\administrator and the password Netapp123, and then click Next.




STEP ACTION

6. On the Verify Installation page, notice that the HyperV-V2 server is marked for SMHV

Upgrade, and then click Next.

7. On the Host Details page, click Next.

8. On the Summary page, click Next.

9. The Add Host Wizard performs an automatic upgrade of SMHV on the HyperV-V2

host.




STEP ACTION

10. On the Status page, notice that the Add Host Wizard performed an automatic upgrade of SMHV

on the HyperV-V2 host, and then click Close.

11. When a window appears, prompting you to run the configuration wizard, click Yes.

12. When the Configuration Wizard starts, on the Welcome page, click Next.

13. Without making any changes on the Report Settings page, click Next.

14. Without making any changes on the Notification Settings page, click Next.




STEP ACTION

15. On the Storage Connection Settings page, click the plus-sign button, enter the following settings,

and then click Next:

Storage: hv_svm (name of the NetApp storage VM)

User: vsadmin

Password: Netapp123

Protocol: HTTP

Port: 80

Selected checkbox: Update all nodes

16. Notice that in Step 15 you are using the vsadmin account for authentication, and the

Update all nodes checkbox is selected.




STEP ACTION

17. On the SnapInfo Settings page, click the NAS button, click the Browse button, and expand the

\\HV_STORAGE server.

18. Select the SMHV_SnapInfo share and click OK.

19. When you are returned to the SnapInfo Settings page, click Next.





STEP ACTION

21. When the Status page indicates that the operation finished successfully, click Close.

22. In the left pane, select Protection.

23. Click the Hosts tab, expand HVServerCluster, and expand Unprotected resources.


24. Close SMHV on the HyperV-V1 server.

TASK 2: VM EXPORT AND IMPORT

In this task, you use Microsoft Hyper-V Manager to export a VM to local storage. You then import the VM

and delete the original VM.

STEP ACTION

1. SMHV does not contain a migration wizard to help you migrate VMs from third-party

storage. You must manually export and import the VM by using Hyper-V Manager.

2. Open a Remote Desktop Connection to the HyperV-V1 server and start the Hyper-V Manager

utility.




STEP ACTION

3. To be sure that both VMs are shut down, select the HyperV-V1 server and, in the Virtual

Machines window, select Shut Down.

4. In the Shut Down Machine window, click Shut Down.

5. In the Actions pane, under CentOS6.7_V1, click Export.




STEP ACTION

6. When the Export Virtual Machine wizard starts, click Browse.

7. Browse to the HyperV1_VMs CIFS share on the NetApp cluster and click the Export button.

8. When the export process begins, notice the Status column.

9. The export process might take several minutes to finish. Inform the instructor that you

are at this step.




STEP ACTION

10. To import the VM, in the Actions pane, select Import Virtual Machine.


12. On the Locate Folder page, type or browse to

\\hv_storage\hyperv1_vms\CentOS6.7_V1, and then click Next.

13. On the Select Virtual Machine page, click Next.




STEP ACTION

14. On the Choose Import Type page, select Copy the virtual machine and click Next.

15. Select the Store the virtual machine in a different location checkbox, adjust the paths as

shown, and click Next.




STEP ACTION

16. On the Choose Folders to Store Virtual Hard Disks page, enter the same path and click Next.

17. On the Completing Import Wizard page, click the Finish button.




STEP ACTION

18. Next, you will delete the original VM. You must be very careful to delete the correct

VM because you will see two VMs with identical names. Check the VM settings to

verify the path where the VM is being stored.

This example shows the CentOS6.7_V2 VM using local storage.

19. Right-click the VM and select Delete.

20. In the confirmation window, click the Delete button.




STEP ACTION

21. To start the VM in its new location, right-click the VM and select Start.

22. Verify that the VM starts correctly.

23. Optional: Connect to the VM and verify that you see a localhost login prompt.

24. Open a Remote Desktop Connection to the HyperV-V2 server and repeat Steps 1 through 22 to

export and import the CentOS6.7_V2 VM. These steps must be performed from the HyperV-V2

server.




TASK 3: UPDATING FAILOVER CLUSTER MANAGER

In this task, you update the Windows Failover Cluster Manager with the information that the VMs have

moved to new storage.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server, start Server Manager, and click

Tools > Failover Cluster Manager.

2. Expand HVServerCluster.learn.netapp.local, click Roles and, in the Roles pane, select the

CentOS6.7_V1 VM.

3. In the Actions pane, click Remove.

4. In the confirmation window, click Yes.

5. Repeat Steps 3 and 4 to remove the CentOS6.7_V2 VM from the Roles pane.

6. Right-click Roles and select Configure Role.





STEP ACTION

8. On the Select Role page, select Virtual Machine and click Next.

9. On the Select Virtual Machine page, select both VMs and click Next.

10. On the Confirmation Page, click Next.




STEP ACTION

11. When the Summary page indicates a successful result, click Finish.





EXERCISE 2: CONFIGURING SNAPMANAGER FOR HYPER-V FOR BACKUPS

In this exercise, you use SMHV to create datasets to protect the VMs. You add policies to the datasets to

create manual and scheduled backup jobs, and you perform manual VM backup jobs.

OBJECTIVES


Use SMHV to create datasets

Use SMHV to apply policies to datasets

Use SMHV to perform VM backup jobs manually

Use SMHV to schedule automatic backup jobs

TASK 1: CREATING DATASETS

In this task, you use SMHV to create a dataset to protect one of the VMs running on the Hyper-V servers.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server and start SMHV.

2. In the left pane, select Protection.

3. In the Dataset Management window, click the Datasets tab and expand Unprotected resources.


4. In the Actions pane, click Create Dataset.

The Create Dataset Wizard starts.





STEP ACTION

6. On the Basic Details page, enter the dataset name CentOS_V1 and the description Backup of

CentOS6.7_V1 Virtual Machine, and then click Next.

7. On the Resources page, expand Hosts and HVServerCluster, select the CentOS6.7_V1 VM,

and click Next.




STEP ACTION

8. On the validation page, make sure that the remarks indicate that the VMs in the dataset are valid,

and then click Next.


10. Verify that the Status page indicates a successful operation, and then click Close.




STEP ACTION

11. On the Datasets tab, expand CentOS_V1 and Unprotected resources and verify that your

window looks similar to this example:

12. A dataset without a policy cannot be used in a backup job. You add a policy to the

dataset in the next steps.

13. Select the CentOS_V1 dataset and then, in the Action pane, click Add Policy.

The Add Policy Wizard starts.


15. On the Basic Details page, enter the following configuration settings, and then click Next.

Policy name: CentOS_V1_Daily

Description: Daily backup of the CentOS6.7_V1 VM

Backup type: Crash consistent




STEP ACTION

16. On the Retention page, enter the following configuration settings, and then click Next.

Retention type: Daily

Delete backup older than 7 days

17. The number of backup jobs retained correlates directly with the number of Snapshot

copies on the Data ONTAP volume. Sizing the storage for capacity is an important

consideration.

18. Without making any changes on the Scheduling page, click Next.

19. Without making any changes in the Backup Options page, click Next.





STEP ACTION


TASK 2: PEFORM A MANUAL VM BACKUP

In this task, you manually back up a VM, using the dataset created in Task 1.

STEP ACTION

1. Open SMHV.

2. On the Datasets tab, click the CentOS_V1 dataset and then, in the Actions pane, click Backup.

The Backup Dataset Wizard starts.


4. Without making any changes, click Next on the Backup Name, Retention Policy, and Backup

Options pages.




STEP ACTION


6. After the backup is complete, verify that the Status page indicates a successful backup task, and

then click Close Wizard.




TASK 3: CREATE A SCHEDULED VM BACKUP JOB

In this task, you create a dataset, apply a policy, and schedule the backup job to run automatically.

STEP ACTION

1. On the HyperV-V1 server, open SMHV.

2. On the Datasets tab, expand the CentOS_V1 dataset and expand Unprotected resources.

The CentOS6.7_V2 VM remains unprotected.

3. Select the CentOS6.7_V2 VM.

4. In the Actions pane, click Create Dataset.

The Create Dataset Wizard starts.


6. On the Basic Details page, enter the following configuration settings, and then click Next:

Dataset name: CentOS_V2

Description: Daily backup of the CentOS6.7_V2 VM

Selected checkbox: Validate Dataset

7. On the Resources page, select the CentOS6.7_V2 VM and click Next.




STEP ACTION

8. On the Validation page, verify that all VMs in the dataset are valid, and then click Next.


10. Verify that the Status page indicates a successful operation and click Close.

11. On the Datasets tab, select the newly created dataset and, in the Actions pane, click Add Policy.

The Add Policy Wizard starts.


13. On the Basic Details page, enter the following configuration settings, and then click Next.

Policy name: CentOS_V2_Daily_Scheduled

Description: Daily scheduled backup of the CentOS6.7_V2 VM

Backup type: Crash consistent




STEP ACTION

14. On the Retention page, enter the following configuration settings, and then click Next.

Retention type: Daily

Delete backup older than 7 days

15. On the Scheduling page, select the Enable Scheduler checkbox and click the Schedule button.




STEP ACTION

16. In the Schedule Job window, enter these settings, and then click OK:

Scheduler Job Name: CentOS_V2

Run As: Administrator

Password: Netapp123

Confirm password: Netapp123




STEP ACTION

17. In the Job Schedule configuration window, click the Schedule tab, schedule the task to run at

9:00 PM daily, every day, and click OK.

18. In the Set Account Information window, enter the Administrator password twice and click OK.




STEP ACTION

19. On the Scheduling summary page, click Next.

20. Without making any changes on the Backup Options page, click Next.



23. Open SMHV.




STEP ACTION

24. On the Datasets tab click the CentOS_V1 dataset and then, in the Actions pane, click Backup.

The Backup Dataset Wizard starts.


26. Without making any changes, on the Backup Name, Retention Policy, and Backup Options

pages, click Next.


28. After the backup is complete, verify that the Status page indicates a successful backup task, and

then click Close Wizard.

END OF EXERCISE


E6-1 Implementing Hyper-V on Data ONTAP: Restoring Virtual Machines with SnapManager for Hyper-V


MODULE 6: RESTORING VIRTUAL MACHINES WITH SNAPMANAGER FOR HYPER-V

EXERCISE 1: RESTORING VIRTUAL MACHINES WITH SMHV

In this exercise, you use SnapManager for Hyper-V (SMHV) to restore a virtual machine (VM). You verify

the success of the restore process and review SMHV recovery reports.

OBJECTIVES


Use SMHV to restore a VM

Verify the success of the VM restore process

Review SMHV recovery reports

TASK 1: PERFORMING A VM RESTORE

In this task, you create some data in a guest VM and use SMHV to perform a series of backup jobs. You

restore the VM from a backup and verify the success of the restore process. You then review SMHV recovery

reports.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server, start Hyper-V Manager, and

select the Hyperv-V1 server.

2. Go to Step 3 if the VM is already running.

To start the VM, in the Virtual Machines pane, right-click CentOS6.7_V1 and select Start.

3. When the guest operating system starts, in the Actions pane, connect to the VM by clicking

Connect.

4. Log in to the guest operating system.

User name: root

Password: Netapp123




STEP ACTION

5. On the command line type:

Cd /

pwd

6. On the command line, type:

touch FileOne

ls FileOne

7. Minimize the CentOS6.7_V1 connect window and create another on-demand backup of the VM.

Refer to the exercise in Module 5 if necessary.

8. When the backup is complete, repeat Step 6 and create a file named FileTwo.

9. Repeat Step 7 and create another backup of the CentOS_V1 dataset.

10. In the CentOS_V1 connection window, delete File Two:

a. On the command line, type rm FileTwo.

b. At the confirmation prompt, type y.

c. Type ls File*.

11. Minimize the CentOS6.7_V1 window again and, in SMHV, select Recovery.

12. Expand Protected Resources and select the CentOS6.7_V1 resource.




STEP ACTION

13. In the Backups pane, select the most recent backup and then, in the Actions pane, click Restore.

14. When the Restore Wizard starts, on the Restore Options page, notice that the Restart Virtual

Machine option is selected.

15. Without making any changes, on the Restore Options page, click Next.




STEP ACTION


17. If a Virtual Machine Connection window opens, click Exit.




STEP ACTION

18. When the restore operation is successfully finished, notice that the VM was taken offline during

the restore process, causing the disconnect message in Step 17.

19. Click Close Wizard.

20. In Hyper-V Manager, reconnect to the VM and log in.

21. On the command line type:

cd /

pwd

ls File*

22. Notice that FileTwo has been restored.




EXERCISE 2: WINDOWS LIVE MIGRATION

In this exercise, you use the Windows Failover Cluster Manager to perform a live migration between two

Hyper-V servers.

OBJECTIVES

This exercise focuses on enabling you to do the following use Windows Failover Cluster to perform a live

migration between Hyper-V Servers.

TASK 1: TESTING WINDOWS CLUSTER FAILOVER

In this task, you configure the Ethernet IP addresses for the guest VMs. Then you use Windows Failover

Cluster Manager to perform a live migration between Hyper-V servers. You observe the behavior of the live

migration while it is being performed.

STEP ACTION

1. Open a Remote Desktop Connection to the HyperV-V1 server and open Windows Hyper-V

Manager.

2. To connect to the CentOS6.7_V1 VM, click the HyperV-V1 server, right-click the VM, and

select Connect.

3. Log in to the CentOS 6.7 VM and configure the Ethernet interface with an IP address:

Login: root

Password: Netapp123

Type: ip addr add 192.168.0.110/24 dev eth0

Type: ip addr show

4. Check the output for the correct configuration.

5. Close the connection to CentOS6.7_V1 and keep the VM running.




STEP ACTION

6. Connect to the CentOS6.7_V2 VM, configure the IP address 192.168.0.111/24, and check your

configuration.

See Steps 2 and 3 for details, as needed.

7. Close the connection to CentOS6.7_V1 and keep the VM running.

8. Open a Windows PowerShell window and start a continuous ping to the CentOS6.7_V1 VM by

typing ping –t 192.168.0.110.

9. While the ping command is running, resize your Windows PowerShell window and place it in

the lower-left corner of your desktop.




STEP ACTION

10. Open Windows Failover Cluster Manager and resize the window so that you can see the ping

running in the Windows PowerShell window.

Your desktop should look similar to this example:




STEP ACTION

11. Right-click the CentOS6.7_V1 VM and select Move > Live Migration > Select Node.

12. Select the HyperV-V2 node and click OK.




STEP ACTION

13. When the migration begins, resize your Failover Cluster Manager window so that you can see

the Information column that shows the live migration.

14. As the migration is running, watch the continuous ping running in the Windows PowerShell

window.

You might notice that one or two of the ping replies drop.

15. When the migration is complete, notice that the ping is still running, and also notice that the VM

is now running on the HyperV-V2 server owner node.

16. Migrate the CentOS6.7_V1 VM back to the HyperV-V1 server.

See Steps 11 and 12, as needed.

END OF EXERCISE


E7-1 Implementing Microsoft Hyper-V on Data ONTAP: Managing the Integrated Virtualized Data Center


MODULE 7: MANAGING THE INTEGRATED VIRTUALIZED DATA CENTER

EXERCISE 1: MIGRATING VIRTUAL MACHINES WITH ONCOMMAND SHIFT

In this exercise, you watch two videos. The first video demonstrates using OnCommand Shift to migrate a

virtual machine (VM) from VMware ESX to Hyper-V. The second video demonstrates using OnCommand

Shift to migrate a VM from Hyper-V to VMware ESX.

OBJECTIVES


Explain the VM migration process using OnCommand Shift

Describe the VM migration process from VMware ESX to Hyper-V

Describe the VM migration process from Hyper-V to VMware ESX

TASK 1: VM MIGRATION FROM VMWARE ESX TO HYPER-V

In this task, you watch a video that demonstrates the VM migration process using OnCommand Shift. The

process involves converting the VM format from VMware ESX to Hyper-V.

STEP ACTION

1. Your course files include nine video files in MP4 format.

Open the file named 8_ESX_To_HyperV.

2. View the video

TASK 2: VM MIGRATION FROM HYPER-V TO VMWARE ESX

In this task, you watch a video that demonstrates the VM migration process using OnCommand Shift. The

process involves converting the VM format from Hyper-V to VMware ESX.

STEP ACTION

1. Open the file named 9_HyperV_To_ESX.

2. View the video.

OPTIONAL TASK 3: INSTALLING AND CONFIGURING ONCOMMAND SHIFT

In this task, you watch a series of videos that illustrate the installation and configuration of OnCommand

Shift.

STEP ACTION

1. View the video files in the order.

They are numbered 1 through 7.

END OF EXERCISE


Documents

Implementing Microsoft Hyper-V on Data ONTAP · PDF fileMODULE 7: MANAGING THE ... – One Active Directory Domain Controller with DNS Server ... E-7 Implementing Microsoft Hyper-V