emc vnx 5200

Here is Your Customized Document

Your Configuration is:

Manage LUNs

Model - VNX5200Storage Type - VNX for Block (SAN)Connection Type - Fibre Channel DirectServer Operating System - Windows Server 2008Path Management Software - PowerPathDocument ID - 1386864476235

Reporting Problems

To send comments or report errors regarding this document,please email: [email protected] Issues not related to this document, contact your service provider.Refer to Document ID:1386864476235Content Creation Date December 12, 2013

This guide describes how to manage LUNS within Unisphere™ for EMC® VNX™ platforms.

Topics include:

Starting Unisphere..................................................................................................................................................3Configuring cache with Unisphere.......................................................................................................................5Enabling storage groups with Unisphere............................................................................................................6Verifying that each LUN is fully initialized using Unisphere..........................................................................7Allocating storage on a new system with the Unisphere LUN Provisioning Wizard..................................9Create pool LUNs..................................................................................................................................................11Create classic LUNs...............................................................................................................................................13Create a LUNs folder............................................................................................................................................15Add LUNs to folders.............................................................................................................................................16Remove LUNs from a folder................................................................................................................................17Set LUN properties................................................................................................................................................18Set classic LUN write cache or FAST Cache properties...................................................................................19Auto assign for a LUN..........................................................................................................................................20Default owner of a LUN.......................................................................................................................................21Source LUN............................................................................................................................................................22Destination LUN definition.................................................................................................................................23Verify priority for a LUN......................................................................................................................................24Rebuild priority for a LUN..................................................................................................................................25Start the Storage Expansion wizard....................................................................................................................26LUN migration overview.....................................................................................................................................28Start a LUN migration..........................................................................................................................................29Cancel (stop) a LUN migration...........................................................................................................................30Display the status of active LUN migrations....................................................................................................31Creating storage groups with Unisphere...........................................................................................................32Making LUNs visible to a Windows server or Windows virtual machine with NICs................................33Verifying that PowerPath for Windows servers or Windows virtual machines sees all paths to theLUNs.......................................................................................................................................................................34

EMC®

Managing LUNs on your VNX5200

Starting Unisphere

1. Log in to a host (which can be a server) that is connected through a network to the system’smanagement ports and that has an Internet browser: Microsoft Internet Explorer,Netscape, or Mozilla.

2. Start the browser.

3. In the browser window, enter the IP address of one of the following that is in the samedomain as the systems that you want to manage:

◆ A system SP with the most recent version of the VNX Operating Environment (OE)installed

Note: This SP can be in one of the systems that you want to manage.

◆ A Unisphere management station with the most recent Unisphere Server and UIsinstalled

Note: If you do not have a supported version of the JRE installed, you will be directed to the Sunwebsite where you can select a supported version to download. For information on the supportedJRE versions for your version of Unisphere, refer to Environment and System Requirements in theUnisphere release notes on the EMC Online Support website.

4. Enter your user name and password.

5. Select Use LDAP if you are using an LDAP-based directory server to authenticate usercredentials.

If you select the Use LDAP option, do not include the domain name.

When you select the LDAP option, the username / password entries are mapped to anexternal LDAP or Active Directory server for authentication. Username / password pairswhose roles are not mapped to the external directory will be denied access. If the usercredentials are valid, Unisphere stores them as the default credentials.

6. Select Options to specify the scope of the systems to be managed.

Global (default) indicates that all systems in the domain and any remote domains can bemanaged. Local indicates that only the targeted system can be managed.

7. Click Login.

When the user credentials are successfully authenticated, Unisphere stores them as thedefault credentials and the specified system is added to the list of managed systems inthe Local domain.

Starting Unisphere 3

Starting Unisphere

http://support.emc.com

8. If you are prompted to add the system to a domain, add it now.

The first time that you log in to a system, you are prompted to add the system to aUnisphere domain. If the system is the first one, create a domain for it. If you alreadyhave systems in a domain, you can either add the new system to the existing domain orcreate a new domain for it. For details on adding the system to a domain, use theUnisphere help.

4 Managing LUNs on your VNX

Starting Unisphere

Configuring cache with Unisphere

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, right-click the entry for the system for which you want to verifycache properties and select Properties.

3. Enable or configure the cache as described in the Unisphere online help.

Note: The latest version of Unisphere automatically sets the read and write cache sizes. If yoursystem is running an older version of Unisphere, refer to the system's version of the online helpfor advice on setting read/write cache values and setting watermarks.

