EMC MirrorView/Cluster Enabler

Version 3.1

Release Notes
P/N 300-007-911 Rev A02 January 22, 2009

These release notes contain supplemental information about EMC MirrorView/Cluster Enabler for Microsoft Failover Clusters V3.1. Topics include:

Product description.............................................................................. 2 New features and changes .................................................................. 3 Fixed problems ..................................................................................... 4 Environment and system requirements ............................................ 5 Known problems and limitations ...................................................... 8 Technical notes .................................................................................... 15 Documentation ................................................................................... 19 Software media, organization, and files.......................................... 20 Installation ........................................................................................... 21 Troubleshooting and getting help .................................................... 25

Product description

Product description
MirrorView/Cluster Enabler for Microsoft Failover Clusters (MirrorView/CE) is a software extension of failover clusters functionality. MirrorView/CE allows Windows Server 2003 and 2008 Enterprise and Datacenter editions running Microsoft failover clusters (formerly called server clusters using Microsoft Cluster Server or MSCS) to operate across multiple MirrorView-connected CLARiiON arrays in geographically distributed clusters. MirrorView/CE supports both MirrorView/Synchronous and MirrorView/Asynchronous replication software. Once configured using the EMC Cluster Enabler (CE) Manager (graphical user interface or GUI), Microsoft failover clusters are referred to as CE clusters. MirrorView/CE supports quorum model types Majority Node Set (MNS), and MNS with File Share Witness on Windows Server 2003, or Node Majority, and Node and File Share Majority on Windows Server 2008. Using a MirrorView link, Cluster Enabler expands the range of cluster storage and management capabilities while ensuring full business continuance protection. An iSCSI or Fibre Channel connection from each cluster node is made to its own CLARiiON array. Two CLARiiON arrays are connected through MirrorView links to provide automatic failover of mirrored volumes during a Microsoft failover cluster node failover. This connection effectively extends the distance between cluster nodes to form a geographically distributed cluster (stretch cluster) with disaster-tolerant capabilities.1 Cluster Enabler protects data from the following types of failures, 24 hours a day, 7 days a week, and 365 days per year:

Storage failures System failures Site failures

1. The EMC Network Topology Guide provides additional information regarding distance restrictions for your specific configuration.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

New features and changes

New features and changes

The following list provides an overview of the MirrorView/CE new features and enhancements for V3.1:

Support for CLARiiON AX4-5 and FLARE release 2.23 MirrorView/Asynchronous Microsoft Hyper-V

For information on previous MirrorView/CE versions and features, refer to the corresponding release notes located on the Powerlink website at:
http://Powerlink.EMC.com

CLARiiON AX4-5
MirrorView/CE V3.1 supports the CLARiiON AX4-5 series storage array running FLARE software release 2.23.

MirrorView/Asynchronous
MirrorView/CE V3.1 supports MirrorView/Asynchronous (MirrorView/A) replication software and consistency groups. MirrorView/A lets you periodically update a remote copy of production data by keeping a point-in-time copy of a logical unit number (LUN) that replicates the copy to a separate location in order to provide disaster recovery. Existing MirrorView/A consistency groups can be converted to CE groups.

Microsoft Hyper-V
Mirrorview/CE version 3.1 supports Windows Server 2008 (x64) Hyper-V server virtualization for CLARiiON arrays. Once configured as a CE group using the CE Configuration wizard, groups with Hyper-V resources display as regular device groups. MirrorView/CE support for Hyper-V includes configurations employing either Host or Guest Clustering. Hyper-V support on page 15 provides more information.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Fixed problems

Fixed problems
There are no reported fixed problems for MirrorView/Cluster Enabler for Microsoft Failover Clusters V3.1. For information on previous Cluster Enabler fixed problems, refer to the corresponding release notes located on the Powerlink website at:
http://Powerlink.EMC.com

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Environment and system requirements

Environment and system requirements

This section lists the hardware, software, and FLARE requirements for a MirrorView/CE cluster.

Hardware requirements
You need the following hardware to create a geographically distributed MSCS cluster using MirrorView/CE software. CLARiiON arrays The following hardware requirements are required for CLARiiON arrays:

Two supported CLARiiON CX3 storage arrays running FLARE version 3.26, or two supported CLARiiON CX4 storage arrays running FLARE version 4.28, or two supported CLARiiON AX4 storage arrays running FLARE version 2.23 as documented in the E-Lab Interoperability Navigator at:
http://elabnavigator.EMC.com

