MR-1CP-MVSCSP_Lab_Guide_R30_.pdf

8/14/2019 MR-1CP-MVSCSP_Lab_Guide_R30_.pdf

1/51

M irrorView and SAN Copy

Conf iguration and Management

October 2010


2/51

MirrorView and SAN Copy Configuration and Management Lab Guide

Copyright 2010 EMC Corporation. All Rights Reserved. Version 4.30.0 Page 1 of 51

Copyright:

Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 EMC Corporation.All Rights Reserved.

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THISPUBLICATION, 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 softwarelicense.


3/51



Trademark Information:

EMC

Trademarks

EMC , EMC, Symmetrix, Celerra, CLARiiON, CLARalert, Connectrix, Dantz,

Documentum, HighRoad, Legato, Unisphere, PowerPath, ResourcePak,

SnapView/IP, SRDF, TimeFinder, VisualSAN, and where information lives are

registered trademarks and EMC Automated Networked Storage, EMC , EMC

Developers Program, EMC OnCourse, EMC Proven, EMC Snap, Access Logix,

AutoAdvice, Automated Resource Manager, AutoSwap, AVALONidm, C-Clip,

Celerra Replicator, Centera, CentraStar, CLARevent, CopyCross, CopyPoint,

DatabaseXtender, Direct Matrix, Direct Matrix Architecture, EDM, E-Lab,

Enginuity, FarPoint, FLARE, GeoSpan, InfoMover, MirrorView, NetWin, OnAlert,

OpenScale, Powerlink, PowerVolume, RepliCare, SafeLine, SAN Architect, SAN

Copy, SAN Manager,SDMS, SnapSure, SnapView, StorageScope, SupportMate,

SymmAPI, SymmEnabler, Symmetrix DMX, Universal Data Tone, and VisualSRM

are trademarks of EMC Corporation. All other trademarks used herein are the

property of their respective owners.

Third Party

Trademarks

AIX is a registered trademark of International Business Machines Corporation.

Brocade, SilkWorm, SilkWorm Express, and the Brocade logo are trademarks or

registered trademarks of Brocade Communications Systems, Inc., in the United

States and/or in other countries. Compaq and the names of Compaq productsreferenced herein are either trademarks and/or service marks or registered

trademarks and/or service marks of Compaq. Hewlett-Packard, HP, HP-UX,

OpenView, and OmniBack are trademarks, or registered trademarks of Hewlett-

Packard Company. McDATA, the McDATA logo, and ES-2500 are registered

trademarks of McDATA Corporation. Microsoft, Windows, and Windows NT are

either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries. NobleNet is a registered trademark of Rogue Wave

Software, Inc. SANbox is a trademark of QLogic Corporation. Linux, Linux

Microsystems, the Linux Logo, LinuxOS and all Linux-based trademarks and logos,

Java, the Java Coffee Cup Logo, and all Java-based trademarks and logos, Solaris,

and NFS, are trademarks or registered trademarks of Linux Microsystems, Inc. inthe United States and other countries. UNIX is a registered trademark of The Open

Group.


4/51



Document Revision History:

Rev # File Name Date

3.24 MR-1CP-MVSCSP_Lab_Guide_r24.doc January 2007

3.26.0.1 MR-1CP-MVSCSP_Lab_Guide_R26.0.1.doc November 2007

4.28.0 MR-1CP-MVSCSP_Lab_Guide_R28.0.doc September 2008

4.28.5 MR-1CP-MVSCSP_Lab_Guide_R28.5.doc February 2009

4.29.0 MR-1CP-MVSCSP_Lab_Guide_R29.doc October 2009

4.30.0 MR-1CP-MVSCSP_Lab_Guide_R30.doc October 2010


5/51



Table of Contents: MirrorView and SAN Copy Configuration

and Management Labs

Lab Introduction ...................................................................................................................5Lab Exercise 1: Create and Test a Local SAN Copy Session.........................................11

Part 1: Create and Test a Local SAN Copy Session .......................................................12Lab Exercise 2: Create and Test a Remote SAN Copy Session .....................................15

Part 1: Verify SAN Copy Connections .............................................................................16Part 2: Create a Remote SAN Copy Session ..................................................................17

Part 3: Start and Test a Remote SAN Copy Session ......................................................19Lab Exercise 3: Create and Test an Incremental SAN Copy Session ............................21

Part 1: Create an Incremental SAN Copy Session ..........................................................22Part 2: Start and Test an Incremental SAN Copy Session ..............................................24