Configuring cache with Unisphere 5

Configuring cache with Unisphere

Enabling storage groups with Unisphere

You must enable storage groups using Unisphere if only one server is connected to thesystem and you want to connect additional servers to the system.

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, right-click the icon for the system, and click Properties.

3. Click the General tab, and select Storage Groups.

4. Click OK.


Enabling storage groups with Unisphere

Verifying that each LUN is fully initialized using Unisphere

Although the storage group with a new LUN is assigned to the server, the server cannot seethe new LUN until it is fully initialized (completely bound). The time the initializationprocess takes to complete varies with the size of the LUN and other parameters. While aLUN is initializing, it is in a transitioning state, and when the initialization is complete, itsstate becomes ready.

To determine the state of a LUN:

1. From Unisphere, navigate to the LUN you want to verify (Storage ➤ LUNs).

2. Right-click the LUN and click Properties.

3. Verify that the state of the LUN is Normal.

If the state is Transitioning, wait for the state to change to Ready before continuing.

Verifying that each LUN is fully initialized using Unisphere 7

Verifying that each LUN is fully initialized using Unisphere

MetaLUNs overview

MetaLUNS are available for classic LUNs only.

Important: EMC strongly recommends that you do not expand LUN capacity by concatenating LUNsof different RAID types. Do this only in an emergency situation when you need to add capacity to aLUN and you do not have LUNs of the same RAID type or the disk capacity to create new ones.Concatenating metaLUN components with a variety of RAID types could impact the performance ofthe resulting metaLUN. Once you expand a LUN, you cannot change the RAID type of any of itscomponents without destroying the metaLUN. Destroying a metaLUN destroys all LUNs in themetaLUN, and therefore causes data to be lost.

A metaLUN is a type of LUN whose maximum capacity can be the combined capacities ofall the LUNs that compose it. ThemetaLUN feature lets you dynamically expand the capacityof a single LUN (base LUN) into a larger unit called a metaLUN. Do this by adding LUNsto the base LUN. You can also add LUNs to a metaLUN to further increase its capacity. Likea LUN, a metaLUN can belong to a Storage Group, and can participate in SnapView,MirrorView, and SAN Copy sessions.

Note: Thin LUNs cannot be part of a metaLUN.

AmetaLUNmay includemultiple sets of LUNs and each set of LUNs is called a component.The LUNs within a component are striped together and are independent of other LUNs inthe metaLUN. Any data that is written to a metaLUN component is striped across all theLUNs in the component. The first component of any metaLUN always includes the baseLUN.

You can expand a LUN or metaLUN in two ways — stripe expansion or concatenateexpansion:

◆ A stripe expansion takes the existing data on the LUN or metaLUN you are expanding,and restripes (redistributes) it across the existing LUNs and the new LUNs you areadding. The stripe expansion may take a long time to complete.

◆ A concatenate expansion creates a new metaLUN component that includes the newexpansion LUNs, and appends this component to the existing LUN or metaLUN as asingle, separate, striped component. No restriping of data between the original storageand the new LUNs occurs. The concatenate operation completes immediately.

During the expansion process, the host is able to process I/O to the LUN or metaLUN, andaccess any existing data. It does not, however, have access to any added capacity until theexpansion is complete. Whether you can actually use the increased user capacity of themetaLUNdepends on the operating system running on the servers connected to the storagesystem.


MetaLUNs overview

Allocating storage on a new system with the Unisphere LUNProvisioning Wizard

Important:

If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server.

1. Select the system for which you want to allocate storage.

2. Select Storage ➤ LUNS ➤ LUNS.

3. Under the Wizards list, select the LUN Provisioning Wizard.

4. On the Select Servers page, select Assign LUNs to the Servers, and select the servers thatwill have access to the new LUNs.

5. Select the system in which the new LUNs will reside.

6. Create a LUN:

a. Select a pool or RAID group in which to create a LUN, or create a new pool for theLUN.

We recommend you use an existing pool or create a pool instead of a RAID groupbecause a pool supports options, such as Fully Automated Storage Tiering (FAST)and Thin Provisioning, which a RAID group does not support.

b. If you are creating a pool LUN and you want the LUN to be a thin LUN, select ThinLUN.

The Thin LUN option is available and will be selected by default if the ThinProvisioning enabler is installed. To learn about pools and thin LUNs, click the ? iconnext to Thin LUN.

