EMC Virtual Storage Integrator for Hyper-V Version 1.0 ... · EMC Corporation Corporate...

EMC Virtual Storage Integrator for Hyper-VVersion 1.0

Product GuideP/N 300-011-016

REV A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

Published August, 2010

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Document/Whitepaper Library on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC Virtual Storage Integrator for Hyper-V Version 1.0 Product Guide

Contents

Chapter 1 About EMC Virtual Storage Integrator for Hyper-VVirtual Storage Integrator for Hyper-V overview........................ 14

Microsoft System Center Virtual Machine Manager overview.......................................................................................16SRDF/Cluster Enabler overview .............................................17

Software requirements ..................................................................... 19Microsoft Windows Server Hyper-V.......................................19EMC Solutions Enabler ..............................................................19VSI Server ....................................................................................19VSI Client .....................................................................................20Symmetrix storage arrays..........................................................20CLARiiON storage arrays .........................................................21

VSI for Hyper-V logging.................................................................. 22Disk space requirements............................................................23Extracting logs.............................................................................23Changing the logging level .......................................................24Changing the logging directory ...............................................24Changing logging retention period .........................................25Changing the maximum log file size .......................................25

Chapter 2 VSI for Hyper-V InstallationInstallation overview........................................................................ 28

Before you begin .........................................................................28Installing Virtual Storage Integrator .............................................. 32

Installing the VSI Server/Client components ........................32Installing the VSI Client.............................................................33

Uninstalling Virtual Storage Integrator ......................................... 34Uninstalling EMC Solutions Enabler .......................................35

EMC Virtual Storage Integrator for Hyper-V Version 1.0 Product Guide 3

Contents

Chapter 3 VSI ConfigurationConfiguring Solutions Enabler ....................................................... 38

Licensing...................................................................................... 38Local mode .................................................................................. 39Remote mode or client/server mode ...................................... 40Configuring a Symmetrix array ............................................... 41Configuring a CLARiiON array............................................... 42Configuring the Solutions Enabler Server .............................. 42

Discovering storage arrays.............................................................. 46

Chapter 4 Using the VSI for Hyper-V Client GUIGetting started with VSI .................................................................. 50

Connecting to an SCVMM Server ............................................ 50VSI navigation tree ..................................................................... 51

Viewing EMC storage ...................................................................... 54Viewing volumes........................................................................ 54Viewing LUNs ............................................................................ 56Viewing targets ........................................................................... 58Viewing virtual machines ......................................................... 61Viewing EMC storage ................................................................ 63Viewing library servers ............................................................. 65Refreshing information.............................................................. 67

Disaster Restart ................................................................................. 68Integrating VSI with Cluster Enabler ...................................... 69Renaming sites ............................................................................ 70Cluster configurations ............................................................... 71Viewing Disaster Restart sites .................................................. 72Refreshing DR information ....................................................... 76

Appendix A VSI Powershell CommandsSupported VSI Powershell commands.......................................... 78

EMC Virtual Storage Integrator for Hyper-V Version 1.0 Product Guide4

Title Page

Figures

1 VSI for Hyper-V configuration..................................................................... 152 VSI installation diagram................................................................................ 313 Enter a SCVMM Server to Connect ............................................................. 424 EMC Virtual Storage Integrator for Hyper-V main page......................... 435 Storage Configuration Solutions Enabler Server tab ................................ 446 Storage Configuration CLARiiON Assisted Discovery tab ..................... 477 CLARiiON Assisted Discovery tab remove array..................................... 478 Connecting to a SCVMM Server .................................................................. 509 VSI for Hyper-V main page .......................................................................... 5110 VSI Hyper-V Hosts navigation pane ........................................................... 5211 Expanded VSI navigation tree...................................................................... 5312 Viewing volumes on a host........................................................................... 5513 Example of a four volume cluster ................................................................ 5614 Viewing LUNs on a host ............................................................................... 5715 Viewing Targets on a host............................................................................. 5916 Viewing Target information ......................................................................... 6017 Viewing Virtual Machine information........................................................ 6218 Viewing EMC storage.................................................................................... 6419 Viewing library servers ................................................................................. 6620 Viewing DR site information - Virtual Machine tab ................................. 7321 Viewing sites - right-click menu options .................................................... 7522 Viewing DR Site information - Storage tab ................................................ 76

Figures

Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the EMC product line, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all revisions of the software and hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a Virtual Storage Integrator feature does not function properly or does not function as described in this guide, please contact the EMC Customer Support Center for assistance.

Audience This guide is part of the EMC Virtual Storage Integrator for Hyper-V documentation set and is intended for use by Microsoft System Center administrators and storage administrators during installation, system setup, and routine operations.

Storage administrators working with Virtual Storage Integrator for Hyper-V must be proficient in the use of the following products:

◆ EMC Symmetrix or CLARiiON storage arrays, as per your Virtual Storage Integrator supported product version and the following applicable software:

• Solutions Enabler (SYMCLI/SYMAPI)

• SRDF/Cluster Enabler

• EMC PowerPath/VE, if installed

◆ Microsoft products:

• Microsoft System Center Virtual Machine Manager (SCVMM) Administrator Console including the Windows PowerShell commands

Preface

• Windows Server 2008 and Windows Server 2008 R2

Requireddocumentation

The following documentation is part of the EMC Virtual Storage Integrator for Hyper-V documentation set, and is required for Virtual Storage Integrator:

◆ EMC Virtual Storage Integrator for Hyper-V version 1.0 Release Notes

Relateddocumentation

The following EMC documentation contains information that may be helpful in a Virtual Storage Integrator environment and are available on the EMC Powerlink website:

EMC Solutions Enabler:

◆ EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide

◆ EMC Solutions Enabler Symmetrix Array Management CLI Product Guide

◆ EMC Solutions Enabler Installation Guide

EMC Symmetrix array:

◆ EMC Symmetrix with Microsoft Hyper-V Virtualization White Paper

EMC ControlCenter:

◆ EMC ControlCenter Planning and Installation Guide

EMC PowerPath:

◆ EMC PowerPath Product Guide

Fibre Channel:

◆ Symmetrix Fibre Channel Product Guide

Preface

Conventions used inthis document

EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

IMPORTANT!An important notice contains information essential to operation of the software. The important notice applies only to software.

Preface

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic: Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier: Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and command

syntax.

Courier bold: Used for:• Specific user input (such as commands)

Courier italic: Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example

Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

techpub_comments@EMC.com

Preface

1Invisible Body Tag

This chapter provides a high-level overview of EMC Virtual Storage Integrator for Hyper-V.

Important: EMC recommends reading this chapter in its entirety before installing and configuring Virtual Storage Integrator for Hyper-V.

◆ Virtual Storage Integrator for Hyper-V overview......................... 14◆ Software requirements ...................................................................... 19◆ VSI for Hyper-V logging ................................................................... 22

About EMC VirtualStorage Integrator for

Hyper-V

About EMC Virtual Storage Integrator for Hyper-V 13

About EMC Virtual Storage Integrator for Hyper-V

Virtual Storage Integrator for Hyper-V overviewEMC Virtual Storage Integrator (VSI) for Hyper-V version 1.0 provides storage details for Hyper-V hosts and virtual machines that are managed by the Microsoft System Center Virtual Machine Manager (SCVMM). Installed as a separate graphical user interface (GUI), VSI for Hyper-V provides storage viewing functionality to facilitate the discovery and identification of the underlying EMC Symmetrix® and CLARiiON® storage devices that are allocated to Hyper-V hosts and virtual machines (VMs). For an overview of SCVMM functionality, see “Microsoft System Center Virtual Machine Manager overview” on page 16.

VSI for Hyper-V presents the EMC storage details to the virtual datacenter administrator, merging the data of several different storage mapping tools into a few seamless views. VSI enables you to resolve the underlying storage of Windows NT File System (NTFS) virtual disks. You are also presented with lists of storage arrays and devices that are accessible to the Hyper-V hosts in the virtual datacenter.

In addition to providing storage viewing functionality, VSI can be integrated with EMC SRDF®/Cluster Enabler (SRDF/CE) software (version 4.0 and higher) to support disaster restart of failover clusters, thus extending disaster restart to support Hyper-V child virtual machines. SRDF/CE extends cluster storage and management capabilities to provide disaster recovery and business continuance protection for Symmetrix storage arrays. For an overview of SRDF/CE functionality, see “SRDF/Cluster Enabler overview” on page 17.

VSI for Hyper-V follows a client/server architecture model. The software is installed as two separate VSI components, one for the client, and one for the server. Once the software has been installed and configured, the VSI GUI displays a navigation tree hierarchy similar to that presented in the VMM Administrator Console. From the VSI navigation tree, you can view storage information for standalone hosts and clusters. If custom host groups are created in the VMM Administrator Console, you can view the same host group hierarchy in the VSI GUI. Host groups are represented in the navigation tree under the SCVMM server name. For standalone hosts, you can view volumes, LUNs, targets, and VMs. For clusters, you can view volumes, VMs, and cluster nodes. For each cluster member node, you can view volumes, LUNs, targets, and VMs.

Figure 1 provides an example of a VSI for Hyper-V client/server configuration.

Figure 1 VSI for Hyper-V configuration

Virtual Storage Integrator for Hyper-V overview 15

Microsoft System Center Virtual Machine Manager overviewVirtualization technology creates an abstraction layer between the physical hardware and software, so that IT administrators can run multiple VMs on a single physical server. This approach helps businesses increase asset utilization, lower operation costs, and quickly respond to the rapidly changing business needs. SCVMM is a virtualization management product from Microsoft System Center, which is Microsoft's family of system management products. It provides support for consolidating multiple physical servers within a virtual infrastructure, thereby helping to increase the overall utilization of physical servers.