A minimum of two HBAs are required for connectivity to the CLARiiON array with PowerPath software. For clustering reliability, you must have at least two paths per device. MirrorView/CE supports both iSCSI and Fibre channel SAN connectivity, as well as MirrorView connections over Fibre channel and MirrorView connections over iSCSI.

Servers

Two or more x64 or x86 servers with separate external iSCSI or Fibre Channel buses. All servers in a cluster must be of the same processor architecture. MirrorView/CE requires all disks have signatures. You can assign disk signatures using Windows device management initialization or other third-party tools. MS failover clusters (or MSCS) compatible network configuration, as recommended by Microsoft.

Disks

Network

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Environment and system requirements

Mandates

EMC mandates that all hardware configurations (servers, adapter cards, cluster system, and so forth) be supported in the MirrorView/CE cluster environment, as documented in the E-Lab Interoperability Navigator at:
http://elabnavigator.EMC.com

Software requirements
To install and configure MirrorView/CE, the following Microsoft software and EMC software must be installed on all nodes that compose the MirrorView/CE cluster. Microsoft software The software requirements for Microsoft products are:

Windows Server 2003 Enterprise or Datacenter Editions with SP2 and Microsoft.NET Framework version 2.0. Windows Server 2008 Enterprise or Datacenter Editions requires that all nodes first be installed with the Failover Cluster feature. Microsoft Internet Explorer 6.0 and later (only required for online help). Currently, the latest release is 7.0 available at:
http://www.microsoft.com/windows/ie/default.mspx

Microsoft Cluster Server (MSCS) for Windows Server 2003 SP2 or Windows Server 2003 R2. Be aware of known problems dealing with adding new devices in a clustered environment. Microsoft Knowledge Base article 834911 The Volume label is blank after you mount a volume in Windows Server 2003 at:
http://support.microsoft.com/kb/q834911

Be aware that volume mount points that you have configured on shared disks in a server cluster may intermittently become unavailable. Microsoft Knowledge Base article 898790 provides details:
http://support.microsoft.com/kb/898790

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Environment and system requirements

EMC software

The software requirements for EMC software are as follows:

A minimum version of Solutions Enabler version 6.5.2 is required to be installed prior to installing MirrorView/CE V3.1. PowerPath is required to be installed for multi-path I/O management. The Engineering Support Matrix for your CLARiiON array model provides supported version information.

HBA driver firmware and software MirrorView/CE supports the STORport driver for both Emulex and QLogic.

Installation and operating requirements

A domain based user ID with effective local administrator rights on each node of the cluster can install, configure and manage MirrorView/CE. MirrorView/CE requires a minimum of 64 MB of disk space, not including runtime logging storage. MirrorView/CE uses a runtime licensing methodology. To license this product, the correct MirrorView/CE runtime license must be entered into the EMC Solutions Enabler License Management Facility using the symlmf command. This process is documented in the EMC Solutions Enabler Installation Guide.

Multiple CE cluster management

The MirrorView/CE Manager lets you manage multiple CE clusters simultaneously, as long as all of the clusters are either Windows Server 2003 or 2008 clusters. To manage the cluster, CE Manager shall run under the domain account. This account shall be part of local administrator group of every node of the cluster it manages.
Note: Mixing both Windows Server 2003 and 2008 clusters in one CE Manager session is not supported.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Known problems and limitations

Known problems and limitations

The following are performance or functionality restrictions and limitations that may apply to your specific storage environment or host platform. Windows Server 2008 Core installation MirrorView/CE does not support the Windows Server 2008 Core installation option. Node and File Share Majority in Windows Server 2008 To change the quorum model to "Node and File Share Majority" in Windows Server 2008, you must first update the FileShare permissions to add the Cluster Name and allow "Change" and "Read" permissions for the file share. Refer to your MS Windows documentation for instructions on changing FileShare permissions. Elevated command prompt in Windows Server 2008 Administrators must run the CE event trace dump utility (CE_EventTraceDump.exe) from an elevated command prompt on Windows Server 2008. CE Configuration Wizard browse feature The browse feature in the CE Configuration Wizard may not reflect an accurate list of clusters. The browse function queries the Active Directory for known clusters. If a cluster has not registered itself properly with the Active Directory, it will not show up in the browse list and you will need to type in the cluster name manually. Conversely, if a cluster has been destroyed without cleaning up the Active Directory, this cluster name will show up in the browse list but cannot be managed. Cluster support for secondary side larger than primary side MirrorView/CE does not support clusters where the secondary side is larger than the primary side. The reason for this is that when the system fails over to the secondary side, it can never fail back since the secondary side cannot resynchronize all of its data back to the primary side. Cluster support MirrorView/CE does not support mixing both Windows Server 2003 and 2008 clusters in one CE Manager session.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Known problems and limitations