c. Select the properties for the LUN.

d. Add the LUNs to a user-defined folder or do not place them in a folder.

e. Click Finish to create the LUN.

7. Verify that the serverwas assigned to the storage group containing the LUNs you created:

◆ If you know the name of the storage group inwhich the LUNs reside, fromUnisphere,select Storage ➤ Storage Pools.

◆ If you know the name of the server to which the storage group is assigned, fromUnisphere, select Storage ➤ LUNs and confirm that the new LUNs are listed.

Allocating storage on a new system with the Unisphere LUN Provisioning Wizard 9

Allocating storage on a new system with the Unisphere LUN ProvisioningWizard

If you do not see any of the LUNs you just created, youmay not have selected the AssignLUNs to a server option in the Select Servers page of the LUN Provisioning wizard. Youcan use the Storage Assignment Wizard for Block to assign the LUNs to a server.

8. Create a hot spare policy (a RAID group with a hot spare RAID Type) as described inthe Unisphere online help. To do this, select System ➤ Hardware ➤ Hot Spare Policy.

A hot spare is a single disk that serves as a temporary replacement for a failed disk in a6, 5, 3, 1, or 1/0 RAID group. Data from the failed disk is reconstructed automatically onthe hot spare from the parity or mirrored data on the working disks in the LUN, so thedata on the LUN is always accessible.

Note: Only RAID group LUNs can be hot spares.

Note: Vault drives (the first 4 drives) cannot be qualified as hot spares.


Allocating storage on a new system with the Unisphere LUN ProvisioningWizard

Create pool LUNs

Lets you create one or more pool LUNs of a specified size within a storage pool and specifydetails such as LUN name, and the number of LUNs to create.

1. In the systems drop-down list on the menu bar, select a storage system.

2. Select Storage ➤ LUNs ➤ LUNs.

3. In the LUNs view, click Create.

4. In the Create LUN dialog, under Storage Pool Properties:

a. Select Pool.

b. Select a RAID type for the pool in which the LUN will be created.

For Pool LUNs, only RAID 6, RAID 5, and RAID 1/0 are valid. RAID 5 is the defaultRAID type. Ifmixed tiers are available that use different RAID types, this field displaysMixed.

If available, the software populates Storage Pool for new LUN with a list of pools thathave the specified RAID type, or displays the name of the selected pool. The Capacitysection displays information about the selected pool. If there are no pools with thespecified RAID type, click New to create a new one.

5. In LUN Properties, the Thin checkbox is selected by default. If you do not want to createa thin LUN, clear the Thin checkbox.

6. Assign a User Capacity and ID to the LUN you want to create.

7. If you want to create more than one LUN, select a number in Number of LUNs to create.

Note: For multiple LUNs, the software assigns sequential IDs to the LUNs as they are available.For example, if you want to create five LUNs starting with LUN ID 11, the LUN IDs might be 11,12, 15, 17, and 18.

8. In LUN Name, either specify a name or select Automatically assign LUN IDs as LUN Names.

9. Choose one of the following:◆ Click Apply to create the LUN with the default advanced properties, or◆ Click the Advanced tab to assign the properties yourself.

10. Assign optional advanced properties for the LUN:

Create pool LUNs 11

Create pool LUNs

Select a default owner (SP A or SP B) for the new LUN or accept the default value ofAuto.

a.

b. Set the FAST VP tiering policy option.

11. Click Apply to create the LUN, and then click Cancel to close the dialog box.

An icon for the LUN is added to the LUNs view window.


Create pool LUNs

Create classic LUNs

If you need to create one or more LUNs of a specified size within a RAID group and specifydetails such as SP owner, element size, and the number of LUNs to create, you may wantto determine if the RAID Group has enough free space to accommodate the new LUNs.

Note: If no LUNs exist on a storage system connected to a NetWare server, refer to the Release Noticefor the NetWare Unisphere Agent for information on how to create the first LUN.

If you are creating LUNs on a storage system connected to a Solaris server, and no failover softwareis installed, refer to the Storage System Host Utilities for Solaris Administrator’s Guide for information onhow to create the first LUN.

If the LUNs you are creating reside on a storage system connected to a VMware ESX server, and theseLUNs will be used with layered applications such as SnapView, configure the LUNs as raw devicemapping volumes set to physical compatibility mode.