SCVMM has several components, including the Virtual Machine Manager (VMM) Server, the VMM Administrator Console, and the Windows PowerShell command line interface. The VMM Server is the core process that communicates with the virtual machine hosts and maintains the system information in a Microsoft SQL Server database.

The VMM Administrator Console is a GUI that allows administrators to effectively manage an environment of hundreds of VMs. The Administrator Console executes Windows PowerShell commands. The VMM Server services can be accessed through the VMM Administrator Console or by using the Windows PowerShell commands.

SCVMM manages virtual machine hosts, which are physical servers running the following virtualization software:

◆ Microsoft Virtual Server 2005 R2 — Virtual Server 2005 R2 is a hosted server virtualization technology engineered for the Windows Server 2003 platform.

◆ Microsoft Windows Server Hyper-V — Hyper-V is a hypervisor- based virtualization platform that Microsoft includes with Windows Server 2008 and R2.

◆ VMware ESX Server — SCVMM is also able to interact with VMware's Virtual Infrastructure, enabling the management of VMware VMs running on ESX Servers.

Note: VSI for Hyper-V is designed only for the viewing of the Hyper-V hosts. Virtual Server 2005 R2 and VMware ESX are not supported by VSI for Hyper-V. An additional software product, named Virtual Storage Integrator for vSphere Client is designed for VMware ESX.

SRDF/Cluster Enabler overviewSRDF/CE version 4.0 and higher is a software plug-in module to EMC Cluster Enabler for Microsoft Failover Clusters software. Cluster Enabler (CE) version 4.0 plug-in architecture consists of a CE base module component and separately available plug-in modules, which support various storage replication technologies.

The SRDF/CE plug-in module provides a software extension of failover clusters functionality that allows Windows Server 2003 and 2008 (including R2) Enterprise and Datacenter editions running Microsoft Failover Clusters to operate across multiple connected Symmetrix arrays in geographically distributed clusters. In Windows Server 2003, the failover clusters are called server clusters and use Microsoft Cluster Server (MSCS).

Note: VSI for Hyper-V does not support CE clusters with Windows Server 2003 hosts, as Hyper-V is a Windows Server 2008 product

Each cluster node is connected through a storage network to the supported Symmetrix array. Once configured using the EMC Cluster Enabler Manager GUI, Microsoft Failover Clusters are referred to as CE clusters. SRDF/CE software can support up to 64 shared quorum disk clusters per Symmetrix pair. There is no limit on the number of Majority Node Set (MNS) clusters per Symmetrix pair.

Note: VSI for Hyper-V currently supports Node and File Share Majority cluster models.

Using an SRDF1 link, SRDF/CE expands the range of cluster storage and management capabilities while ensuring full business continuance protection. A Fibre Channel connection from each cluster node is made to it’s own Symmetrix array. Two Symmetrix arrays are connected via SRDF to provide automatic failover of SRDF-mirrored volumes during a Microsoft cluster node failover. This connection effectively extends the distance between cluster nodes to form a geographically distributed cluster with disaster-tolerant capabilities.

1. The EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide provides information about how SRDF operations work.

Virtual Storage Integrator for Hyper-V overview 17

The EMC SRDF/Cluster Enabler Plug-in Product Guide provides detailed information about Cluster Enabler functionality, component installation, and usage.

Note: MirrorView/Cluster Enabler for Microsoft Failover Clusters (for CLARiiON storage arrays) and RecoverPoint/Cluster Enabler for Microsoft Failover Clusters (for multiple RecoverPoint-supported storage arrays) are not currently supported with VSI for Hyper-V.

Integration with VSI forHyper-V

When using the SRDF/CE GUI, you can only view the VMs in one cluster at a time. The VSI for Hyper-V disaster restart feature provides a consolidated view, where you can view all of the disaster restart sites in all clusters. You must still use the SRDF/CE GUI to configure a failover cluster. Once configured, the cluster member nodes in the CE cluster can be added as managed Hyper-V hosts in the VMM Server using the VMM Administrator Console. The VSI for Hyper-V GUI can then be used to view the VMs grouped by disaster restart sites. You can also move or migrate a group with VMs to another disaster restart site.

Software requirementsThis section describes the software components and requirements for Virtual Storage Integrator for Hyper-V version 1.0.

Microsoft Windows Server Hyper-VVirtual Storage Integrator for Hyper-V version 1.0 supports Microsoft Windows Server 2008 R2. The minimum supported version of VMM Server is Microsoft System Center Virtual Machine Manager 2008 R2 (version 2.0.4258.0). The Windows Server SCVMM software must be installed prior to installing VSI for Hyper-V.

EMC Solutions EnablerVirtual Storage Integrator for Hyper-V version 1.0 requires that EMC Solutions Enabler version 7.1.0 or higher be installed and configured. Installation of Solutions Enabler software enables the browsing capabilities of Symmetrix and CLARiiON device attributes. Solutions Enabler is required for VSI Server installations only; the VSI Client hosts do not require Solutions Enabler.

Note: If Solutions Enabler version 7.1.0 or higher is not detected when installing VSI, the required Solutions Enabler version 7.1.0 components will be installed/upgraded along with the VSI for Hyper-V Server component.

“VSI for Hyper-V Installation” on page 27 provides prerequisite requirements and installation instructions.

After configuring the Solutions Enabler server, a Storage Discover has to be performed to populate the Solutions Enabler database. A menu option is available for the Storage Discover operation in the VSI client GUI. Refer to “Configuring Solutions Enabler” on page 38 for details on how to set up the Solutions Enabler server.

VSI ServerThe VSI Server is a WMI provider that provides storage abstractions. It communicates with the Solutions Enabler server to discover and map information about storage arrays. The VSI Server includes a base WMI provider and plug-in libraries for Symmetrix and CLARiiON arrays. The VSI Server can only be installed on a host where the

Software requirements 19

supported VMM Server is installed. Refer to the recommended hardware and software requirements for installing and running the VMM server. “Installing Virtual Storage Integrator” on page 32 provides installation instructions for the VSI Server component.

VSI ClientThe VSI Client includes two user accessible components, the GUI and a PowerShell Snap-in. The VSI GUI provides several views that display storage details of managed Hyper-V hosts and VMs from different perspectives. The PowerShell Snap-in can be used to gather storage details of Hyper-V hosts or VMs from the PowerShell command prompt. The VSI GUI is a standalone GUI that provides detailed storage information not available through the VMM Administrator Console.

The VSI Client must be installed on the same host as the VMM Administrator Console. The VMM Administrator console must be installed first. If Windows PowerShell has not previously been installed, the installation of the VMM Administrator Console automatically installs the Windows PowerShell components. Powershell is the command shell used by SCVMM to perform monitoring and management tasks. The VSI Client retrieves information from SCVMM using the PowerShell commands.

Appendix A, “VSI Powershell Commands,” lists the supported VSI Powershell Commands (cmdlets) that can be used to retrieve storage details for hosts and virtual machines that are managed by the SCVMM server. Refer to the recommended hardware and software requirements for installing and running the VMM Administrator Console. “Installing Virtual Storage Integrator” on page 32 provides instructions for installing the VSI Client component.

Symmetrix storage arraysThe Virtual Storage Integrator for Hyper-V supports all EMC Symmetrix storage arrays that are supported with the versions of Solutions Enabler and SCVMM. For detailed interoperability information, refer to the E-Lab Interoperability Navigator:

http://elabnavigator.EMC.com.

For VSI to resolve Symmetrix LUNs properly, all of the front-end ports that are used in the Hyper-V environment must have the SPC-2 flag enabled. Without the SPC-2 flag enabled, the unique World Wide Name (WWN) of each LUN will not report properly, and the plug-in will not be able to identify the LUN in the virtual environment.

To confirm that your current level of EMC Enginuity™ supports the SPC-2 flag, review the Knowledgebase article, emc134969, on EMC Powerlink® at:

Read “Configuring a Symmetrix array” on page 41 for more information about setting the SPC-2 flag.

Additional Symmetrix settings that should be enabled include:

◆ VCM/ACLX if using Volume Logix

◆ SC3 for SCSI-3 interface

◆ UWN for unique WWNs

◆ C bit (C flags) for common serial number when using native failover functionality

Consult your EMC Symmetrix SYMCLI documentation for instructions on enabling these settings.

Note: Consult the EMC Support Matrix for an up-to-date listing of port settings.

CLARiiON storage arraysThe Virtual Storage Integrator for Hyper-V Client currently supports EMC CLARiiON storage arrays running EMC FLARE® release 19 or higher.

Note: For CLARiiON storage arrays running EMC FLARE release 30 or higher, if using Solutions Enabler in Client/Server mode, Solutions Enabler version 7.1.2 or higher is required to be installed on both the client and the server.

Software requirements 21

VSI for Hyper-V loggingVSI for Hyper-V provides detailed logging features and implements a simplified extraction process for the log file data. If there is a problem with VSI for Hyper-V, detailed logs provide EMC Customer Support with the technical information necessary to help diagnose the problem and help VSI engineers with debugging.

VSI for Hyper-V incorporates various logging capabilities to create application detail logs. The amount of detail that these logs contain is controlled by the logging level. The logging level can be adjusted. Refer to “Changing the logging level” on page 24 for more information. Under normal operating conditions, error, warning, and information entries will be written to the application detail log. When verbose logging is enabled, these logs contain enough information to help developers diagnose various application failures.

By default, logs are stored in the C:\Program Files\EMC\VSI For Hyper-V\Logs directory. The latest log file is named vsi_event_trace_current.txt. If both the VSI Server and VSI Client software reside on the same host, logging for the server and client will be in the same log file. When a VSI Client is running on a host different from the VSI Server, the client logging is located on the client host and the server logging is located on the server host.