Lab Exercise 4: Create a Synchronous Remote Mirror ..................................................27Part 1: Allocate the Write Intent Log ................................................................................28Part 2: Manage Mirror Connections .................................................................................29Part 3: Create a Synchronous Remote Mirror .................................................................30

Lab Exercise 5: Promote and Test a Secondary Mirror Image .......................................33Part 1: Promote and Test a Secondary Mirror Image ......................................................34

Lab Exercise 6: Create and Test an Asynchronous Mirror .............................................37

Part 1: Create an Asynchronous Mirror ...........................................................................38Part 2: Test an Asynchronous Mirror ...............................................................................40

Lab Exercise 7: Create and Test a MirrorView/A Consistency Group ...........................45Part 1: Create a MirrorView/A Consistency Group ..........................................................46Part 2: Test a MirrorView/A Consistency Group ..............................................................48


6/51



Lab Introduction

Purpose: To ensure that the environment is configured correctly for MirrorViewand SAN Copy.

Objectives:This lab provides hands-on experience allowing you to verify that:

MirrorView is enabled on the CLARiiON

SAN Copy is enabled on the CLARiiON

MirrorView/A is enabled on the CLARiiON The SAN zoning is correct

The required LUNs and Storage Groups are present on theCLARiiON


7/51



Lab Introduction

The table on the next Page 9 of this introduction, include space for you to note which storage systemsand hosts your group will use, and which your partner group you will use.

EMC Unisphere produces numerous confirmation and informational messageswhen performing

operations. Click Yesor OKas appropriate after reading the messages. These messages are typically

not mentioned in the procedures.

LUNs can be named or renamed during the LUN creation or after they are created (by accessing LUN

Properties), and after they have completed the binding process. You may use the getlun state

command to check the state of all LUNs on the storage system.

Some operations can onlybe accomplished by using the CLI.

The CLARiiON Replication Software(MirrorView/S, MirrorView/A, SnapView, SAN Copy and

Incremental SAN Copy) enhance the functionality of the storage systems and often require the use of

two or more hosts/arrays when using secondary mirror images, snapshots, sessions and Clones. You

may be interactingwith another group also performing these exercises.

Please wait for your partner group, if instructed to do so.

AnEMC Navisphere Secure CLImanual is available on PowerLink. Download it and refer to it if

needed.

CLI commandsare directed to a CLARiiON SP. Use thehoraddressswitch with the resolvableSP nameor the SP IP address, e.g. navisecclih 192.168.10.22 or naviseccliaddress cx1spa

The Secure CLIaccepts thehswitch or theaddressswitch.

CLI commandsare directed to a CLARiiON SP. Use thehoraddressswitch with the resolvable

SP nameor the SP IP address, e.g. navisecclih 192.168.10.22 or naviseccliaddress cx1spa

The Secure CLIaccepts thehswitch or theaddressswitch.

Commands often need to be run in a certain order. You cannot, for example, enable write caching if

no memoryhas been assigned to write cache. Also, you can not make changesto cache parameters

without first disabling the cache. If you forget to disable the cache and receive error messages, click

Cancel, and re-startthe procedure.

If you see error messagesreturned from the CLI or the GUI, read them carefully. The error

messageshelp you determine how to fix the problem.

and refer to the hostnames/IP addresses of SPA and SPB. Hostnames are treated in a

similar way.


8/51



The diagram below shows the genericCLARiiON lab setup.

Each student group is assigned a Windows host and a Linux host, and will manage a CLARiiON

storage system.

Where exercises require that groups work together, the groups will be those using CLARiiONs that

are in the same storage domain.

Win

Win

Lin

Lin

CX

CX

Group 1

Group 2

Group 1/Group 2SAN

CLARiiONDomain


9/51



Group numbers Primary Group number: Secondary Group number:

Classroom

Desktops

Username: Password:

Windows Hosts Username: Password:

Primary Windowshost

Name: IP:

SecondaryWindows host

Name: IP:

Linux Hosts Username: Password:

Primary Linux host Name: IP:

Secondary Linuxhost

Name: IP:

Primary storage

system

SPA Name: SPA IP:

SPB Name: SPB IP:

Secondary

storage system

SPA Name: SPA IP:

SPB Name: SPB IP:


10/51



Step Action

1 Ensure that you have created a security file for useremc. If this step is not completed, the

Navisphere Secure CLI commands will fail.

naviseccliaddusersecurityuser emc

password emcscope 0

2 Point your browser at SPA of your primary storage system. Use the IP address or a knownresolvable host name for SPA. The splash screen appears followed by the Unisphere Login

