IBM VSS Hardware Provider 4.2.1 Support for Hyper-V ...

[Pages:11]IBM VSS Hardware Provider 4.2.1 Support for Hyper-V Configuration Guide

1 Overview.................................................................................................................2 2 Primary Configuration ............................................................................................2

2.1 Requirements ................................................................................................ 2 2.2 Configure the Host (Hyper-V) Server ..........................................................2 2.3 Configure IBM VSS Hardware Provider .....................................................3 2.4 Configuring Source Volumes .......................................................................4 2.5 Taking snapshots ..........................................................................................5 3 Advanced Configuration.........................................................................................5 3.1 Configuring NPIV ........................................................................................5

3.1.1 Requirements ........................................................................................ 6 3.1.2 Create virtual Port .................................................................................6 3.1.3 Create Zoning........................................................................................6 3.1.4 Configuring Storage..............................................................................6 3.1.5 Configuring the Host Disk ....................................................................6 3.1.6 Deploying Guests..................................................................................7 3.1.7 Configuring Source Volume..................................................................7 3.1.8 Verifying NPIV Configuration..............................................................8 3.1.9 Taking snapshot.....................................................................................8 3.2 Storage Protocol Setting...............................................................................8 4 Limitation..............................................................................................................10 5 Troubleshooting ....................................................................................................10

IBMVSS Hardware Provider 4.2.1 | Overview 1

1 Overview

This guide describes the steps to take shadow copies in Hyper-V guest OS with IBM VSS Hardware Provider for DS8000 and SVC. If you have installed software ISCSI initiator in guest OS and do not plan to use FC protocol or ISCSI protocol on host, the configuration is the same as physical host. This guide will not cover this part of configuration. Because there's no FC HBA on guest OS, IBM VSS Hardware Provider will serve as a bridge to associate the FC HBA on host to the guest OS during creating and deleting shadow copy. Provider supports host ISCSI as well depending on host and provider's settings. Privileges to access host WMI are required to support this feature. Provider supports shadow copy on pass-through disks in the guest OS only, since it can't support the hardware information of virtual hard disk. The volume shadow copy's target LUN is attached to guest OS as pass-through disk by provider automatically.

2 Primary Configuration

Follow configurations in this section, you'll be able to create shadow copies in Hyper-V guest OS.

2.1 Requirements

IBM VSS Hardware Provider 4.2.1 Server Hardware. Microsoft recommended server configuration for Microsoft

Windows Server 2008 Hyper-V Microsoft Windows Server 2008 Hyper-V Multipathing I/O (MPIO) software. Available from your storage array vendor

2.2 Configure the Host (Hyper-V) Server

i. Install Microsoft Windows Server 2008 x64. Or Windows Server 2008 R2 ii. Install Hyper-V role on the Windows Server via Server Manager (Reboot

IBMVSS Hardware Provider 4.2.1 | Overview 2

needed). iii. Disable automount: turn off automount for the disks on host.

C:\>diskpart

C:\>automount disable

iv. Allow for remote administration on physical host, you can use following command to enable the Windows Firewall:

netsh firewall set service RemoteAdmin enable

v. Install the MPIO driver that ships with Windows 2008. vi. Install the MPIO driver that is supplied by your storage vendor. vii. Install and configure Hyper-V guest OS via Hyper-V Manager. The guest OS

should be windows 2003 R2 or above. viii. Download and install "Microsoft Visual C++ 2008 SP1 Redistributable

Package" on physical host. The package can be download from Microsoft website, the x64 version can be downloaded with link , the x86 version can be downloaded with link 7-4ab7-a40d-3802b2af5fc2&displaylang=en . Both x86 and x64 version should be installed.

2.3 Configure IBM VSS Hardware Provider

i. Logon the Hyper-V guest OS, install IBM VSS Hardware Provider. ii. Copy the file "ibmrescan.exe" from installation directory to physical host. iii. Set parameters to access Host Server. Host Server IP address, domain, user

name and password are needed. A. The user should have following privileges:

Access WMI on host Server, Query WMI objects in following name spaces: root/cimv2, root/wmi,

root/default and root/virtualization. Create process with class Win32_Process in root/cimv2 Manage resources in name space root/virtualization B. Domain should be set as host name if the user does not belong to a Windows domain.

IBMVSS Hardware Provider 4.2.1 | Primary Configuration 3

C. Commands to set the parameters: Set IP address of the Host Server

ibmvcfg set vmhost

Set user name

ibmvcfg set vmusername

Set password

ibmvcfg set vmpassword

set domain

ibmvcfg set vmdomain

set command to rescan devices on physical host.

set rescandevicecmd eg: set rescandevicecmd "C:\ibmrescan.exe"

D. A typical setting showed with command "ibmvcfg showcfg"

2.4 Configuring Source Volumes

Since provider can only support taking shadow copies for volumes that based on disks from SVC or DS8000, the disks need to be assgined to guest OS by pass-through mode.

IBMVSS Hardware Provider 4.2.1 | Primary Configuration 4

i. Add SCSI Controller to guest OS ( need to shutdown guest OS first) ii. Add pass through disk drive to guest OS (Guest OS can be running state), the

disks should be offline state on host, otherwise they cannot appear in the physical hard disk combo box. iii. Logon guest OS, create volume on the newly added hard disk, and assign drive letter or mount point to the volume.