The stored logs are saved as text files and can be viewed using any text editor. Note that the current log file is an active file and therefore may not contain a complete set of log entries, as some may still be in process. Some text editors may not be able to access the current log file. To obtain a complete copy of the current log file, use the VSI_EventTraceDump.exe program. “Extracting logs” on page 23 provides more detail and some extraction examples.

By default, when the log file exceeds 100 MB in size, it is closed out and renamed from vsi_event_trace_current.txt to vsi_event_trace_yyyymmddhhmmss.txt, where yyyymmddhhmmss is the current date and time. The maximum file size of the log is controlled by a registry key entry and can be changed. “Changing the maximum log file size” on page 25 provides more information.

To help manage logging disk space, older log files are automatically purged. By default, 7 logs are saved. “Changing logging retention period” on page 25 provides additional information on how to control how many logs are saved.

Disk space requirementsThe amount of disk space required depends on the logging level and the amount of VSI activity taking place.

Extracting logsTo extract a current log file, type VSI_EventTraceDump.exe from the command line of the working directory. This extracts the dump file to the designated log directory and names it vsi_event_trace_yyymmddhhmmss.txt, where yyyymmddhhmmss is the current date and time. You can use the -o filename option to change the name of the output file to your desired name.

Examples Each of the following examples assume that the current working directory is C:\Program Files\EMC\VSI For Hyper-V and that the default log directory is C:\Program Files\EMC\VSI For Hyper-V\Common.

Example 1To extract the dump file to the log directory and name it vsi_event_trace_yyyymmddhhmmss.txt, enter:

VSI_EventTraceDump.exe

Example 2To extract a named dump file to a particular location, use the following format:

VSI_EventTraceDump.exe -o C:\filename.txt

Note: Use the -h option to display usage information.

VSI for Hyper-V logging 23

Changing the logging levelThe logging level is controlled by a registry key. To change the logging level, follow these steps:

1. Open a command prompt and enter:

regedit

2. Edit the registry key value for:

HKEY_LOCAL_MACHINE\SOFTWARE\EMC\VSI For Hyper-V\Configuration\EventTraceLevel

By default the level is set to 4. At this level error, warning, and informational messages save to the log file. To create verbose logs, change the value to a 5. At this level error, warning, informational, and verbose messages save to the log file. Be aware that changing this level to a 5 will dramatically increase the amount of data that is sent to the log file. The VSI_EventTrace service does not need to be restarted after changing the logging level. The new value takes effect immediately.

Changing the logging directoryThe logging directory is controlled by a registry key. To change the logging directory, follow these steps:

net stop VSI_EventTrace

2. Then enter:

regedit

HKEY_LOCAL_MACHINE\SOFTWARE\EMC\VSI For Hyper-V\Configuration\EventTraceDirectory

Your edited path must have a trailing backslash and must exist before making this change.

4. Then enter:

net start VSI_EventTrace

Changing logging retention periodThe log retention period is controlled by a registry key. To change the log retention period, follow these steps:

regedit

HKEY_LOCAL_MACHINE\SOFTWARE\EMC\VSI For Hyper-V\Configuration\EventTraceLogRetention

The DWORD value represents the number of logs to keep. The VSI_EventTrace service does not need to be restarted. The new value takes effect immediately.

Changing the maximum log file sizeThe maximum log file size is controlled by a registry key. To change the maximum log file size, follow these steps:

regedit

HKEY_LOCAL_MACHINE\SOFTWARE\EMC\VSI For Hyper-V\Configuration\EventTraceFileMaxSize

The DWORD value represents the file size in MBs. The VSI_EventTrace service does not need to be restarted. The new value takes effect immediately.

VSI for Hyper-V logging 25

2Invisible Body Tag

This chapter explains how to install and uninstall the Virtual Storage Integrator for Hyper-V.

◆ Installation overview......................................................................... 28◆ Installing Virtual Storage Integrator ............................................... 32◆ Uninstalling Virtual Storage Integrator .......................................... 34

VSI for Hyper-VInstallation

VSI for Hyper-V Installation 27

VSI for Hyper-V Installation

Installation overviewThis chapter describes how to install and uninstall Virtual Storage Integrator (VSI) for Hyper-V version 1.0. VSI for Hyper-V version 1.0 currently supports only the Windows x64 architecture. Following a client/server architecture model, the software is installed as two separate VSI components, one for the client, and one for the server.

Before you beginBefore installing VSI for Hyper-V, read the following installation requirements and considerations:

Install SCVMM A minimum supported version of Microsoft System Center Virtual Machine Manager 2008 R2 (version 2.0.4258.0) is required. The VMM Server must be installed prior to installing the VSI Server. The VMM Administrator console must be installed prior to installing the VSI Client.

Microsoft IIS Microsoft Internet Information Services (IIS) is optional for installing the VSI for Hyper-V Server component to display the web location of the VSI for Hyper Client component. Without IIS, the Client component is available from the VSI Server installation location.

Solutions Enablerinstallation

Virtual Storage Integrator for Hyper-V version 1.0 requires that Solutions Enabler version 7.1.0 or higher be installed on hosts that are running the VSI Server. VSI Client-only machines do not require Solutions Enabler. The Solutions Enabler software enables the browsing capabilities for Symmetrix and CLARiiON device attributes and provides the libraries necessary for the VSI to properly discover and map the Symmetrix and CLARiiON storage arrays.

IMPORTANT!If Solutions Enabler is not detected when installing VSI, the required Solutions Enabler version 7.1.0 runtime kit automatically installs along with the VSI for Hyper-V Server component and a client download is provided. Note that the runtime kit installed in this scenario is a scaled down kit that does not include SYMCLI components.

If Solutions Enabler version 7.1.0 or higher is detected when installing VSI, only the VSI Server component is installed and a Client download is provided.

If a version of Solutions Enabler earlier than 7.1.0 is detected, you are prompted to upgrade to the minimum required version 7.1.0 runtime kit to continue the install. A warning displays that proceeding with the VSI install causes certain current Solutions Enabler components (i.e., SYMCLI) to be uninstalled. To manually upgrade Solutions Enabler components prior to installing VSI, click No to exit the install.

Note: After installing VSI for Hyper-V, the installed Solutions Enabler runtime kit may be uninstalled separately and a full Solutions Enabler kit then reinstalled.

The EMC Solutions Enabler Installation Guide provides full installation instructions for installing Solutions Enabler separately from VSI and can be downloaded from the EMC Powerlink website at:

Note: If performing a custom install of Solutions Enabler, the only required components are the Core and Base Storage components.

It is not necessary to have the storage directly connected to the host where VSI is installed. Instead, it is possible to use a Solutions Enabler server elsewhere in the datacenter as the source for storage array information in client/server mode. Even in that case, Solutions Enabler must be installed on the VSI Server host to make the client libraries available, and the appropriate changes made for this Solutions Enabler client to communicate with the Solutions Enabler server installation. The steps required to configure Solutions Enabler for client/server operation can be found in “Configuring Solutions Enabler” on page 38.

Note: Using Virtual Storage Integrator does not require any Solutions Enabler licenses. All Solutions Enabler license checking is disabled for any operations run through the VSI server. “Licensing” on page 38 provides more information.

Installation overview 29

Supported operating systemsVSI for Hyper-V supports the following operating systems:

◆ VSI Server:

• Windows Server 2008

• Windows Server 2008 R2

◆ Hyper-V Hosts:

• Windows Server 2008 with Hyper-V

• Windows Server 2008 R2 with Hyper-V

◆ VSI Client:

• Only supports x64 platforms, including Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows Vista, and Windows Server 2003.

Note: On the Windows Server 2003 x64 platform, only storage viewing capability is available. Disaster restart functionality is not supported.

Domain administratoraccount

VSI for Hyper-V requires the user to have a Domain Administrator account. SCVMM Delegated Administrator users are not supported by VSI.

Figure 2 on page 31 provides an example VSI configuration diagram showing VSI component installation.

Figure 2 VSI installation diagram

Installation overview 31

Installing Virtual Storage IntegratorEnsure that you have read the installation requirements and considerations in “Before you begin” on page 28 before installing the VSI for Hyper-V Server and Client components. Note that both the VSI Server and Client components should be installed on the SCVMM Server host. Additionally, the VSI Client component can be installed on other hosts that have the VMM Administrator Console.

Installing the VSI Server/Client componentsTo install the VSI Server/Client components on the SCVMM Server host:

1. Download the VSI for Hyper-V Server component (EMC_VSI.exe) from the support link on EMC Powerlink at:

Home > Support > Software Downloads and Licensing > Downloads V > Virtual Storage Integrator > Hyper-V

2. Run the EMC_VSI.exe file that was downloaded from EMC Powerlink, following the installation prompts. The InstallShield installation wizard installs all of the necessary files.

Note: If Solutions Enabler is not detected when installing VSI, the required Solutions Enabler version 7.1.0 runtime kit installs along with the VSI for Hyper-V Server component, and a Client download is provided. Note that the runtime kit installed in this scenario is a scaled down kit that does not include SYMCLI components. Refer to “Solutions Enabler installation” on page 28 for considerations on upgrading your Solutions Enabler version when installing VSI.

3. Client download information displays at the end of the Server component install. Launch the Client component install from the location provided.

Note: If IIS is installed on the VSI Server host before installing the VSI Server component, a web page automatically displays a download link for the VSI Client host component for x64 platforms. The Hyper-V Client component link can also be accessed from other hosts that have the VMM Administrator Console.

Note: If IIS was not installed on the VSI Server host, Windows Explorer opens to a locally-saved VSI Client install available at the Server installation location.

4. Reboot the host after VSI Server install completes.

Installing the VSI ClientTo install the VSI Client component:

1. Launch the Client component installation from the location provided at the end of the VSI Server component install.

Note: If IIS is installed, a web browser opens to the following web page for the Client component download: - http://localhost/vsi (This web page is for installing the Client component from the VSI Server host. This page automatically opens at the Server install.)In addition, the Client component is available from other hosts at the following web page:- http://<VSI Server name>/vsi (This page is not opened by the Server install. Go to other hosts to access this web page.)