Screen.

3 Enter emc for the username and emcfor the password, and select globalfor the scope from

the drop-down menu.

Result: The EMC Unisphere storage window appears.

4 Double-click your primary storage system and click the Propertiestab or right-click the

array and select Properties.

5 Click the Softwaretab.

6 Click your primary storage system and select Replicasor optionally, right-click your

primary storage system and click Properties.

7 Click the Softwaretab.

8 The dialog displays a list of the licensed products. Verify that the following entries appear

(note the dash in front of the names):

-SANCopy

-MirrorView/S

-MirrorView/A

If the entries are present, then the CLARiiON Replication Software is ready to be used. If

they are not present, consult the instructor.

9 Click Cancelto close the Propertieswindow.


11/51



Step Action

10 Configure your CLARiiON with the LUNs listed below. If some of the LUNs are not

present, create and rename them now. Verify the LUN attributes below. This lab has users

create additional LUNs and rename LUNs as the lab progresses. Names are given only as aconvenience. If you want to supply their own names you may. Labs require a Source and

Destination LUN( Primary and Secondary ). Also the size of the LUNs used are

configured only because of the time to sync, etc. Feel free to use a larger size LUN if you

want.

RAID

GROUP

LUN ID NAME SIZE OWNER

6 100 to

107

RLP

RG_LUN_100 to

RLP

RG_LUN_107

256 MB SP B

6 108 WIL LUN_108A 128 MB SP B

6 109 WIL LUN 109A 128 MB SP B

5 81 to 84 RG5 LUN 1 GB SP A

5 85 RG5 SC_MV

source LUN_85

1 GB SP A

5 86 RG5 SC_MV

Dest LUN_86

1 GB SP A

11 Verify that your CLARiiON and your partner groups CLARiiON are in the same storageDomain. If they are not, one member of the two teams should make the required domain

changes.

12 Add RG5 SC_MV source LUN_85to your primary Windows Storage Group on yourCLARiiON and ensure your Windows host is connected.

13 Format the LUN and assign drive letter X, populate the LUN with some files.

14 Connect yourpartner groups Windows host to its Storage Group on your CLARiiON. The

host may still be connected to another SG from the previous labs.

Note: We have written the labs so that you complete all of the Windows labs first. Then, if you

choose, you can run through these labs for your Linux hosts as well.

End of Lab Introduction


12/51



Lab Exercise 1: Create and Test a Local SAN Copy

Session

Purpose: Create a local copy of a LUN with SAN Copy, using EMC Unisphere

Objectives: Create a local SAN Copy Session directly from the Source LUN

Verify that the procedure worked correctly


13/51



Lab Exercise 1

Part 1: Create and Test a Local SAN Copy Session

Step Action

1 Click the Replicasmenu, locate SAN Copy Settingsfrom the left window and select SAN

Copy Wizard.

2 Read the Welcomescreen window and select Next.

Select your primary storage system from the list of available systems and select Next.

3 Choose a Session Typeof Full.

4 From the Select Storage Sourceswindow, use the dropdown to view available storagesystems and select your primary storage system from the list.

5 Select RG5 SC_MV source LUN_85from the Select Storage Source for Move

Select Next.

6 From the Select Storage Destinations for Storage Sourceswindow, right-click the source

LUN and click Select Destination Storage.

When the Destination storage window appears, choose your primary storage system, locate

the RG5 SC_MV Dest LUN_86, click Next.

Click OKtwice and confirm the action.

7 From the Session Nameswindow, click the name and select Edit. Call the session SC

session_X_85. Change the Throttle valueto 10.

Click Next.

8 Read the Summaryscreen and select Finish > OK.

9 Browse to the Replicasmenu, select SAN Copy Sessions. Select the Sessiontab and verify

the session exists, is a Full Session and shows a status of Not Started.


14/51



Step Action

10 Right-click the session note the options. Select Start.

11 Wait until the status changes to Completed.

Note The status changes from Not Startedto Activeand ends with Completed.

12 Right-click the Session, and choose Statusor select the Statustab from the bottom of thewindow.

Verify that the copy is 100% complete before continuing.

13 MakeRG5 SC_MV Dest LUN_86 visible to your Windows host by adding it to theappropriate Storage Group, and performing host procedures as required such as host

updates.

Note Install admhostif it is not installed already.Example install software: admhost-Win2K3-32--en_US-2.30.0.0.0-1.exe

Perform the following host procedures as needed:

In Computer Management, right-click Disk Managementand select Rescan Disks.

From your command prompt and issue the following commands:

admhost lun_list

admhost lun_activate

admhost lun_ list

If you do need to reboot your host (though the disk rescanand admhostcommands should

have been sufficient) ensure that your partner group is not performing operations on the host

before you reboot it. Note the drive letter of LUN 86. Note that LUN 85 will also be

activated (become visible) because it was not removed from the Storage Group.

14 View the data on RG5 SC_MV Dest LUN_86, and verify that it is identical to the data on

RG5 SC_MV source LUN_85.

15 Remove RG5 SC_MV Dest LUN_86from the Storage Group after deactivating it with thefollowing command:

admhost lun_deactivateo :

The drive changes to a Physical Drive x.


15/51



Step Action

16 Ensure that RG5 SC_MV source LUN_85has the same drive letter as before - change theletter to X: if required.

Note If needed, enter Computer Managementon your Windows host. Right-click the whiterectangular part of the drive and select Change drive letter and paths.

Assign the drive letter X:.

21 Verify that the data on RG5 SC_MV source LUN_85is unchanged.

22 Right-click SC session_X_85 and choose Remove.

End of Lab Introduction


16/51



Lab Exercise 2: Create and Test a Remote SAN Copy Session

Purpose: Create a remote copy of a LUN with SAN Copy, using EMC Unisphere

Objectives: Configure SAN Copy connections

Create a Remote SAN Copy Session


17/51



Lab Exercise 2

Part 1: Verify SAN Copy Connections

Step Action

1 Browse to the Replicasmenu, select SAN Copy Sessions.

Locate the Configurations and Settingsmenu from the left side window and select

Update SAN Copy Connections.

Click OKas required.

2 Create a Storage Group named SANcopyon your primary CLARiiON.

5 Once created, right-click the SANcopy Storage Group, and select SAN Copy >

Connections.

6 Choose SPBon your partner groups CLARiiON from the SAN Copy System drop-downlist.

7 Check all available Ports. Click Apply.

8 Click Advancedto view the dialog with one of the SPB Ports selected. Verify that all

displayed connections are checked.

9 Repeat for the SPAports on your partner groups CLARiiON. Acknowledge all choices,

and click OKto finish.

10 Click the SANcopy Storage Group, in the Detailswindow select the SAN Copy

Connectionstab ensure that both SPs of your partner groups CLARiiON are listed there.


18/51



Lab Exercise 2

Part 2: Create a Remote SAN Copy Session

Step Action

1 Add RG5 LUN_83and RG5 LUN_84to Storage Group SANcopyon your CLARiiON.

Wait for your partner group to complete this step.

2 Verify RG5 SC_MV source LUN_85is still drive X: with the following command:

Ensure the LUN still has files on it. (open Explorer )

3 Flush RG5 SC_MV source LUN_85with the following command:

5 Deactivate RG5 SC_MV source LUN_85with the following command:

admhost lun_deactiveateo x:

Note If the command fails, check to ensure you dont have drive X: open (highlighted) in

Windows Explorer.

6 Right-click your CLARiiON. Choose SAN Copy > Create Session.

7 The SAN Copy Create Session Wizardlaunches. Read the information on the first page

and then click Next.

8 Choose Fullas the Session Type and then click Next

9 Select your CLARiiON from the Storage Source drop-down list, and choose RG5 SC

Source LUN_85 from the LUNs listed in the lower pane.

10 Right-click the Source LUN in the dialog that appears.

Click Select Destination Storage.


19/51



Step Action

11 The dialog that appears next allows you to choose the destination LUNs. Choose your

partner groups CLARiiON as the Storage Destination, then select RG5 LUN_83and RG5

LUN_84and move them to the right pane.

12 Click OK.

13 Check the Verify Connections checkbox and click Next.

You should see a message confirming that all destination LUNs are accessible.

Click OK.

14 Highlight the Session and clickEdit

.

15 Change the Session Name to RemoteMulti.

Change the Throttle value to 10.

Click OKand then Next.

Result: The Summaryscreen appears.

16 Verify that all the settings are correct and click Finish.

17 Verify that the SAN Copy Session exists under SANCopy Sessions on your array.


20/51



Lab Exercise 2

Part 3: Start and Test a Remote SAN Copy Session

Step Action

1 From the SAN Copy Sessionstab, on your CLARiiON.

2 Right-click Session RemoteMulti, and choose Start.

The session starts and the status changes to Active.

3 You can view the session status at any time by right-clicking the session, and choosing

Status.

4 Once the transfer is complete, make RG5 LUN_83and RG5 LUN_84on your partner