Mount points mounted on a local drive are not supported MirrorView/CE does not support mount points mounted on a local drive such as C:\. For example, if a volume made from CLARiiON device 0010 is mounted as C:\mnt, MirrorView/CE does not support the cluster group containing 0010. Delete group when MirrorView link is down If you delete a CE group using the CE Manager when the MirrorView link is down, the CE group will be deleted from Cluster Enabler and the consistency group will be deleted from only the local CLARiiON array. You must then use Navisphere Manager to cleanup the consistency groups on the remote CLARiiON array. MirrorView/S device states displaying incorrectly After moving resources between arrays, the MirrorView device states may not display accurately in the CE Manager GUI. Performing a storage discover operation may correct the problem. If the problem continues, you should verify the correct device state using Navisphere Manager. Cluster group operations and devices Devices can only belong to a single cluster group. When creating or modifying a group using the CE Manager, ensure that you do not add devices that already belong to an existing MirrorView consistency group. Group creation fails and displays the following error message if you choose devices that already belong to an existing MirrorView consistency group:
Failure during CLARiiON Interface Layers attempt to obtain data from CLARiiON array.

Cluster group conversion with consistency groups When MirrorView/CE is installed in an existing MirrorView environment where storage is already clustered and mirrored, the CE Configuration wizard does not currently support the conversion of existing cluster groups with existing consistency groups. The existing consistency groups must first be destroyed before they can be converted to CE groups. When mirrors in existing consistency groups are not resources in a failover cluster, the Create Group wizard can be used to convert existing consistency groups to CE groups.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Known problems and limitations

Using Modify Group Wizard to add device pairs When using the CE Modify Group Wizard to add device pairs, first verify that the device pair is in the synchronized or consistent state using the Navisphere Manager. Add nodes DNS error If the following error message is encountered while using the CE Configuration Wizard to add nodes, you must update your Domain Name Server (DNS) list in Windows:
An error occured when doing Configure Cluster. Exception: Exception has been thrown by the target of an invocation.

Follow these steps to update your DNS list: 1. Click Start > Control Panel > Network and Internet Connections > Network Connections. 2. Right-click the network connection that you want to configure, and then click Properties. 3. On the General tab (for the local area connection), or the Networking tab (for all other connections), click Internet Protocol (TCP/IP), and then click Properties. 4. Click Advanced and then click DNS. 5. Click Append these DNS suffixes (in order), and then click Add to add suffixes to the list. Ensure that your full domain name including the suffix is the first one listed (for example, mydomainname.com). Internet connection and CRL checking If your Windows Server internet connection is disabled, the Microsoft certificate revocation list (CRL) check operation times out and the EMC Cluster Enabler Service will be unavailable. In this case, you need to turn off the CRL checking feature by setting the registry for the Local System account (S-1-5-18) at the following registry location:
[HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentV ersion\WinTrust\Trust Providers\Software Publishing] "State"=dword:00023e00

If the Windows Server internet connection is enabled, you can revert back to the default behavior by setting the following:
[HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentV ersion\WinTrust\Trust Providers\Software Publishing] "State"=dword:00023c00

10

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Known problems and limitations

Create Group Wizard If the group creation process fails before the CE Manager Create Group Wizard completes, the MirrorView consistency group created must be manually cleaned up using the Navisphere Manager. Cluster group error message #999 The following error message may be returned while running the CE Configuration Wizard or Create Group Wizard:
Failed to set storage group definition in cluster properties for group with status [999].

This error is returned because the WMI (Windows Management Instrumentation component) repository did not properly update after the CE resource was created and therefore, it cannot find the CE resource just created. To fix the problem, manually delete the CE resource added by CE from the cluster group in Microsoft Failover Cluster and reboot the cluster nodes. SYMAPI license update CE detects when a new SYMAPI license has been added and will validate the license successfully after re-running the CE Configuration wizard. However, If a SYMAPI license is removed, you must either stop the CE WMI provider by stopping the wmiprvse.exe process or reboot the MirrorView/CE host so that Cluster Enabler can update the license information. Follow these steps to stop the wmiprvse.exe process: 1. Open the Windows Task Manager and click Processes. 2. Locate and select the wmiprvse.exe process with username SYSTEM in the list. 3. Click End Process. Duplicate disk signatures MirrorView/CE requires that all disks have signatures. If the following error is encountered while creating a CE group:
Duplicate disk signatures or GPT GUIDs are found.