Note: If IIS is not installed, Windows Explorer opens to location:C:\Program Files\EMC\VSI For Hyper-V\VSI_Client

2. A reboot is required only if installing on Windows Server 2003 x64 platform.

Note: If SCVMM was open during the install, then it must be closed and re-opened in order for VSI to be enabled. No configuration or input is required during the installation other than accepting the prompts to move forward with the install.

Installing Virtual Storage Integrator 33

Uninstalling Virtual Storage IntegratorVirtual Storage Integrator for Hyper-V can be uninstalled either by using the Windows Add or Remove Programs utility for Windows Server 2003, the Programs and Features utility for Windows Server 2008, or by using the Virtual Storage Integrator installer program.

Note: Removing VSI for Hyper-V does not remove Solutions Enabler, which is installed as a separate program. “Uninstalling EMC Solutions Enabler” on page 35 provides instructions.

To uninstall VSI using the Add or Remove Programs utility for Windows Server 2003, follow these steps:

1. Open the Add or Remove Programs utility in the Control Panel by selecting Start > Settings > Control Panel.

2. When the list of currently installed programs loads, select EMC Virtual Storage Integrator for Hyper-V Server or Client.

3. Select Change/Remove and follow the dialogs presented.

To uninstall VSI using the Programs and Features utility for Windows Server 2008, follow these steps:

1. Select Start > Control Panel > Programs > Programs and Features.

2. From the list, select EMC Virtual Storage Integrator for Hyper-V Server or Client.

3. Select Uninstall and follow the dialogs presented.

To uninstall VSI using the VSI installer, follow these steps:

1. Open the Virtual Storage Integrator installer program that was previously downloaded.

2. When prompted by the Program Maintenance dialog, select Remove and click Next. Follow the dialogs presented to complete the uninstall.

Uninstalling EMC Solutions EnablerSolutions Enabler can be uninstalled by using the Windows Add or Remove Programs utility for Windows Server 2003, or the Programs and Features utility for Windows Server 2008.

To uninstall EMC Solutions Enabler using the Add or Remove Programs utility for Windows Server 2003, follow these steps:

1. Open the Add or Remove Programs utility in the Control Panel by selecting Start > Settings > Control Panel.

2. When the list of currently installed programs loads, select the EMC Solutions Enabler listing.

3. Select Change/Remove and follow the dialogs presented.

To uninstall Solutions Enabler using the Programs and Features utility for Windows Server 2008, follow these steps:

1. Select Start > Control Panel > Programs > Programs and Features.

2. From the list, select EMC Solutions Enabler.

3. Select Uninstall and follow the dialogs presented.

Uninstalling Virtual Storage Integrator 35

3Invisible Body Tag

This chapter explains the configuration options available for Virtual Storage Integrator for Hyper-V.

◆ Configuring Solutions Enabler......................................................... 38◆ Discovering storage arrays ............................................................... 46

VSI Configuration

VSI Configuration 37

VSI Configuration

Configuring Solutions EnablerThis section describes how to configure Solutions Enabler for use with VSI. VSI for Hyper-V requires Solutions Enabler for managing Symmetrix and CLARiiON arrays, as it provides the necessary client libraries and performs storage inquiry commands on the storage array.

If the local installation of the Solutions Enabler has direct access to the arrays providing storage to the VMM Servers, both of the functions can be provided by the local installation of the Solutions Enabler. However, if the host running the client does not have direct access to the arrays, then you require a remote Solutions Enabler server with access to the storage area network and the appropriate storage arrays.

There are various aspects to Solutions Enabler configuration that depend on whether you use a local or remote Solutions Enabler database. Certain Solutions Enabler configurations require additional configuration after installing Solutions Enabler, and these scenarios are described in the sections that follow.

LicensingVSI does not require any Solutions Enabler licenses. All Solutions Enabler license checking will be disabled for any operations run through the VSI server. This means that Solutions Enabler licenses are not required on the VSI client host. If running in Solutions Enabler in local mode, licenses are required on the VSI Server host to perform SYMCLI operations. If running in Solutions Enabler in client/server mode, licenses are not required on the VSI Server host, but they are required on the Solutions Enabler Server host to perform SYMCLI operations.

Note: Licenses are required if you plan to use Solutions Enabler outside of VSI, such as through the command line interface (SYMCLI).

VSI Configuration

Local modeUsing Solutions Enabler in local mode means that the Solutions Enabler database will be maintained on the local host. Furthermore, all required connections to storage arrays will need to be made from the local host. For this reason, local mode is only supported with server operating systems that EMC supports for connection to their storage arrays. Client and desktop operating systems such as Windows XP, Windows Vista, and Windows 7 are not supported in this mode.

Note: For SRDF, only storage arrays on one site are required to be connected to the local host.

Advantages The following are the advantages to using Solutions Enabler in local mode:

◆ Local mode is straightforward. There are no additional configuration steps required.

◆ There is no need to build and maintain a secondary host, thus reducing complexity of the solution.

Setup For Solutions Enabler to perform an in-band discovery of an EMC Symmetrix storage array in local mode, at least one LUN from that storage array must be accessible to the local host. Symmetrix arrays can only be discovered in-band; this means that at least one LUN must be accessible for that Symmetrix array. CLARiiON arrays are discovered over the TCP/IP network, so an accessible CLARiiON LUN is not required.

Note: If the local host is a virtual machine, then all LUNs used for in-band discovery must be SCSI Pass Through Devices so that they are not masked underneath NTFS. The SCSI filtering functionality for the VM must also be disabled. Refer to the EMC Symmetrix with Microsoft Hyper-V Virtualization White Paper for details on disabling SCSI filtering.

Configuring Solutions Enabler 39

VSI Configuration

Remote mode or client/server modeWhen using Solutions Enabler in a client/server configuration, the Solutions Enabler database is maintained on a remote Solutions Enabler server. All required connections to the storage arrays must be made from that remote server.

Note: For SRDF, only storage arrays on one site are required to be connected to the remote SE server.

Advantages One advantage to using a remote Solutions Enabler server is that a single, centralized Solutions Enabler server can service various clients and applications (including VSI), thus reducing infrastructure costs, complexity, and improving security.

Disadvantages The following are the disadvantages to using a remote Solutions Enabler server:

◆ A separate host must be configured as the Solutions Enabler server (the Solutions Enabler Virtual Appliance can lessen this investment cost).

◆ Additional steps must be taken on both the Solutions Enabler server and the client machine to properly configure the security relationship.

◆ Depending on the port used for the Solutions Enabler server, additional network changes may be required to configure firewalls, proxies, etc.

Setup When configuring a remote Solutions Enabler server, the first step is to install and start the Solutions Enabler server daemon (storsrvd). Without this service, your client cannot connect to the Solutions Enabler server. If this service was not created during Solutions Enabler installation, it can be created with the following Solutions Enabler command:

stordaemon install storsrvd -autostart

This service can then be started with the following command:

stordaemon storsrvd start

For Solutions Enabler to perform an in-band discovery of a storage array in remote mode, at least one LUN from that storage array must be accessible to the remote Solutions Enabler server. Symmetrix

VSI Configuration

arrays can only be discovered in-band; this means that at least one LUN (preferably more) must be accessible for that Symmetrix array.

CLARiiON arrays are discovered over the TCP/IP network, so an accessible CLARiiON LUN is not required.

Note: For CLARiiON® storage arrays running EMC FLARE® release 30 or higher, if using Solutions Enabler Client/Server mode, Solutions Enabler version 7.1.2 or higher is required to be installed on both the client and the server.

Note: If the local host is a virtual machine, then those LUNs must be SCSI Pass Through Devices so that they are not masked underneath the NTFS. The SCSI filtering functionality for the VM must also be disabled. Refer to the EMC Symmetrix with Microsoft Hyper-V Virtualization White Paper for details on disabling SCSI filtering.

Security considerationsBy default, all communication between VSI and the Solutions Enabler server is secured using SSL. Additionally, the Solutions Enabler server verifies the client's certificate before permitting connection. More information regarding these security settings, as well as others, can be found in the EMC Solutions Enabler Installation Guide available on EMC Powerlink.

Configuring a Symmetrix arrayFor VSI to properly resolve Symmetrix array LUNs, all of the front-end ports being used in the Hyper-V environment must have the SPC-2 flag enabled. Without the SPC-2 flag enabled on the Symmetrix array front-end ports, the unique WWN of each LUN is not properly reported, and VSI cannot identify the LUNs in the virtual environment. Confirm that your current level of Enginuity supports the SPC-2 flag by reviewing Knowledgebase article emc134969 on EMC Powerlink.

The host that is going to serve as the Solutions Enabler server (either local or remote) must have access to at least one LUN, preferably a gatekeeper (GK) device, from each Symmetrix array that needs to be resolved. If possible, it is recommended to have more than one gatekeeper accessible from each Symmetrix array. Without this LUN, Solutions Enabler will not be able to discover the array, and therefore VSI will not be able to resolve the devices.

VSI Configuration

Additional Symmetrix settings that should be enabled include:

◆ VCM/ACLX if using Volume Logix

◆ SC3 for SCSI-3 interface

◆ UWN for unique WWNs

◆ C bit (C flags) for common serial number when using native failover functionality

Consult your EMC Symmetrix SYMCLI documentation for instructions on enabling these settings.

Note: Consult the EMC Support Matrix for an up-to-date listing of port settings.

Configuring a CLARiiON arrayThere are no additional steps needed to configure a CLARiiON array for use with VSI.

Configuring the Solutions Enabler ServerThe VSI for Hyper-V client GUI provides a configuration option for using Solutions Enabler locally or remotely. Solutions Enabler Server settings for VSI are displayed under the Storage Configuration view and Solutions Enabler Server tab.