You may receive a message that this ID is already being used by a private classic LUN. If you get thismessage, assign a new ID, keeping in mind that the system assigns high numbers to private LUN IDs.


2. In the LUNs view, click Create.

3. In the General tab, under Storage Pool Properties, select RAID Group.

4. Select a RAID type that you want to assign to the LUN.

5. If there are no RAID groups with the specified RAID type, click New to create a newRAID group.

The software populates Storage Pool for new LUN with a list of RAID Groups with thespecified RAID type, or displays the name of the selected RAID group. The Capacitysection displays information about the selected RAID group.

6. In LUN Properties, assign a user capacity and ID to the LUN you want to create.

If you want to create more than one LUN, select a number in Number of LUNs to create.

Formultiple LUNs, the software assigns sequential IDs to the LUNs as they are available.For example, if you want to create five LUNs, starting with LUN ID 11, the LUN IDsmay be similar to 11, 12, 15, 17, and 18.

7. In LUN Name, either type a name or select theAutomatically assign LUN IDs as LUN Namescheckbox.

8. Choose one of the following:

Create classic LUNs 13

Create classic LUNs

Click Apply to create the LUN with the default advanced properties.◆

◆ Click the Advanced tab to manually assign the properties.

9. Assign advanced properties for a classic LUN.

a. By default, the Use SP Write Cache checkbox is selected to enable write caching forthe classic LUN. Clear the checkbox if you want to disable write caching.

b. If you want to perform an initial background verify to eliminate latent soft mediaerrors on the newly bound LUN, do NOT select the No Initial Verify checkbox (clearedis the default).

c. If you do NOT want to perform the background verify operation, select the No InitialVerify checkbox.

Important: Do not send data to the LUN until the background verify operation is complete.

d. In the Rebuild Priority list, select a rebuild priority of either ASAP, High (default),Medium, or Low.

e. In the Verify Priority list, select a verify priority of either ASAP,High,Medium (default),or Low.

f. Select a default owner (SP A or SP B) for the new LUN.


Create classic LUNs

Create a LUNs folder

Lets you create a new user-defined LUNs folder, which is a folder created by you in orderto organize your LUNs. You can modify user-defined folders.

1. In the systems drop-down list on the menu bar, select a system.

2. Select Storage ➤ LUNs ➤ LUN Folders.

3. Click Create.

4. In Folder Name, enter a name for the new folder.

EMC recommends that the name you select is one that will help you identify the LUNsin the folder. For example, you might use a name of Accounts Payable.

5. Click OK to save the changes and close the dialog box.

Create a LUNs folder 15

Create a LUNs folder

Add LUNs to folders

Lets you add a LUN to one or more folders.

1. In the systems drop-down list on themenu bar, select the system that includes the folders.


3. In the LUNs view, right-click the icon for a LUN, and then click Select Folders.

4. In Available Folders, double-click the folder to which you want to add the LUN.

The folder moves into the Selected Folders list.


The software adds the LUN to the specified folder.


Add LUNs to folders

Remove LUNs from a folder

Lets you remove LUNs from the selected folder.


2. Select Storage ➤ LUNs ➤ LUN Folders.

3. In the Folders view, right-click the folder from which you want to remove LUNs andselect Select LUNs.

4. In the LUNs tab, under Selected LUNs, select one or more LUNs and click Remove.


The software removes the selected LUNs from the folder.

Remove LUNs from a folder 17

Remove LUNs from a folder

Set LUN properties

Note: In this topic, the term LUN refers to both pool LUNs and classic LUNs.

The LUN properties determine the individual characteristics of a LUN. You set LUNproperties when you create the LUN. You can also change some LUN properties after theLUN is created.



3. In the LUNs view, select a LUN and click Properties.

4. Click one of the property tabs to view and change the current properties for the LUN.


Set LUN properties

Set classic LUN write cache or FAST Cache properties

Important: For a classic LUN to use write cache, write cache must be enabled for the system. For aclassic LUN to use the FAST Cache, FAST Cache must be configured on the system and enabled onthe LUN.

1. In the systems drop-down list on the menu bar, select the storage system.


3. Right-click the icon for the classic LUN, and then click Properties.

4. Select the Cache tab.

5. By default, the Use SP Write Cache checkbox is selected to enable write caching for theclassic LUN. Clear the checkbox if you want to disable write caching.

6. Select the FAST Cache checkbox to enable the FAST Cache for the classic LUN, or clearit to disable the FAST Cache for the classic LUN.