You must reboot all CE hosts, perform a storage discover, and try creating the group again. This problem is caused by stale disk signatures present on some hosts and is a known Microsoft Windows issue.
EMC MirrorView/Cluster Enabler Version 3.1 Release Notes
11

Known problems and limitations

Restrict group movement and recovery If a CE group has the "Restrict Group Movement" policy set and the MirrorView link is down, it may take a long time for the resource to come online if the user manually tries to move the group to a node that is connected to a different storage array. For example, if the user tries to move group G1 from the primary side to the secondary side when the MirrorView link is down, then Microsofts preferred owner logic will attempt to bring the group online on the secondary side as expected. But since the restrict group movement policy is set for the CE group, Microsoft will fail the resource on the secondary side nodes. This is correct behavior and is expected, but it may take a long time for the resource to fail on all the secondary nodes before coming back online on one of the primary side nodes. This is because by default Microsoft will try to bring the group online 3 times on each node. The more nodes you have in the cluster the longer it will take for Microsoft to complete the preferred owner logic. To minimize this undesirable effect, you can change the number of retries from 3 to 1 on each node. Follow these instructions to change the Microsoft preferred owner logic from 3 times to 1 time per node: 1. Using the MS Cluster Administrator/Failover Cluster Manager, right-click on the EMC resource in the group. 2. Select Properties and click the Advanced tab. 3. Change the Threshold property from 3 to 1. This will minimize number of retries and reduce the time required to bring the group online.

12

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Known problems and limitations

Consistency group and mirror limitations There is a fixed number of allowable consistency groups per CLARiiON storage array model, and a fixed number of allowable mirrors per consistency group. These limitations must be adhered to when creating or modifying MirrorView/CE groups. Table 1 on page 13 presents the MirrorView/Synchronous consistency group limitations per supported CLARiiON storage array by specific platform model. Table 2 on page 14 presents the MirrorView/Asynchronous consistency group limitations per supported CLARiiON storage array by specific platform model.
Table 1

MirrorView/Synchronous consistency group limitations Mirrors per consistency group 8 8 Consistency groups per storage array 8 8

CLARiiON platform AX4-5 CX3-10c CX3-20c CX3-20f CX3-40c CX3-40f CS3-80 CX4-120 CX4-240 CX4-480 CX4-960

16

16

16

64

32

64

MirrorView/CE displays one of the following error messages if the maximum number of allowed consistency groups per CLARiiON array has been exceeded:
An error (SystemException) occurred when creating storage group [GROUPNAME]. Message: Could not create group : Maximum number of groups allowed on array has been met. An error (SystemException) occurred when creating storage group [GROUPNAME]. Message: Could not create group : Failure during CLARiiON Interface Layer's attempt to obtain data from CLARiiON array

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

13

Known problems and limitations

MirrorView/CE displays the following error message if the maximum number of allowed mirrors per consistency group has been exceeded:
An error (SystemException) occurred when creating storage group [GROUPNAME]. Message: Could not create group : Failure during CLARiiON Interface Layer's attempt to obtain data from CLARiiON array
Table 2

MirrorView/Asynchronous consistency group limitations Mirrors per consistency group 8 8 Consistency groups per storage array 8 8

CLARiiON platform AX4-5 CX3-10c CX3-20c CX3-20f CX3-40c CX3-40f CS3-80 CX4-120 CX4-240 CX4-480 CX4-960

16

16

50

16

50

14

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Technical notes

Technical notes
The following technical notes are presented with this release of MirrorView/CE for Microsoft Failover Clusters V3.1.