To configure the Solutions Enabler Server:

1. Open the VSI for Hyper-V GUI. The Enter a SCVMM Server to Connect page appears. Figure 3 shows an example.

Figure 3 Enter a SCVMM Server to Connect

VSI Configuration

2. To connect to the SCVMM Server on the local host, click Connect. Or enter the name of the SCVMM Server to connect and click Connect. To save the server name as the default dialog display, check the Make this server my default box.

3. The EMC Virtual Storage Integrator for Hyper-V main page and Navigation tree appears. Figure 4 on page 43 shows an example.

Figure 4 EMC Virtual Storage Integrator for Hyper-V main page

4. Select the SCVMM Server icon in the Hyper-V Hosts column to expand the navigation tree. Then select the SCVMM Server node. The Storage Configuration page appears. Figure 5 shows an example.

VSI Configuration

Note: The Storage Configuration page only displays in the VSI client GUI if running on a SCVMM server host.

Figure 5 Storage Configuration Solutions Enabler Server tab

5. If using Solutions Enabler in local mode, no configuration changes are necessary. To configure for remote client/server mode, check the Configure Solutions Enabler Connection check box.

6. Enter the Remote Server Name and Port number in the boxes provided.

7. Click the Test Connection button to test the validity of the remote connection.

Note: If the remote connection is not valid, an error message displays.

8. If the remote connection is valid, click the Save Connection button to save the connection.

Note: You must save the remote connection to be used by VSI or the local Solutions Enabler connection is used by default.

Note: Username and Password are not required for configuring a remote node connection.

VSI Configuration

9. If this is the first time connecting to this SCVMM Server, after the connection is made, click the Storage Discover button to discover EMC storage.

Removing a Solutions Enabler remote connectionTo remove a Solutions Enabler remote connection, click the Remove Connection button. This removes the remote connection from VSI for Hyper-V.

VSI Configuration

Discovering storage arraysThe Storage Configuration view provides a means for discovering storage arrays as described in the following two sections for Symmetrix and CLARiiON arrays.

Symmetrix arraysAfter configuring the Solutions Enabler Server as described in “Configuring the Solutions Enabler Server” on page 42, click the Storage Discover button as shown in Figure 5 on page 44. This discovers all storage arrays connected to the server that is running Solutions Enabler. This option is also available through the right-click menu when selecting a Server Node.

When you first connect to a SCVMM server using the VSI client GUI, the VSI client attempts to resolve the devices that are mapped to each VM host. If storage information for an EMC device cannot be found, a message displays informing you that a Storage Discover is required.

After selecting the Storage Discover menu option or button and completing the Discover process, updated storage details display in the VSI GUI.

Note: iSCSI devices are not supported by VSI.

CLARiiON arraysThe Storage Configuration view and CLARiiON Assisted Discovery tab provides the ability to perform an assisted discover of CLARiiON arrays. Assisted Discovery indicates that you have directed Solutions Enabler to a particular storage array, with all discovery being performed over the TCP/IP network. When you select the CLARiiON Assisted Discovery tab, the VSI client retrieves all CLARiiON arrays already discovered, as well as the authorization lists currently stored in the Solutions Enabler database and displays them in the list. Figure 6 on page 47 provides an example.

The Assisted Discovery tab allows you to input the IP address of the CLARiiON storage processors (SPA and SPB), as well as the username and password for gaining access to the CLARiiON array. After populating these fields, clicking the Discover New CLARiiON Array button discovers the new CLARiiON array. Each CLARiiON array discovered is added to the CLARiiON arrays list.

VSI Configuration

Figure 6 Storage Configuration CLARiiON Assisted Discovery tab

As part of the Assisted Discovery, VSI adds the user credentials to Solutions Enabler for the purpose of discovering the CLARiiON array. If Solutions Enabler already contains user credentials for these storage processors, the Solutions Enabler's user credentials will be overwritten with the ones entered.

Removing a CLARiiON array from the Solutions Enabler databaseTo remove a CLARiiON array from the Solutions Enabler database, right-click on the CLARiiON array and select Remove ArrayID. Figure 7 provides an example.

Figure 7 CLARiiON Assisted Discovery tab remove array

Discovering storage arrays 47

VSI Configuration

4Invisible Body Tag

This chapter explains how to use the Virtual Storage Integrator for Hyper-V Client GUI to view information and perform a disaster restart.

◆ Getting started with VSI ................................................................... 50◆ Viewing EMC storage........................................................................ 54◆ Disaster Restart................................................................................... 68

Using the VSI forHyper-V Client GUI

Using the VSI for Hyper-V Client GUI 49

Using the VSI for Hyper-V Client GUI

Getting started with VSIThis section explains how to connect VSI to a SCVMM Server and how to use the VSI for Hyper-V Client navigation tree for viewing storage information. The VSI navigation tree presents information in a similar format to that of the VMM Administrator Console.

Connecting to an SCVMM ServerTo use the VSI for Hyper-V Client GUI, you must first connect to an SCVMM Server. Open the VSI for Hyper-V GUI to access the Enter a SCVMM Server to Connect page. Figure 8 shows an example.

Figure 8 Connecting to a SCVMM Server

To connect to the SCVMM Server on the local host, click Connect. Or enter the name of the SCVMM Server to connect and click Connect. To save the server name as the default dialog display for the next time, open the GUI, and check the Make this server my default box. The VSI for Hyper-V main page and Navigation tree appears. Figure 9 on page 51 shows an example.

Note: If this is the first time connecting to this SCVMM Server, after the connection is made, perform a Storage Discover operation to discover EMC storage.

Figure 9 VSI for Hyper-V main page

VSI navigation treeThe VSI navigation tree for Hyper-V Hosts appears in the left-hand pane of the GUI. From the navigation tree, you can view EMC storage information for standalone hosts, clusters, and library servers. Click the SCVMM Server icon in the Hyper-V Hosts pane to expand the tree view. Selecting the Server node, further expands the tree to expose folders for All Hosts, EMC Storage, and Library Servers. Figure 10 on page 52 shows an example of the navigation tree.

At the bottom of the pane are two buttons: EMC Storage and Disaster Restart. By default, EMC Storage is automatically selected, which presents storage details for Hyper-V hosts and virtual machines. Host Groups are represented by folders in the navigation pane under the SCVMM Server name. The VSI client retrieves information for Hyper-V hosts and virtual machines from the SCVMM Server.

Getting started with VSI 51

Figure 10 VSI Hyper-V Hosts navigation pane

Figure 10 shows a SCVMM Server named API3144 with the EMC Storage button selected. Under the server name, is a folder named All Hosts. Under the All Hosts folder, there are additional folders for standalone hosts and cluster hosts.

All Hosts is the master Host Group for all virtual machine hosts. Additional Host Groups can be created under the All Hosts folder and hosts added to them using the VMM Administrator Console. If custom Host Groups are created in the VMM Administrator Console, they can be viewed under the same Host Group hierarchy in the VSI GUI.

There is an EMC Storage folder under the SCVMM Server name. It displays all EMC Symmetrix and CLARiiON storage arrays connected to hosts managed by this SCVMM Server. There is also a Library Server folder. It displays library servers and library objects, including templates, Virtual Hard Disks, and ISO's, managed by this SCVMM Server.

In the example shown in Figure 11, selecting the standalone host folder further expands host l82aq228.apiad.com to expose additional folders for viewing the Volumes, LUNs, Targets, and Virtual Machines available on the host. Selecting the clusterhosts folder further expands cluster host VMCLUS145 to expose additional folders for viewing the Volumes, Nodes, and Virtual Machines available in the cluster. Hosts and clusters display in the tree the same way as in the VMM Administrator Console.

Figure 11 Expanded VSI navigation tree

Getting started with VSI 53

Viewing EMC storageThis section describes the storage details that display when you select the EMC Storage button for various objects in the navigation tree. Storage can be viewed for volumes, LUNs, targets, virtual machines, EMC storage, and library servers.

Viewing volumesThe Volumes view displays all Windows volumes on a standalone host or a cluster. Figure 12 on page 55 shows an example. The following table columns display for each volume:

◆ Volume — Shows the volume mount point.

◆ CSV Path — Shows the path of the cluster shared volume, if applicable.

◆ Host — Shows the name of the host.

◆ Label — Shows the label for this volume.

◆ File System — Shows the file system type for this volume, such as NTFS.

◆ Capacity — Shows the capacity of this volume in MB or GB.

◆ Free Space — Shows the free space for this volume in MB or GB.

◆ Volume GUID — Shows the volume GUID.

When a specific volume is selected, detailed LUN information for the volume displays in the Storage tab below. If the selected volume is comprised of multiple LUNs, a list of the constituent LUNs displays.

The following properties display in the table for each LUN:

◆ Physical Drive — Shows the physical drive number of the LUN on this host.

◆ Product — Shows the product type of the storage platform such as Symmetrix or CLARiiON.

◆ Array — Shows the storage array ID for the LUN.

◆ Device ID — Shows the device ID for the LUN.

◆ Device Status — Shows the device status of a LUN, i.e., Ready, Write-disabled, etc.

◆ WWN — Shows the World Wide Name for the LUN.

◆ Type — Shows the device type for the LUN, such as BCV, VDEV, R1, etc.

◆ RAID — Shows the RAID level for the LUN.

◆ Meta — Indicates whether the LUN is a Meta LUN. If it is, it indicates the type, such as concatenated or striped.

◆ Group — Shows the storage group for CLARiiON or initiator group for Symmetrix to which the LUN is assigned.

◆ VP — Indicates whether the LUN is virtually provisioned.

Figure 12 Viewing volumes on a host

Switching to the Virtual Machine tab in the lower pane displays detailed VM information on the selected volume. If there is more than one VM utilizing space for virtual hard disks on this volume, a list of the relevant VMs display.