You should not enable the FAST Cache for write intent log LUNs and Clone PrivateLUNs. Enabling the FAST Cache for these LUNs is a suboptimal use of the FAST Cacheand may degrade the cache's performance for other LUNs.

Note: If the FAST Cache enabler is not installed, FAST Cache is not displayed.

7. Click Apply to save changes without closing the dialog box, or click OK to save changesand close the dialog box.

Set classic LUN write cache or FAST Cache properties 19

Set classic LUN write cache or FAST Cache properties

Auto assign for a LUN

Important: Enable this LUN property only if the connected host does not use failover software. Theauto assign property is ignored when the storage system's failover mode for an initiator is set to 1.This property will not interfere with PowerPath's control of a LUN.

Auto assign enables or disables (default) auto assign for a LUN. Auto assign controls theownership of the LUN when an SP fails in a storage system with two SPs. You enable ordisable auto assign for a LUN when you bind it. You can also enable or disable it after theLUN is created without affecting the data on it.

With auto assign enabled, if the SP that owns the LUN fails and the server tries to accessthat LUN through the second SP, the second SP assumes ownership of the LUN to enableaccess. The second SP continues to own the LUN until the failed SP is replaced and thestorage system is powered up. Then, ownership of the LUN returns to its default owner. Ifauto assign is disabled in this situation, the second SP does not assume ownership of theLUN, and access to the LUN does not occur.

If you are running failover software on a server connected to the LUNs in a storage system,youmust disable auto assignment for all LUNs that youwant the software to fail over whenan SP fails. In this situation, the failover software, not auto assign, controls ownership ofthe LUN in a storage system with two SPs.

Note: The auto assign property is not available for a Hot Spare LUN.


Auto assign for a LUN

Default owner of a LUN

The default owner is the SP that assumes ownership of the LUN when the storage systemis powered up. If the storage system has two SPs, you can choose to create some LUNs usingone SP as the default owner and the rest using the other SP as the default owner, or you canselect Auto, which tries to divide the LUNs equally between SPs. The primary route to aLUN is the route through the SP that is its default owner, and the secondary route is throughthe other SP.

If you do not specifically select one of the Default Owner values, default LUN owners areassigned according to RAID Group IDs as follows:

Default LUN ownerRAID Group IDs

SP AOdd-numbered

SP BEven-numbered

Note: The default owner property is unavailable for a Hot Spare LUN.

Default owner of a LUN 21

Default owner of a LUN

Source LUN

A classic LUN, metaLUN, or thin LUN from which data is moved. After a LUN migrationcompletes, the source LUN is destroyed (becomes private).

Important: The source LUN cannot be:

◆ a Hot Spare

◆ in the process of being created

◆ in the process of expanding

◆ a private LUN

◆ a component of a metaLUN.


Source LUN

Destination LUN definition

A classic LUN, metaLUN, or thin LUN to which data is moved. After a LUN migrationcompletes, the destination LUN assumes the identity of the source LUN, and the sourceLUN is destroyed. The capacity of the destination LUNmust be equal to or greater than thecapacity of the source LUN. The destination can be a different RAID type than that of thesource LUN.

Important: The destination LUN cannot be:

◆ a Hot Spare

◆ in the process of being created

◆ in the process of expanding

◆ in a Storage Group

◆ a private LUN

◆ a LUN that is participating in a MirrorView, SnapView, or SAN Copy session.

Destination LUN definition 23

Destination LUN definition

Verify priority for a LUN

The verify priority is the relative importance of validating the consistency of redundantinformation in a LUN. The priority dictates the amount of resources the SP devotes tochecking LUN integrity versus performing normal I/O. You set the verify priority for aLUN when you create it, and you can change it after the LUN is bound without affectingthe data on the LUN.

If an event happens, such as when an SP fails and the LUN is taken over by the other SP, abackground verification begins to check the redundant information within the LUN. Validverify priorities are ASAP, High, Medium (default), and Low. The ASAP setting checks andverifies as fast as possible, but may degrade storage-system performance.

Note: When creating a RAID 0, Disk or Hot Spare LUN, the verify priority property is unavailable.


Verify priority for a LUN

Rebuild priority for a LUN

The rebuild priority is the relative importance of reconstructing data on either a hot spareor a new disk that replaces a failed disk in a LUN. It determines the amount of resourcesthe SP devotes to rebuilding instead of to normal I/O activity. Valid rebuild priorities are