2.5 Taking snapshots

You need to configure LUNs with the same size as source LUNs as snapshot target in the free pool on storage. Before taking snapshot for the volume on the guest OS, you can run following command to check whether the configuration is correct(X: is the driver letter or mount point to take snapshot, one or more drive letter or mount point supported by this command):

ibmvcfg testsnapshot X:

The procedures of taking, deleting, masking, resynchronizing and importing snapshots are the same as physical host. Provider attaches the target LUNs to physical host, then assign it to guest OS as pass-through disk when taking or importing snapshot. Provider removes target LUN from guest OS before detaching it from physical host when deleting or masking snapshot.

3 Advanced Configuration

This section describes NPIV(N_Port Virtualization) and storage protocol priority supports in provider.

3.1 Configuring NPIV

NPIV stands for N_Port ID Virtualization. It provides a simple, high-availability capability. NPIV uses Host Bus Adapter (HBA) technology, which creates virtual HBA ports on hosts by abstracting the underlying physical port. This support enables a single physical Fiber Channel HBA port to function as multiple logical ports, each with its own identity. Each virtual machine can then attach to its own virtual HBA port and be independently zoned to a distinct and dedicated World Wide Port Name (WWPN). ()

IBMVSS Hardware Provider 4.2.1 | Advanced Configuration 5

For more information about NPIV and HBA technology, refer to your HBA vendor documentation. If you plan to use ISCSI protocol please ignore following subsections.

3.1.1 Requirements

NPIV Enabled FC Adapter. NPIV Enabled FC Switch. FC HBA Manager and Agent with V-Port creation feature. NPIV WMI provider installed on host. (Most of the FC drivers implement it.)

3.1.2 Create virtual Port

Open FC HBA Manager GUI, select a physical port and create a virtual port on it.

3.1.3 Create Zoning

Create an alias and zone with that virtual port and storage, but do not to add the host WWN to the zone. The only two things in that zone will be the new NPIV port and the storage. You do not need to reboot the host to make the NPIV port available.

3.1.4 Configuring Storage

Add the virtual port to the LUN that will contain the guest. You do not need to add the physical port to the LUN.

3.1.5 Configuring the Host Disk

For virtual disks, bring the new LUN online and initialize it . Assign drive letters to the volume to contain guest OS configuration files and VHDs. Volume with mount point is not supported by provider to support NPIV.

For pass through disks, you need two LUNs per guest: one for the configuration files and the other to actually install the OS. The volume containing configuration files needs to be assigned a drive letter. Make sure that the disk to be offline to install OS.

IBMVSS Hardware Provider 4.2.1 | Advanced Configuration 6

3.1.6 Deploying Guests

Deploying with Hyper-V Manager Open Hyper-V Manager; click "New->Virtual Machine ..." menu item in "Actions" panel. When you are prompted for a location for the virtual machine, choose the volume that is on the LUN created earlier.

After Memory and Networking configurations, you need to specify hard disk to install guest OS. If it's a virtual hard disk, you should locate it on a volume that is on the LUN through the virtual port. If it's a pass-through disk, it should be from the virtual port, be marked offline and be configured as MBR disk type. GPT and dynamic will not work with a pass-through disk. If the disk is previously configured as GPT or dynamic, you must bring the disk online and convert it, which means that you need to shut down the guest.

Deploying with SVCMM If the host is managed by Microsoft System Center Virtual Machine Manager (SCVMM), you can create virtual machine through it. When you get to the screen prompting for the host on which to place the guest, make sure you pick the one that has the virtual port active. When you are prompted for a location for the files, click Browse and select the LUN created earlier. If you do not see it, you may need to refresh the disks or check the host to make sure the disk is online, and formatted.

The configuration of the disk to install guest OS is the same as Hyper-V Manager.

3.1.7 Configuring Source Volume

The steps are the same as primary configuration, except the LUN is through virtual port.

IBMVSS Hardware Provider 4.2.1 | Advanced Configuration 7

3.1.8 Verifying NPIV Configuration

To make sure that a LUN is from virtual port, you can open FC HBA Manager and see whether the LUN is under the virtual port(some of the FC HBA Manager do not support this feature).

3.1.9 Taking snapshot

The procedure of taking snapshot is the same as primary configurations, except provider attaches the LUN to host through virtual port automatically.

3.2 Storage Protocol Setting

Since provider supports ISCSI feature for SVC 5.1 or higher, storage protocol setting is to set by which protocol the target LUNs are attached to host. There are three options to choose for this setting, auto, FC and ISCSI.

Auto Provider will choose appropriate protocol automatically, if there's no available protocol on host snapshot will fail.

FC Provider will choose Fiber Channel protocol, if there's no FC protocol, snapshot will fail.

ISCSI Provider will choose SCSI protocol, if there's no ISCSI protocol, snapshot will fail.

The command to set storage protocol is:

ibmvcfg set storageprotocol

If there are more than one storage protocols installed on host and guest OS, provider will choose right protocol by following algorithm:

1. Protocol setting is auto If FC and ISCSI coexist, FC prior to ISCSI. If ISCSI installed on both guest and host, ISCSI on guest prior to on host.

2. Protocol setting is FC IBMVSS Hardware Provider 4.2.1 | Advanced Configuration 8

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download