The following columns are shown for each VM:

◆ Name — Shows the name of the VM.

◆ Host — Shows the host of the VM.

◆ Location — Shows the physical location of the VM.

◆ Host Group Path — Shows the full host group path of this VM.

◆ Status — Shows the status of this VM, i.e., Running, Stopped, etc.

Viewing EMC storage 55

If a cluster is selected, only one Volume view is displayed for the entire failover cluster. VSI retrieves information for each volume from the cluster member node, where the corresponding disk resource is online. In a failover cluster, a volume can only be on a single disk. As shown in Figure 13 there are 4 volumes in cluster clus3190-91 shown in the VSI GUI.

Figure 13 Example of a four volume cluster

Viewing LUNsThe LUNs view displays LUN information in three separate window panes, each providing additional details for the selected device. Initially the view begins with the storage array and exposes further details down to the device level. Figure 14 on page 57 shows an example. The following table columns display for each storage array:

◆ Model — Shows the model of the storage platform, such as DMX2, VMAX CX3, etc.

◆ Version — Shows the microcode version. This represents the Enginuity level for Symmetrix and the FLARE level for CLARiiON.

Figure 14 Viewing LUNs on a host

When a storage array is selected in the top pane, all the arrays LUNs mapped to this host display in the middle pane. The following columns display for each LUN:

◆ Physical Drive — Shows the physical drive number for the LUN on this host.

When a LUN is selected, more detailed information about the LUN displays in the bottom pane. The following columns display for each LUN:

◆ Mount Points — Shows the all mount points for this LUN.

◆ Device Status — Shows the device status of the LUN, i.e., Ready, Write-disabled, etc.

◆ Capacity — Shows the capacity of the LUN in MB or GB.

◆ VP — Indicates whether or not the LUN is virtually provisioned.

Viewing targetsThe Targets view displays information for all storage adapters connected to the host in three separate window panes, beginning with the storage array and filtering down to the LUN level. Figure 15 on page 59 shows an example. The following table columns display for each storage array:

Note: VSI for Hyper-V does not currently support Hyper-V hosts with multiple paths to storage. When viewing target LUN information, LUNs display down one path only.

Figure 15 Viewing Targets on a host

When a storage array is selected in the top pane, all targets on this array display in the middle pane. The following columns display for each target:

Target — Shows the name of the target.

Port — Shows the port for the target.

Product — Shows the product type of the storage platform such as Symmetrix or CLARiiON.

Array — Shows the storage array ID for the LUN.

World Wide Name — Shows the World Wide Name for the target.

There are some additional array-specific information displays for each target depending on the storage array. For a Symmetrix array, the following recommended flags for a VM environment display:

◆ VCM/ACLX — Indicates whether the VCM or ACLX flag is enabled on the target.

◆ SPC-2 — Indicates whether the SPC-2 flag is enabled on the target.

◆ SCSI-3 — Indicates whether the SCSI-3 flag is enabled on the target.

◆ UWN — Indicates whether the UWN flag is enabled on the target.

◆ C — Indicates whether the C flag is enabled on the target.

A color-coded green or red icon displays for each of the above flags settings. Figure 16 shows an example. A green icon indicates the current flag setting is the recommended setting. A red icon indicates the current flag setting is not the recommended setting. When a red icon is moused-over, a message displays the recommended setting.

Figure 16 Viewing Target information

For CLARiiON, the following additional information displays:

◆ IP Address — Shows the IP address for a SPA or SPB.

When a target is selected, all LUNs mapped to the target display in the bottom pane. The following columns displayed for each LUN:

◆ Mount Points — Shows all mount points for this LUN.

Viewing virtual machinesThe Virtual Machines view displays information for virtual machines running on a standalone host or a failover cluster under the Virtual Machines folder. When a specific virtual machine is selected, a two-pane view displays in the right-side window.

Figure 17 on page 62 shows an example. The following table columns are displayed for each virtual machine:

◆ Location — Shows the physical location of the VM.

◆ Host — Shows the host of the VM.

◆ Status — Shows the status of the VM, whether it is running, stopped, etc.

◆ OS Name — Shows the name of the operating system installed on the VM, such as W2K8 R2.

◆ OS Version — Shows the version of the operating system installed on the VM, such as 6.1.7600.

◆ System Type — Shows the system type of the operating system installed on the VM, such as x64.

Figure 17 Viewing Virtual Machine information

A list of devices are shown in the bottom pane. These are devices for VHD, config file, and Passthrough. The following columns display for each device:

◆ Device Type — Shows the type of the devices, such as VHD, config file, or Passthrough.

◆ VP — Indicates whether the LUN is virtually provisioned.

◆ Group — Displays the storage group for CLARiiON or initiator group for Symmetrix to which the LUN is assigned.

By dragging the Device Type column header to the area above the column headers, the devices can be grouped by Device Types such as VHD, Passthrough, etc. As shown in Figure 17 on page 62, there are three Passthrough devices in the cluster clus3190-91.

Viewing EMC storageThe Storage view provides EMC storage array summary information. The Storage folder in the navigation tree contains folders for each product name. Listed under each product name are all storage arrays belonging to that product, which are connected to hosts that are managed by this SCVMM Server. When a specific array is selected in the navigation tree, a three-pane window view displays in the right window. Figure 18 on page 64 shows an example. The following detailed information about the selected array displays in the top pane:

◆ Product — Shows the product type of the storage platform, such as Symmetrix or CLARiiON.

Figure 18 Viewing EMC storage

Hosts connected to the selected storage array display in the middle pane. The following columns are shown for each host:

◆ Host — Shows the name of the host.

◆ OS Name — Shows the name of the operating system installed on the host, such as W2K8 R2.

◆ OS Version — Shows the version of the operating system installed on the host, such as 6.1.7600.

◆ System Type — Shows the system type of the operating system installed on the host, such as x64.

When a specific host is selected from the middle pane, all LUNs on the selected array that are mapped to the host display. The following properties are shown for each LUN:

◆ Product — Shows the product type of the storage platform, such as Symmetrix or CLARiiON.

Viewing library serversThe Library Server view provides summary information for SCVMM Library Servers that use storage visible to the VSI Server. Information displays in a two-pane view in the right-side window. Figure 19 on page 66 shows an example. The top pane displays all library objects including template, Virtual Hard Disk, and ISOs that are managed by this SCVMM Server. The following columns display for each library object:

◆ Name — Displays the name of the library object.

◆ Library Server — Displays the name of the library server for this library object.

◆ Type — Displays the type of this library object, such as Template, Virtual Hard Disk, etc.

◆ Product — Shows the product type of the storage platform such as Symmetrix or CLARiiON for the LUN used by this library object. This field will be empty if the object is not on a LUN managed by VSI.

◆ Array — Shows the storage array ID for the LUN used by this library object. This field will be empty if the object is not on a LUN managed by VSI.

◆ Device ID — Shows the device ID for the LUN used by this library object. This field will be empty if the object is not on a LUN managed by VSI.

Figure 19 Viewing library servers

When a library object is selected in the top pane, more detailed information about the selected object displays in the bottom pane. The following column information displays:

◆ Owner — Displays the owner of this library object.

◆ Type — Displays the type of this library object, such as Template, Virtual Hard Disk, etc.

◆ Share Path — Displays the share path of this library object.

◆ Operating System — Displays the operating system of the LUN where this library object resides.

◆ Status — Displays the status of this library object, such as Normal, etc.

VSI supports Library Servers in the following described configuration. When the SCVMM Server is stated in the below list, it refers to the SCVMM Server where the specified Library Server resides:

◆ The Library Server can be a Hyper-V host managed by this SCVMM Server.

◆ The Library Server can be a Virtual Machine hosted by a Hyper-V host managed by this SCVMM Server.

◆ The Library Server can be another physical host that is not a Hyper-V host in this SCVMM.

VSI supported operating systems for the Library Server are Windows Server 2008 x64 or Windows Server 2008 R2 x64. For VSI to display storage details, the Library Server must use storage that is visible to the VSI Server.

Refreshing informationA Refresh option at the SCVMM Server name level refreshes information on all Hyper-V hosts and virtual machines that are managed by the SCVMM Server, as well as information on EMC Storage and Library Servers. A Refresh option at a host level refreshes information on that host only. A Refresh option at a cluster level refreshes information on all cluster member nodes.

Disaster RestartVSI can be integrated with EMC SRDF/Cluster Enabler (SRDF/CE) software (version 4.0 and higher) to support disaster restart of failover clusters, thus extending disaster restart to support Hyper-V child virtual machine partitions. SRDF/CE expands cluster storage and management capabilities while ensuring disaster recovery and business continuance protection for Symmetrix storage arrays.

When integrated with SRDF/CE, VSI for Hyper-V displays Virtual Machines that reside on different Disaster Restart sites. Virtual Machines from different CE clusters can be online on the same site. VSI for Hyper-V examines all the CE clusters managed by the SCVMM Server and utilizes a user-defined site name in CE to group Virtual Machines. Each Virtual Machine is contained in a cluster resource group and each group resides on one site.

Note: EMC SRDF/Cluster Enabler Base Component version 4.0 does not currently support Cluster Shared Volumes (CSV). The EMC SRDF/Cluster Enabler Base Component Release Notes provides more information.

The following rules apply to using VSI for Hyper-V with SRDF/CE for disaster restart functionality:

◆ VSI for Hyper-V and Cluster Enabler cannot co-exist on the same host.

◆ Only CE clusters are supported. Failover clusters that are not managed by CE are not supported. Failover Clusters with Hyper-V hosts that are managed by the SCVMM Server are supported.

◆ Although SRDF/CE supports a range of operating systems, only failover clusters comprised of Windows Server 2008 or Windows Server 2008 R2 systems with Hyper-V 64 bit are supported.