Target rebuild rate in GB/hourValue

0 (as quickly as possible)ASAP

12 (default value)High

6Medium

4Low

Rebuild priorities correspond to target rebuild rates in the table above. Actual time to rebuilda LUN is dependent on I/O workload, LUN size and LUN RAID type. Each LUN builds atits own specified rate.

A rebuild operation with an ASAP or High (default) priority restores the LUN faster thanone with Medium or Low priority, but may degrade storage system performance.

You set the rebuild priority for a LUN when you create it, and you can change it after theLUN is bound without affecting the data on the LUN.

Note: The rebuild priority property is unavailable for a RAID 0, Disk, or Hot Spare LUN.

Rebuild priority for a LUN 25

Rebuild priority for a LUN

Start the Storage Expansion wizard

The Storage Expansion wizard is supported for classic LUNs only.

The RAIDGroup LUN ExpansionWizard lets you dynamically expand the capacity of newor existing LUNs by combining multiple LUNs into a single unit called a metaLUN. Youcan add additional LUNs to a metaLUN to increase its capacity even more. The wizardpreserves the expanded LUN's data. You do not have to unbind the LUNyouwant to expandand lose all the data on this LUN. Once you create a metaLUN, it acts like a standard LUN.You can expand it, add it to a Storage Group, view its properties, and destroy it.

For existing metaLUNs, you can expand only the last component of the metaLUN. If youclick a component other than the last one and select Add LUNs, the software displays anerror message.

AmetaLUNcan spanmultiple RAIDGroups and, depending on expansion type (concatenateor stripe), the LUNs in a metaLUN can be different sizes and RAID Types.

Note: The software allows only four expansions per storage system to be running at the same time.Any additional requests for expansion are added to a queue, and when one expansion completes, thefirst one in the queue begins.

1. In the systems drop-down list on the menu bar, select a storage system.

2. From the task list, under Wizards, select RAID Group LUN Expansion Wizard.

3. Follow the steps in the wizard, and when available, click the Learn more links foradditional information.


Start the Storage Expansion wizard

Delete LUNs

Important: Deleting a LUN (classic LUN or pool LUN) will delete all data stored on the LUN. If theLUN is part of a StorageGroup, youmust remove the LUN from the StorageGroup before you unbindit. Before unbinding a LUN, make a backup copy of any data on it that you want to retain.

Typically, you delete a LUN only if you want to:

◆ Delete a storage pool (RAID group or pool) on a storage system. You cannot delete astorage pool that includes LUNs.

◆ Add disks to it. If the LUN is the only LUN in a storage pool, you can add disks to it byexpanding the storage pool.

◆ Use its disks in a different storage pool.◆ Recreate it with a different capacity of disks.

In any of these situations, you should make sure that the LUN contains the disks that youwant.

1. To determine which disks make up a LUN, do the following:

a. In the systems drop-down list on the menu bar, select a system.

b. Select Storage ➤ LUNs ➤ LUNs.

c. Open the LUN Properties dialog box by double-clicking the LUN icon, or by selectingthe LUN and clicking the Properties button.

d. Select Disks to view a list of disks.

2. To delete a LUN, do the following:

a. In the systems drop-down list on the menu bar, select a system.

b. Select Storage ➤ LUNs ➤ LUNs.

c. Right-click the LUN icon, and select Delete, or select the LUN and click the Delete tab.

d. Click Yes to continue with the operation, or click No to cancel the operation.

Delete LUNs 27

Delete LUNs

LUN migration overview

The LUNmigration feature, included in the Unisphere software and the VNX for Block CLI,lets you move the data in one LUN, thin LUN, or metaLUN to another LUN, thin LUN, ormetaLUN. You might do this to:

◆ Change the type of drive the data is stored on (for example, from more economicalNL-SAS to faster SAS, or vice-versa).

◆ Select a RAID type that better matches the data usage.◆ Recreate a LUN with more disk space.

For example, you may have a metaLUN that has been expanded several times byconcatenation with other LUNs (not by addition of another entire disk unit), and whoseperformance suffers as a result. You can use the migration feature to copy the metaLUNonto a new LUN, which, being a single entity and not a group of several entities, providesbetter performance.

During a LUN migration, the Unisphere software copies the data from the source LUN toa destination LUN. After migration is complete:

◆ The destination LUN assumes the identity (World Wide Name and other IDs) of thesource LUN.

◆ The source LUN consumes the destination LUN's storage, and frees the storage itconsumed in its former storage pool or RAID group.

◆ The destination LUN is removed.

Note: Themigration operation detects the zeros on the source LUN and deallocates them on the targetLUNwhich frees up more storage capacity on the target LUN. For better performance and improveduse of space, make sure that the target LUN is a newly created LUN with no existing data.

Using the Unisphere software, you can start migrations, display and modify migrationproperties, and display a summary of all current migrations on one storage system or allthe systems in the domain. You can also cancel (stop) a migration, which deletes thedestination copy and restores the storage system to its original state.

The number of supported active and queuedmigrations is based on the storage system type.


LUN migration overview

Start a LUN migration

Lets you configure and start the LUN migration operation. Prior to starting the migrationoperation, if the source LUN and the destination LUN belong to different SPs, the softwaretrespasses the destination LUN to the SP that owns the source LUN.

Note: If the destination LUN is a thin LUN, the migration operation detects the zeros on the sourceLUNanddeallocates themon the target LUNwhich frees upmore storage capacity on the target LUN.For better performance and improved use of space, make sure that the target LUN is a newly createdLUN with no existing data.



3. Navigate to the LUN that you want to be the source LUN for the migration operation,and right-click Migrate.

4. In the Start Migration dialog box, select a migration rate, and then select the participatingdestination LUN.

5. Click OK to start the data migration, or click Cancel to close the dialog box.

Start a LUN migration 29

Start a LUN migration

Cancel (stop) a LUN migration

Lets you cancel an active LUNmigration. Canceling a LUNmigration deletes the destinationcopy and restores the storage system to its original state.

1. Select Storage ➤ LUNs ➤ LUNs and navigate to the source LUN that is participating inthe data migration.

2. Click Properties.

3. In the LUN Properties dialog box, select the Migration tab, and click Cancel Migration.

The Unisphere software displays a confirmation dialog box, asking you to confirm thecancel request.

4. Click Yes to cancel LUN migration.


Cancel (stop) a LUN migration

Display the status of active LUN migrations

Shows a summary of all the currently active migrations for a particular storage system, orfor all storage systems within the domain that support the LUN migration feature.

◆ Display status of active migrations for a specific storage system.◆ Display status of active migrations for all supported storage systems in the domain.



3. In the task list, under Block Storage, select LUN Migration Summary.

Display the status of active LUN migrations 31

Display the status of active LUN migrations

Creating storage groups with Unisphere

If you do not have any storage groups created, create them now.


2. Hosts ➤ Storage Groups.

3. Under Storage Groups, select Create.

4. In Storage Group Name, enter a name for the Storage Group to replace the default name.

5. Choose from the following:◆ Click OK to create the new Storage Group and close the dialog box, or◆ Click Apply to create the new Storage Group without closing the dialog box. This

allows you to create additional Storage Groups.

6. Select the storage group you just created and click the Connect hosts.

7. Move the host from Available host to Host to be connected and click OK.


Creating storage groups with Unisphere

Making LUNs visible to a Windows server or Windows virtual machinewith NICs

Important:

If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server.

To allow theWindows server access to the LUNs that you created, use Windows ComputerManagement to perform a rescan:

1. Open the Computer Management window (Start ➤ Computer Management).

2. Under the Storage tree, select Disk Management.

3. From the tool bar menu, select Action ➤ Rescan Disks.

Making LUNs visible to a Windows server or Windows virtual machine with NICs 33

Making LUNs visible to a Windows server or Windows virtual machinewith NICs

Verifying that PowerPath for Windows servers or Windows virtualmachines sees all paths to the LUNs

1. On the server, configure PowerPath:

powermt config

2. On the Windows taskbar, either double-click the PowerPath Administrator icon orright-click the icon and select PowerPath Administrator.

3. In the results pane, verify that the path metric for each LUN is n/nwhere n is the totalnumber of paths to the LUN.


Verifying that PowerPath for Windows servers or Windows virtual machinessees all paths to the LUNs

Copyright © 2006 - 2013 EMC Corporation. All rights reserved.

Published November 2013

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KINDWITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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

For the most up-to-date regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

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

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

Corporate Headquarters: Hopkinton, MA 01748-9103

Managing LUNs on your VNX 35

emc vnx 5200

Documents