Hyper-V support
Mirrorview/CE version 3.1 supports Windows Server 2008 (x64) Hyper-V server virtualization for CLARiiON arrays. Hyper-V is installed and managed as a role under Windows Server 2008 and requires an x64-based processor. MirrorView/CE support for Hyper-V includes configurations employing either Host or Guest Clustering. Host Clustering allows you to host and failover virtual machines by making the physical machine highly available. In this common method of deployment, services and applications can run in multiple individual virtual machines that are highly available. If a virtual machine becomes unavailable, only that single service in the virtual machine will failover (assuming each virtual machine has its own physical disk). Guest Clustering enables highly-available services and applications in a virtual layer. In this method of deployment, failover clustering is installed on several virtual machines and are then clustered as physical nodes. Microsoft Windows Server 2008 failover cluster or Microsoft Windows Server 2003 Microsoft Cluster Server software and MirrorView/CE software are installed and configured on the guest virtual machines. For Guest Clustering, MirrorView/CE only supports direct iSCSI disks. This means that the guest virtual machines must be running the Microsoft iSCSI software initiator on each guest operating system, which is connected to the CLARiiON storage array via iSCSI. Each virtual machine must be registered to the CLARiiON storage subsystem to be configured as cluster nodes in the Failover cluster wizard. The EMC Cluster Enabler Manager displays the virtual machines as cluster nodes. In this configuration, the virtual machines on the Hyper-V server act as cluster nodes, thus the failover/failback process is similar to that of a regular Windows server.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

15

Technical notes

Hyper-V configuration notes

Once configured using the CE Configuration wizard, groups with Hyper-V resources display as regular device groups. The following listed Microsoft documentation should be consulted for Hyper-V configuration instructions:

The Hyper-V Getting Started Guide is available at:

http://technet.microsoft.com/en-us/library/cc732470.a spx

The Virtualization with Hyper-V: FAQ is available at:

http://www.microsoft.com/windowsserver2008/en/us/hype rv-faq.aspx

The following steps are provided as a guide for getting started with Hyper-V and MirrorView/CE v3.1: 1. Follow the instructions provided in Microsofts Hyper-V Getting Started Guide to install Hyper-V using the Server Manager. 2. Follow the instructions provided in Microsofts Hyper-V Getting Started Guide to create and setup a virtual machine (guest machine) using the Hyper-V Manager.
Note: If configuring more than one guest machine, ensure that you create only one machine on one physical disk.

3. Install an Operating system on the virtual machine. 4. Install the application that you want to be highly available on the operating system of the virtual machine. 5. Using Microsoft Failover Cluster Manager, configure a failover cluster for the virtual machine resources that you just created. Consult your Microsoft Failover Cluster documentation for instructions.
Note: Turn off the virtual machine before adding it to the cluster.

6. Bring the virtual machines online in Failover Cluster Management. Figure 1 shows an example of the Failover Cluster Management GUI with virtual machines online.

16

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Technical notes

7. Open the CE Manager and configure a CE cluster using the CE Configuration wizard. 8. On the Current Nodes wizard page, add a second Node to the cluster. 9. Once added, follow the steps in the wizard accepting the default settings.

Figure 1

Failover Cluster Management with virtual machines

10. Once the CE cluster is configured, note that the CE resource is part of each virtual machine service group. The physical device where the virtual machine was created is dependent on the CE resource. The CE group with the Hyper-V resource is displayed as a regular device group. Figure 2 shows an example of the CE Manager GUI with a Hyper-V resource configured for host clustering. Figure 3 shows an example of the CE Manager GUI with a Hyper-V resource configured for guest clustering.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

17

Technical notes

Figure 2

CE Manager with virtual machine cluster group (Host Clustering)

Figure 3

CE Manager with virtual machine cluster group (Guest Clustering)

18

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Documentation

Documentation
These release notes provide the latest information not included in the EMC MirrorView/Cluster Enabler Version 3.1 Product Guide. The EMC Cluster Enabler Version 3.1 Product Guide is available on the Powerlink website at:
http://Powerlink.EMC.com

Related documentation

The following documentation from EMC Corporation contains information that may be helpful in an MirrorView/CE clustered environment:
EMC MirrorView

MirrorView/Synchronous command line interface (CLI) Reference MirrorView/Asynchronous command line interface (CLI) Reference MirrorView online help Navisphere Manager help PowerPath product guide

EMC PowerPath

Related third-party documentation

The following Microsoft documentation contains information about or related to the products discussed in this guide:

Microsofts Cluster Server documentation set, especially the Microsoft Cluster Server Administrators Guide, Document No. X0327902 Step-by-Step Guide to Installing Cluster Service, Microsoft Technical Library

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

19

Software media, organization, and files

Software media, organization, and files

The EMC MirrorView/Cluster Enabler for Microsoft Failover Clusters V3.1 kit consists of this document and the following:

EMC MirrorView/Cluster Enabler for Microsoft Failover Clusters Version 3.1 software EMC MirrorView/Cluster Enabler Version 3.1 Product Guide EMC MirrorView/Cluster Enabler for Microsoft Failover Clusters Version 3.1 License Key Card