◆ Although CE supports all cluster models, only Node and File Share Majority cluster models are currently supported.

◆ Since CE supports geographically dispersed Failover Clusters, only LUNs with remote mirrors are supported in a CE environment.

Integrating VSI with Cluster EnablerThis section describes how to integrate VSI for Hyper-V with SRDF/CE for disaster restart functionality.

To integrate VSI for Hyper-V with SRDF/CE:

1. Using Microsoft Failover Cluster software, create a one node Failover Cluster.

Note: For this example, these instructions assume that the following steps are executed on a single node, referred to as Node A. By default Node A utilizes a Node Majority cluster model.

2. Change the cluster model to Node and File Share Witness Majority.

3. Add Storage in Failover Cluster. Ensure that all disks can be brought online on Node A.

4. Ensure that all disks are write enabled on Node A. For Symmetrix arrays, all disks must be in Synchronized or Consistent state and all disks used by Node A are configured to be in an R1 device state.

5. Install SRDF/CE on all nodes that are part of the Failover Cluster.

6. Create Virtual Machines using LUNs with remote mirrors.

7. Use Microsoft Failover Cluster software to configure the Virtual Machines so that they will be managed by the cluster.

Note: Refer to the Hyper-V Support section in the EMC SRDF/Cluster Enabler Product Guide for instructions on how to configure CE with Hyper-V.

8. Run the SRDF/CE Configuration Wizard to add the remaining nodes to the cluster and convert the groups, including the group with Virtual Machines.

9. Optional: After the Configuration Wizard completes, open the SRDF/CE GUI to change site names.

10. In the VMM Administrator Console, add one of the member hosts of the Failover Cluster to be managed by the VMM Server. By doing so, the entire Failover Cluster is added by the VMM Administrator Console.

Disaster Restart 69

11. Open the VSI for Hyper-V GUI, go to the Disaster Restart tab in the left pane. Now Disaster Restart sites with Virtual Machines display in the middle pane.

Renaming sitesBy default, the site names display as Site1 and Site2. Sites are automatically assigned, based on the node and storage array. The SRDF/CE software iterates through cluster member nodes and checks the storage arrays that are attached to each node.

The first cluster member node in the list is assigned to Site1. The remaining nodes are then evaluated for appropriate site placement.

Site names can be changed using the SRDF/CE GUI. Open the CE GUI and expand the tree nodes in the left-hand pane, right click on a Site and a select the Rename option. Since the Configure Wizard is run in the single cluster context, there are situations where the site names in multiple clusters may conflict with each other. Table 1 provides an example of two CE clusters with default site names:

Note: In Table 1, array 000187900830 is in Site1 in the cluster Clus9190 and also in Site2 in the cluster Clus8988. VSI for Hyper-V cannot display consistent information for the DR sites in this case. The Site names must be changed.

Table 2 on page 71 provides an example of the renamed sites.

Table 1 Two cluster example with default naming

Cluster Name DR Sites Storage Arrays DR Groups Hosts Virtual Machines

Clus9190 Site 1 000187900830 Group 1 Api3191 VM1, VM2

Site 2 000187900848 Group 2 Api3190 VM_Grp2

Clus8988 Site 2 000187900830 L82aq189

Site 1 000187900848 Group 3 L82aq188 VM3, VM4

Note: After renaming the sites, VSI for Hyper-V properly displays the DR site information. VM1 and VM2 in Group 1 are displayed under the DR site Hopkinton. VM_Grp2 in Group 2 and VM3 and VM4 in Group 3 are displayed under the DR site Westboro.

Cluster configurationsThis section provides a few examples to illustrate the relationship between the Disaster Restart sites and CE cluster configurations. To properly display in the VSI for Hyper-V GUI, DR Sites and cluster configurations must be appropriately named and organized. Table 3 provides a four site cluster configuration example.

Table 2 Two cluster example with renamed sites

Cluster NameRenamed DR

Sites Storage Arrays DR Groups Hosts Virtual Machines

Clus9190 Hopkinton 000187900830 Group 1 Api3191 VM1, VM2

Westboro 000187900848 Group 2 Api3190 VM_Grp2

Clus8988 Hopkinton 000187900830 L82aq189

Westboro 000187900848 Group 3 L82aq188 VM3, VM4

Table 3 Four DR Site example

Clus6970 Boston 000190300098 Group 5 Api3191 VM5

Providence 000190100860 Api3070

Disaster Restart 71

Note: In Table 3 on page 71, there are four DR sites: Hopkinton, Westboro, Boston, and Providence. For example, VM1 and VM2 in Group 1 display under the DR site Hopkinton in the VSI for Hyper-V GUI. VM_Grp2 in Group 2 and VM3 and VM4 in Group 3 display under the DR site Westboro. VM5 in Group 5 displays under the DR site Boston.

Table 4 provides a negative test case example of a four site cluster configuration with storage on multiple clusters, where VSI for Hyper-V cannot properly display DR site information for all sites.

Note: In Table 4, since storage array 000187900830 is on the DR site Hopkinton in the cluster Clus9190, and it is also on the DR site Westboro in the cluster Clus8988, VSI cannot group them together by sites. In this case, only the DR sites Boston and Providence display in the VSI for Hyper-V GUI.

Viewing Disaster Restart sitesAll DR sites in the SCVMM Server can be viewed from the Sites folder located in the Navigation pane of the VSI for Hyper-V GUI.

When selecting a specific DR site, a multiple-pane view displays in the right side window. The top pane displays all cluster resource groups on this site. Figure 20 on page 73 shows an example. The following columns display for each site:

◆ Group Name — Displays the cluster resource group name that contains Virtual Machines in it.

◆ Status — Displays the status for the group, such as online, offline, etc.

Table 4 Four DR Site example with storage on multiple clusters

Clus6970 Boston 000190300098 Group 5 Api3069 VM5

Providence 000190100860 Api3070

◆ Replication Mode — Displays the replication mode of the group, such as synchronous, asynchronous, etc.

◆ Sync State — Displays the sync state of the group, such as Synchronized, Consistent, Failed Over, etc.

◆ Remote Array — Displays the array ID on the remote site.

◆ Owning Node — Displays the owning node of the group.

◆ Cluster Name — Displays the cluster name.

◆ Remote Site — Displays the remote site name.

There are two tabs located at the top of the middle pane, the Virtual Machine tab and the Storage tab. By default, the Virtual Machine tab is selected and a three-pane view displays. Figure 20 shows an example.

Figure 20 Viewing DR site information - Virtual Machine tab

Selecting a group in the upper pane of the Virtual Machine tab displays all VMs in this group in the middle pane. The following columns display for each VM:

◆ Name — Displays the name of the VM.

◆ Host — Displays the host that is hosting the VM.

◆ Location — Displays the location of the VM.

Disaster Restart 73

◆ Host Group Path — Displays the host group path of this VM.

◆ Status — Displays the status of the VM, such as Running, Stopped, etc.

◆ OS Name — Displays the operating system name installed on the VM.

◆ OS Version — Displays the operating system version of the VM.

◆ System Type — Displays the architecture of the operating system on the VM, such as x64, x86, etc.

Selecting a VM displays all LUNs used by the VM in the bottom pane. These are LUNs for VHD, config file, and Passthrough devices. The following columns display for each LUN:

◆ Device Type — Displays the type of the devices, such as VHD, config file, or Passthrough.

◆ Physical Drive — Displays the physical drive number of the LUN on this host.

◆ Product — Displays the product type of the storage platform such as Symmetrix or CLARiiON.

◆ Array — Displays the storage array ID for the LUN.

◆ Device ID — Displays the device ID for the LUN.

◆ Mount Points — Displays all mount points for this LUN.

◆ Type — Displays the device type for the LUN, such as BCV, VDEV, R1, etc.

◆ RAID — Displays the RAID level for the LUN.

◆ Meta — Indicates if the LUN is a Meta LUN. If it is, it indicates the type, such as concatenated or striped.

◆ VP — Indicates if the LUN is virtually provisioned.

Right-clicking on a group name displays menu options for Live migrate virtual machine to another node, Quick migrate virtual machine(s) to another node, and Move virtual machine(s) to another node. Figure 21 shows an example. Menu options are also available from the right-side Action pane and the top menu bar. The three selections provide a mechanism to relocate the VM to an alternate node, although each uses a different mechanism to achieve the VM movement. Refer to the Hyper-V high availability documentation provided by Microsoft for additional information on the mechanisms used.

Note that Failover Cluster target nodes only supports the live migration of one virtual machine at a time. If a group to be live migrated contains more than one virtual machine, VSI does not perform the operation. Live migration is only supported for synchronous replication. Quick migration and move operations are supported for both synchronous and asynchronous replication.

Note: Live Migration is only supported on Windows Server 2008 R2 platforms.

Figure 21 Viewing sites - right-click menu options

If the Storage tab is selected, a two-pane view displays and all LUNs used by the selected group display in the bottom pane. Figure 22 on page 76 shows an example. The following columns display for each LUN:

◆ Device Type — Displays the type of the devices, such as VHD, config file, or Passthrough.

◆ Physical Drive — Displays the physical drive number of the LUN on this host.

◆ Product — Displays the product type of the storage platform such as Symmetrix or CLARiiON.

◆ Array — Displays the storage array ID for the LUN.

Disaster Restart 75

◆ Device ID — Displays the device ID for the LUN.

◆ Mount Points — Displays all mount points for this LUN.

◆ Type — Displays the device type for the LUN, such as BCV, VDEV, R1, etc.

◆ RAID — Displays the RAID level for the LUN.

◆ Meta — Indicates if the LUN is a Meta LUN. If it is, it indicates the type, such as concatenated or striped.

◆ VP — Indicates if the LUN is virtually provisioned.

◆ Group — Displays the storage group for CLARiiON or initiator group for Symmetrix that the LUN is assigned to.