groups CLARiiON visible to your Windows host.

Right-click the Storage Group for your Windows host that is located on your partner groups

CLARiiON and select Select LUNs (remember to choose the option Show LUNs All

because RG5 LUN_83and RG5 LUN_84are in a SANCopy Storage Group.) Add RG5

LUN_83and RG5 LUN_84to your Windows hosts Storage Group on your partner groups

CLARiiON.

5 Verify that the files on the destination LUNs RG5 LUN_83and RG5 LUN_84are identical

to those on the Source LUN RG5 SC_MV source LUN_85. You must bring the LUNs

online before you can verify what they contain. On your Windows host execute the

following commands:


admhost lun_list

Note If the LUNs were not brought online, it may be necessary to reboot your Windows host.

7 Open Windows Explorer and verify that the data on both of the SAN Copy Destination

LUNs is identical to the data on the Source LUN.


21/51



Step Action

8 Deactivate the destination LUNs. Issue the following commands:

admhost lun_deactivate o for RG5 LUN_83

admhost lun_deactivate o for RG5 LUN_84

9 Remove RG5 LUN_83and RG5 LUN_84from the Storage Group connected to yourWindows host on your partner groups CLARiiON.

10 Remove RG5 LUN_83and RG5 LUN_84from the SAN CopyStorage Group

11 Remove session RemoteMultiby right-clicking it and choosing Delete.

End of lab exercise


22/51


23/51



Lab Exercise 3

Part 1: Create an Incremental SAN Copy Session

Step Action

1 Verify that RG5 SC_MV source LUN_85is visible to your primary windows host, has a

drive letter X, and contains files on it.

Verify LUNS RLP RG LUN_100 through 107are configured in the Reserved LUN Pool.

If not, configure them now.

Note You may need to Rescan Disks (in Computer Manager) and/or logoff and logon and/or

reboot your Windows host in order to see RG5 SC_MV source LUN_85again.

2 On your partners CLARiiON, add RG5_ SC Dest LUN_86 the SANcopy Storage Group.

3 Right-click RG5 SC_MV source LUN_85on your primary CLARiiON.

Choose SAN Copy > Create Session from LUN.

4 RG5 SC_MV source LUN_85is automatically chosen as the Source LUN.

5 Name the Session RG5 ISC_85

Choose a Session Type of Incremental.

Ensure that Initial Sync Requiredis checked.

Set the Session Throttle to 2.

Set the Link Bandwidth to 2048.

6 Click Select Destination Storage.

Select your partner groups CLARiiON as the Storage Destination. Choose RG5 SC_MV

Dest LUN_86as the Destination LUN.

7 Click YES / OKto create the Session.


24/51



Step Action

8 View the Session in EMC Unisphere by browsing over the Replicasmenu and selecting

SAN Copy Sessions

Click the Sessionstab and view the session Properties.

The Session appears as [Initial Copy Required].

9 Right-click session, and select Status. Click the Marktab. You should see that the Total

Source LU Capacity (blocks) and the Number of Blocks Changed to be copied are the same

because Initial Synchronizationbox is required.

10 From the Replicasmenu, select Reserved LUN Pool.

Expand and highlight the RG5 SC_MV source LUN_85

Verify that a RLP LUN has been allocated to the source LUN.

Note the Session Detailswindow, right-click the Session Nameand view the Properties:

Click the Replicasmenu, select Summary. The summary graphs should display all the

information about the current session.

Click somewhere in the graph for Reserved LUN Pool Usageand note what page launches.

Use the < arrow from the menu bar to return the Summarypage.

End of lab exercise


25/51



Lab Exercise 3

Part 2: Start and Test an Incremental SAN Copy Session

Step Action

1 Right-click Session RG5 ISC_85on your CLARiiON, and choose Start. The status

changes to Active.

2 While the Session is running (Active), copy files to RG5 SC_MV source LUN_85.

3 Browse over the Replicasmenu select Reserved LUN Pool.

Expand the RG5 SC_MV source LUN_85.

Do you see any Allocated LUNs associated with this SAN Copy Session?

4 Right-clickthe session and select Status.

Click MARK.

What status does Session Markeddisplay?

5 Once the session completes, right-click the session and select Status.

Click MARK.

What status does Session Markeddisplay?

6 View the Propertiesof the session and change the session Throttlevalue to 10.

7 Start the session. This transfer should complete quicker than the initial transfer.

Why is it faster this time?

8 When the transfer has completed, view the Session Properties.

Is the Sync Copy Requiredbox checked?