Note: Software and documentation are downloadable from the Powerlink website at http://Powerlink.EMC.com.

20

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Installation

Installation
Complete installation instructions for the supported Microsoft Windows Server 2003 or 2008 systems are provided in Chapter 3 of the EMC MirrorView/Cluster Enabler Version 3.1 Product Guide. In most cases, installation should be performed using the InstallShield Wizard. In certain upgrade scenarios, where scripting is employed for complex configurations, the installation may be performed using a command line interface method. This method of installation is described in Appendix A of the product guide and should only be performed by system administrators or advanced users of this product. The CE InstallShield Wizard provides a user-friendly alternative to the more difficult manual installation and configuration. It is recommended that you contact EMC Customer Support for assistance if any of the following issues are applicable:

You have applications already layered with dependencies. You need other devices online. You are not confident about installing and configuring new software within the context of Windows Server 2003 or 2008, Microsoft Failover Clusters, and CLARiiON with MirrorView.

Before you begin

Before installing MirrorView/CE using the CE InstallShield Wizard, read through all of the installation procedures and related information found in the product guide to get an overall understanding of the installation process. The configuration guidelines provide references for properly installing hardware and software in a MirrorView/CE cluster environment.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

21

Installation

Installation requirements and considerations

You should consider the following criteria before installation:

There are two Windows processor architectures that are supported: x86 x64 (AMD64 and Intel EM64T)
Note: Microsoft does not support mixed architecture clusters. All nodes must be the same Windows architecture.

Installation of Cluster Enabler requires a reboot of the system for the configuration to take effect. After installation, you may choose the restart option or postpone your restart until a more convenient time. Installation on Windows Server 2003 systems requires that a minimum of SP2 (Service Pack) first be installed. Installation on Windows Server 2003 requires that Microsoft.NET Framework version 2.0 first be installed. Installation of MirrorView/CE requires that all nodes first be installed with the Failover Cluster feature. MirrorView/CE V3.1 requires that a minimum version of Solutions Enabler V6.5.2 first be installed. Configurations where the cluster node is zoned to both local and remote CLARiiON arrays are not supported.

InstallShield Wizard
The Cluster Enabler InstallShield Wizard is launched by double-clicking on the setup.exe file icon, which is included on your software CD or download. The InstallShield Wizard automatically detects all previous versions of Cluster Enabler and proceeds with the installation upgrade according to the detected version number and installation location.

22

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Installation

Upgrade types
If a previous supported version is detected, a dialog box in the InstallShield Wizard will ask you to select the type of upgrade to perform. Upgrade this node and prepare cluster This option should be used on only one node in the cluster. The install detects the checkpoint file (reglist.txt) and warns the user if it is not present. The checkpoint file is then moved to the new installation directory. The CE cluster resources and resource type are deleted from the cluster. The previous version is uninstalled and Cluster Enabler V3.1 is installed. Upgrade this node This option will uninstall the previous version and install CE 3.1. Clean install Note that the clean install option is useful if a previous version uninstall did not completely clean up the system. Installing CE 3.1 along side an earlier version is not supported. The older version must be uninstalled first.

Clean install
These installation instructions assume that you do not have a previous version of the Cluster Enabler installed on any of the nodes. Before installing be sure to review the requirements and considerations listed above. Follow these instructions to install the MirrorView/CE V3.1 software: 1. Open the installation CD or download the kit from Powerlink and extract the files to a temporary directory. 2. Navigate to your operating system's directory (either x64 or x86) and run the setup.exe file to launch the executable. This will open the first page of the InstallShield Wizard. Click Next. 3. Read the license agreement and select the I accept the terms in the license agreement check box. Click Next. If you do not accept, the software will not be installed and you will be prompted to close the wizard.

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

23

Installation

4. Choose a destination folder location for where to install the program files. It is recommended that you choose the default location as shown. Click Next. 5. Click Install to proceed with the installation. 6. The Windows security message appears, Would you like to install this device software? Click Install. 7. The wizard is now ready to begin installing the files. Click Install. 8. Your system must be restarted for the configuration changes to take effect. Click Yes to restart the system immediately or No to manually restart the system at a later time of your choosing.

24

EMC MirrorView/Cluster Enabler Version 3.1 Release Notes

Troubleshooting and getting help

Troubleshooting and getting 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 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.

Copyright 2009 EMC Corporation. All rights reserved. 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 Technical Documentation and Advisories section 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 MirrorView/Cluster Enabler Version 3.1 Release Notes
25