Figure 22 Viewing DR Site information - Storage tab

Refreshing DR informationA Refresh option is also available at the SCVMM Server name level for the Disaster Restart button. When selected, it refreshes information for all groups and virtual machines on all DR sites managed by the SCVMM Server.

This section provides the supported VSI Powershell Commands (cmdlets) that can be used to retrieve storage details for hosts and virtual machines that are managed by the SCVMM server.

◆ Supported VSI Powershell commands ........................................... 78

VSI PowershellCommands

VSI Powershell Commands 77

VSI Powershell Commands

Supported VSI Powershell commandsVSI Powershell commands (cmdlets) can be used to retrieve storage details for hosts and virtual machines that are managed by the SCVMM Server. Commands are launched from a PowerShell command prompt. This functionality is only supported on the hosts containing the VSI client.

The cmdlets binary is a PowerShell snap-in named VSI_PSSnapIn.dll.

Instructions for running VSI Powershell cmdletsThis section describes two different methods of how to open a Powershell command prompt, connect to a SCVMM Server, and load the VSI PowerShell snap-in.

Method 1: 1. Select Start > Run, and type PowerShell.

2. Type the following in the PowerShell command prompt:

Add-PSSnapIn -Name Microsoft.SystemCenter.VirtualMachineManager

3. Type the following cmdlet to connect to a SCVMM server:

Get-VMMServer

4. Enter the SCVMM server name to connect to.

5. Type the following cmdlet to load the VSI PowerShell snap-in:

Add-PSSnapIn VSI_PSSnapIn

Method 2: 1. Open the SCVMM console and connect to a SCVMM server.

2. Open a PowerShell command prompt from the SCVMM console. This PowerShell command prompt already has a connection to the SCVMM server.

3. Type the following cmdlet in the PowerShell command prompt to load the VSI PowerShell snap-in:

Add-PSSnapIn VSI_PSSnapIn

VSI-supported commands can be run after the VSI snap-in has been loaded. For example, type the following cmdlet from the PowerShell command prompt:

Get-VSI_VMHost

This displays information about all hosts managed by the SCVMM server. Supported cmdlets are described in the following sections.

VM HostsThis section describes cmdlets that retrieve information about VM hosts.

Get-VSI_VMHostThe Get-VSI_VMHost cmdlet displays information about all hosts managed by this SCVMM server.

Get-VSI_VMHost <Host name>The Get-VSI_VMHost <Host name> cmdlet displays information about the specified host managed by this SCVMM server.

Virtual MachinesThis section describes cmdlets that retrieve information about virtual machines.

Get-VSI_VMThe Get-VSI_VM cmdlet displays information about all VMs managed by this SCVMM server.

Get-VSI_VM <VM name>The Get-VSI_VM <VM name> cmdlet displays information about the specified VM managed by this SCVMM server.

Supported VSI Powershell commands 79

StorageThis section describes cmdlets that retrieve information about storage arrays.

Get-VSI_StorageThe Get-VSI_Storage cmdlet displays information about all storage arrays connected to hosts managed by this SCVMM server.

Get-VSI_Storage <Array name>The Get-VSI_Storage <Array name> cmdlet displays information about the specified storage array connected to hosts managed by this SCVMM server.

Library ServerThis section describes cmdlets that retrieve information about library servers.

Get-VSI_LibraryServerThe Get-VSI_LibraryServer cmdlet displays information about all library servers managed by this SCVMM server.

Get-VSI_LibraryServer <Library Server name>The Get-VSI_LibraryServer <Library Server name> cmdlet displays information about the specified library server managed by this SCVMM server.

Storage DiscoverThis section describes cmdlets that perform storage discover operations.

Discover-VSI_StorageThe Discover-VSI_Storage cmdlet performs a storage discover operation.

Disaster Recovery SiteThis section describes cmdlets that retrieve information about disaster recovery sites.

Get-VSI_DRSITEThe Get-VSI_DRSITE cmdlet displays information about all disaster recovery sites managed by this VSI server.

Get-VSI_DRSITE <DR site name>The Get-VSI_DRSITE <DR site name> cmdlet will display information about the specified DR site managed by this VSI server.

MoveThis section describes cmdlets that perform move operations.

Move-VSI_ClusterGroup <Group name> <Cluster name> <Move to node>The Move-VSI_ClusterGroup <Group name> <Cluster name> <Move to node> cmdlet moves a group from the current node to a specified node.

Move-VSI_ClusterGroup <Group name> <Cluster name>The Move-VSI_ClusterGroup <Group name> <Cluster name> cmdlet moves a group from the current node to a different node in the cluster.

Live MigrateThis section describes cmdlets that perform live migration operations.

LiveMigrate-VSI_ClusterGroup <Group name> <Cluster name> <Move to node>The LiveMigrate-VSI_ClusterGroup <Group name> <Cluster name> <Move to node> cmdlet performs a live migration of a virtual machine in a group from the current node to a specified node. Note that Failover Cluster target node only supports the live migration of one virtual machine at a time. If a group contains more than one virtual machine, VSI aborts the requested operation.

Supported VSI Powershell commands 81

LiveMigrate-VSI_ClusterGroup <Group name> <Cluster name>The LiveMigrate-VSI_ClusterGroup <Group name> <Cluster name> cmdlet performs a live migration of a virtual machine in a group from the current node to a different node in the cluster.

Quick MigrateThis section describes cmdlets that perform quick migration operations.

QuickMigrate-VSI_ClusterGroup <Group name> <Cluster name> <Move to node>The QuickMigrate-VSI_ClusterGroup <Group name> <Cluster name> <Move to node> cmdlet performs a quick migration of virtual machines in a group from the current node to a specified node.

QuickMigrate-VSI_ClusterGroup <Group name> <Cluster name>The QuickMigrate-VSI_ClusterGroup <Group name> <Cluster name> cmdlet performs a quick migration of virtual machines in a group from the current node to a different node in the cluster.

EMC Virtual Storage Integrator for Hyper-V Version 1.0 ... · EMC Corporation Corporate...

Documents

EMC VSPEX Blue Hyper-Converged Infrastructure Platform … · Title: EMC VSPEX Blue Hyper-Converged Infrastructure Platform Author: EMC Subject: The EMC VSPEX Blue Hyper-Converged

EMC Avamar Virtual Edition for Hyper-V Installation Guide · Overview of Avamar Virtual Edition for Hyper-V ... l Avamar Product Security Guide ... EMC Avamar Virtual Edition 7.3

Dell EMC XC Series Hyper-Converged Appliances Data ... EMC Reference Architecture Dell EMC XC Series Hyper-Converged Appliances Data Protection Reference Architecture Abstract Describes

VxRail Hyper-converged Appliances from Dell EMC · Lab Validation:VxRail Hyper-converged Appliances from Dell EMC 2 © 2017 by The Enterprise Strategy Group, Inc. All Rights Reserved

Dell EMC XC640 Series Hyper-Converged Appliance …topics-cdn.dell.com/pdf/dell-xc640-ent_users-guide_en-us.pdf · Rev. A01. Contents 1 About Dell EMC ... The Dell EMC XC640 Hyper-Converged

Dell EMC XC6420 Series Hyper-Converged Appliance Solutions ...topics-cdn.dell.com/pdf/dell-xc6420_reference-guide_en-us.pdf · The Dell EMC XC6420 Series Hyper-Converged Appliances

Dell EMC Virtual Storage Integrator (VSI) for VMware ......Dell EMC Virtual Storage Integrator (VSI) for VMware vSphere Client Version 8.2 Product Guide P/N 302-006-063 REV 01 September

Pivotal Cloud Foundry on Dell EMC XC Series Hyper ... · A Dell EMC Reference Architecture Pivotal Cloud Foundry on Dell EMC XC Series Hyper-Converged Appliances - Reference Architecture

User Guide: EMC Storage Integrator PowerShell Toolkit

Dell EMC XC Series Hyper-Converged Appliances for Citrix ... · A Dell EMC Reference Architecture Dell EMC XC Series Hyper-Converged Appliances for Citrix XenDesktop – Reference

Dell EMC Hyper-Converged Infrastructure Customer Presentation€¦ · Dell EMC Hyper-Converged Infrastructure New normal for the modern data center. 2 Expensive tech refreshes, risky

Dell EMC XC630 Series Hyper-Converged Appliance Support …...13 Dell EMC XC630 Series Hyper-Converged Appliance Support Matrix | A22 Expansion Bus Specification Riser 3 (Slot 2) One

EMC VSPEX SERVER VIRTUALIZATION WITH MICROSOFT HYPER-V

EMC STORAGE WITH MICROSOFT HYPER-V VIRTUALIZATION - Dell EMC · PDF fileEMC STORAGE WITH MICROSOFT HYPER-V ... With Windows Server 2012, you can ... EMC Storage with Microsoft Hyper-V

Production Pivotal Cloud Foundry on Dell EMC XC Series Hyper … · A Dell EMC Reference Architecture Production Pivotal Cloud Foundry on Dell EMC XC Series Hyper-Converged Appliances

Implementing EMC VPLEX and Microsoft Hyper-V and SQL Server

Dell EMC Enterprise Storage Integrator for SAP Landscape … · 2020-06-10 · Dell EMC Enterprise Storage Integrator for SAP Landscape Management Simplify and Accelerate System Clone,

Microsoft Hyper-V 2016 with Dell EMC XtremIO X2 White Paper

Dell EMC Hyper-Converged Infrastructure...GLOBAL SPONSORS Dell EMC Hyper-Converged Infrastructure New normal for the modern data center Harry Meier

Dell EMC Unity Storage with Microsoft Hyper-V · PDF file2 Dell EMC Unity Storage with Microsoft Hyper-V ... complexity, expandability, ... Evaluate the solution in a test environment