Why is it in its current state?


26/51



Step Action

9 On your partner groups CLARiiON, add RG5 SC_MV Dest LUN_86to the storage groupfor your partner groups Windows host.

Note: Remember to choose the option Show LUNs: All because RG5 SC_MV DestLUN_86is already in the SANCopy Storage Group.

Run DiskManager to ensure the host sees a Physical Drive x.

10 On your partner groups Windows host, use admhost to make LUN 86 accessible.


admhost lun_list

Note: A reboot may be required at this point.

11 Verify that the data (on both of the SAN Copy destination LUNs) is identical to the data on

the Source LUN.

12 Deactivate RG5 SC_MV Dest LUN_86using the following admhostcommand.

admhost lun_deactivateo

13 Remove RG5 SC_MV Dest LUN_86from the Storage Group.

14 Remove the RG5 ISC LUN_86session by right-clicking it, and choosing Remove.

Ensure the RLP LUNs are free.

End of lab exercise


27/51



This page intentionally left blank


28/51



Lab Exercise 4: Create a Synchronous Remote Mirror

Purpose:To create a synchronous Remote Mirror with EMC Unisphere

Objectives: Configure Write Intent Logs

Manage Mirror Connections

Create a synchronous Remote Mirror


29/51


30/51


31/51



Lab Exercise 4

Part 3: Create a Synchronous Remote Mirror

Step Action

1 Browse to the Replicasmenu and select Mirrors, locate the Mirrorsmenu on the left

window and select Create Mirror.

Optionally, right-click your primary CLARiiON, and choose MirrorView > Create

Remote Mirror.

2 The default Mirror type is Asynchronousso choose Synchronousfrom the dropdownmenu as the Mirror Type.

3 Name the Mirror Mirror Thick Pool_0 LUN_0_group, where xis your group number.

4 Set the Minimum Required Imagesto 1.

5 Verify the Use Write Intent Logcheckbox is selected.

6 Choose Thick Pool_0 LUN_0 as the Primary Storage System LUN to be mirrored from theavailable LUNs.

Click OK.

7 View the Replicasmenu, and locate the Replicas Objects and Replication Summary

graphs.

From the Replica Objectsgraph, click on 1 (blue)

From the Mirrors and Consistency Groupswindow, verify the mirror appears and note

the parameters.

Click the mirror, this populates the lower window Primary and Secondary Mirrors note

the parameters.

8 From the top window select the Add Secondarytab.

The Add Secondary Imagedialog launches.

9 Ensure yourpartner groups CLARiiON is selected as the Secondary Storage System.


32/51



Step Action

10 Expand all the containers and note the Capacity of the available LUNs, ( they should all bethe same size as the source LUN).

Choose Thin Pool_0 LUN_1as the Secondary Mirror ImageLUN.

Verify that the Initial Sync Requiredcheckbox is selected.

Verify that the Recovery Policycheckbox is set to Automatic.

Set the Synchronization Rateto High.

Click OK. ( The mirror begins synchronizing after a brief delay)

11 Change some data on Thick Pool_0 LUN_0 (drive F)

Flush the host buffers by using the command:

admhost lun_flusho F:

12 Allow the mirror to synchronize. The secondary image state changes to Synchronizedor

Consistent.

Result: You have created a synchronous mirror and it is now synchronized.

End of lab exercise


33/51





34/51



Lab Exercise 5: Promote and Test a Secondary Mirror

Image

Purpose:Promote the secondary image of a Remote Mirror with EMC Unisphere

The method used simulates a failover

after a disaster.

Objectives: Promote a Secondary Mirror Image

Make the promoted image available to a host

Verify image data content


35/51



Lab Exercise 5

Part 1: Promote and Test a Secondary Mirror Image

Step Action

1 Deactivate the primary image LUN.

Use admhost lun_deactivateo F:, or remove the drive letter using Windows Disk

Management.

2 From the Primary and Secondary window on your partner groups CLARiiON, highlightthe Secondary Image and select the Promote tab.

Take a minute to read the Warning Unisphere message before selecting Yes.

Read the Confirm: Unisphere message before selecting Yes

Click OK.

3 On your partner groups CLARiiON add ThinPool_0 LUN_1 to your partners Windows host

Storage Group.

Wait for your partner group to reach this point.

4 Ensure that the new primary image (of your partner groupsmirror) is accessible to your

partners Windows host.

Go the Hosts menu, select your windows and do an Update

In Computer Management, right-click Disk Management and select RescanDisks. Go to

your command prompt and issue the following commands:


admhost lun_ list

If you do need to reboot your host (though the disk rescan and admhost commands should

have been sufficient) ensure that your partner group is not performing operations on the host

before you reboot it.


36/51



Step Action

5 Assign a drive letter to the primary image if one has not been assigned. (It should alreadyhave one)

Modify files on the new primary image by deleting one or two files.

Flush the host buffers (use admhost).

6 If your status is anything other than Synchronized then you may need to Synchronize themirrors.

7 After synchronization completes, deactivate the primary image LUN with the same choicesas in Step #1 above.

8 Promote the secondary image. Ensure that it is in the Synchronized or Consistentstate

before you do so.

9 Ensure that the primary image is accessible to your Windows host. A reboot may berequired here, though the disk rescan may be sufficient. Ensure that your partner group is

not performing operations on the host before you reboot it.

10 Verify that the modified files are present on the primary image, and that the deleted files arenot present. You have now successfully failed a mirror over to the secondary site, then failed

it back to the primary site.

11 Destroy the mirror.

1. Fracture the Mirror: Right-click the Secondary Image and select Fracture.

2. Remove the Secondary Image: Right-click the Secondary Image again and select

Remove.

3. Delete the Mirror: Right-click mirr85and select Delete.

4. Remove Thin Pool_0 LUN_1 from your Windows host Storage Group on your

partner groups CLARiiON.

End of lab exercise


37/51





38/51



Lab Exercise 6: Create and Test an Asynchronous

Mirror

Purpose: Create and test a MirrorView/A Mirror, using EMC Unisphere

Objectives: Create, manage and test a MirrorView/A Mirror


39/51


40/51



Step Action

11 Why is the mirror the Attention state?

Will the Mirror accept I/O at this time?

Q Test your assumption by attempting to copy several files to RG5 SC_MV_Source LUN_85and then flushing the host buffers. Did the copy succeed?

13 Right-clickthe mirror and choose Add Secondary Image.

14 Choose your partner groups CLARiiON as the Secondary Storage System (default).

15 Select LUN 150 on your partner groups CLARiiON as the Secondary Mirror Image LUN.

16Ensure that the Initial Sync Requiredbox is checked.

Leave the Recovery Policy as Automatic.

Change the Synchronization Rate to High.

Leave the Update Type set to Manual Update.

Click OK.

17 The Mirror Statechanges to Activeand the data state to ConditionUpdating,

Synchronizing.

Note the SnapView and SAN Copy activity associated with this Mirror.

Note Reserved SnapView and SAN Copy Sessions associated with this mirror were automaticallycreated.

18 When the Secondary Imageis 100% synchronized, the SAN Copy Session that was

transferring the data shows a Completedstatus.

19 Right-click Mirror SC_MVA Source LUN_85and select PropertiesSecondary Image

tab.

How long did the Mirror take to synchronize fully?


41/51



Lab Exercise 6

Part 2: Test an Asynchronous Mirror

Step Action

1 Copy several files to RG5 SC_MV_Source LUN_85. Flush the host buffers with

admhost.

Q Did the data state of the Mirror change?

If it did, what did it change to?

Is there a way to determine how much data will be copied at the next synchronization?

2 Right-click the Secondary Image, and click Synchronize.

3 The Mirror changes to the Updatingstate. Because not a lot of data has changed the

Updating state may not be displayed and what you may see is the Consistent state which is

the next state to be viewed.

4 A short while later it will show the Synchronizedstate again.

View the mirror Properties, and ensure that the Mirror state is 100% synchronized

5 On your Windows host attached to your CLARiiON, flush the host buffers and deactivate

RG5 SC_MV_Source LUN_85. Remove it from the Storage Group attached to your

Windows host on your CLARiiON.

6 On your partner groups CLARiiON, right-click your mirror Secondary Imageand choose

Promote.

Click the Force Promotetab to the warning The image specified to be promoted causes theexisting primary to become out-of-sync message.

Q What would the Local Onlypromote choice cause to happen?

7 When the promotion completes, view the mirror under the Primary and Secondary Imageswindow on your CLARiiON. Note the changes you see.


42/51



Step Action

8 Add the new primary image, LUN 150 to the Storage Group attached to your partners

Windows host on your partner groups CLARiiON.

The LUN should be visible after a rescan; if not, reboot your partners Windows host.

Utilize the following admhost commands:

admhost lun_activate and admhost lun_list

9 Verify that the data on the new primary image is identical to that on the old primary image.

10 Make changes to the new primary image LUN 150 by deleting one or more of the existingfiles and flush the host buffers with admhost

11 Right-click the current Secondary Image RG5 SC_MV_Source LUN_85and click

Synchronize.

Change the primary image LUN 150by creating a file on it. Name it after_sync.txt.

Flush the host buffers of the primary image LUN 150using admhost.

Deactivate the Primary LUN 150before you go to the next step.

Note To resume normal operations after a disaster, the original primary copy (now the Secondary

Image) is again promoted to make it the Primary image.

12 Remove the primary image LUN 150from its Storage Group.

What is the data state of the secondary image?

13 Promotethe secondary image. Read the warning messages.

Choose the Force Promoteoption.

What is the data state of the secondary image?

What does this imply as far as synchronization activity goes?

14 Put the (new) primary image into your Windows hosts Storage Group attached to yourCLARiiON.


43/51



Step Action

15 Bring the primary image online to your Windows host. Run the following commands onyour Windows host:

admhost lun_activate and admhost lun_list

16 View the data on the primary image.

Q Is your file (after_sync.txt) present?

17 Right-click Secondary Image, and click Synchronize.

When the synchronization is complete, view the mirror PropertiesSecondary Image tab.

Q How long did this synchronization take?

Q Is this comparable to the time taken in Part 1 ?

Q Why or why not?

End of lab exercise


44/51



Answers

mirr_85Ais in the Attentionstate because it has no secondary images.

It will accept I/O while in that state.

The mirror should take around 30 seconds to synchronize.

There is no way to determine how much data will be copied with the next transfer.

The data state of the secondary isConsistent, thenOut of Sync after the promotion

Out of Syncmeans that a full sync will be needed, and any new files on the primary will be lost.

Asynchronous mirrors allow a certain amount of data loss.

The synchronization should take about as long as the initial synchronization, because both are full

synchronizations of the data.

Notes:


45/51





46/51



Lab Exercise 7: Create and Test a MirrorView/A

Consistency Group

Purpose: Create and test a MirrorView/A Consistency Group, using EMCUnisphere

Objectives: Create, manage and test a MirrorView/A Consistency Group


47/51



Lab Exercise 7

Part 1: Create a MirrorView/A Consistency Group

Step Action

1 Ensure that RG5 SC_MV_Source LUN_85is still the primary image of an Asynchronous

Mirror.

2 Rename RG5 SC_MV_Dest LUN_86to RG MVA_Source LUN_86

Select MirrorView > Create Remote Mirror.

3 Choose a Mirror Type of Asynchronous.

4 Name the Mirror Mirror RG5 MVA Source LUN_86

Set Minimum Required Images to 1.

RG5 SC_MV_Dest LUN_86is automatically chosen as the Primary Image.

Click OKto create the Mirror.

5 Locate the newly created Mirror under the replicasmenu , highlight it and select Add

Secondary.

Choose your partner groups CLARiiON as the Secondary Storage System.

It should be the default.

Select LUN 151as the Secondary Mirror Image LUN.

Set the Synchronization Rateto High.

Leave all other values at the defaults.

6 Wait until the RG5 SC_MV Source LUN_85and RG5 MVA Source LUN_86are both in

the Synchronizedstate.


48/51



Step Action

7 Choose Create Consistency Groupfrom the Replicas > Mirrormenu

When the window launches, give the group a name such as:Consistency Group x

where is your group number.

8 Add both Asynchronousmirrors to the Selected Remote Mirrorswindow

Set the Recovery Policyto Automatic

Set the SynchronizationRate to High.

Set the Update Typeto Start of Last Update. Set the value to 5.

Click OKto create the Consistency Group.

9 Verify the group was created under Mirrors and Consistency Groupson each CLARiiON.

End of lab exercise


49/51


50/51



Answers

You cannot manage individual mirrors once they are in a Consistency Group

The status changes to the Attention state because you have fractured the mirrors after setting the

required number of secondary images to 1.

Answers

A normal prerequisite for creating an Asynchronous Mirror is that Reserved LUNs should be present

in the Reserved LUN Pool on both CLARiiONs. The Wizard does not require this; it will bind and

allocate its own Reserved LUNs.

Two new Reserved LUNs will be bound on each of the Primary and Secondary CLARiiONs. The

RAID Group selected will be the one with the most free space.

Mirror synchronization starts automatically. The Wizard has no mechanism to allow manual startingand stopping of synchronization


51/51



MR-1CP-MVSCSP_Lab_Guide_R30_.pdf

Documents

Transcript of MR-1CP-MVSCSP_Lab_Guide_R30_.pdf