EMC Lab Guide2 series

EMC2 ***Copyright EMC Corporation August 2008***

Name: ____________________________

Date: ____________________________

EMC2 CLARiiON Replication Software

CLARiiON Training for Engineering

Lab 03 SAN Copy Configuration and Management

Summary:

In the first part of this exercise, you will create a lab configuration to support remote replication using SAN Copy and MirrorView. After the lab is setup, you will configure and perform a full remote copy of a LUN to a second CLARiiON using SAN Copy, followed by an incremental copy using Incremental SAN Copy (ISC). Operations will be performed using EMC ControlCenter Navisphere Manager and CLI.

The exercise is broken into three parts: Lab Preparation, Remote Full SAN Copy, and Incremental SAN Copy.

Objectives:

Following this exercise, participants should be able to: a) Merge two separate lab configuration into a single SAN fabric. b) Merge Navisphere Security domains for two lab groups. c) Configure SAN Copy connections. d) Create a Remote SAN Copy Session using the Wizard. e) Create and manage an Incremental SAN Copy Session. f) Use the admhost utility to manage and control host volumes used in a SAN

Copy scenario.

CLARiiON Replication Software Lab 03 SAN Copy


2

Part 1: Preparation Configure Remote Replication Environment. This exercise requires two CLARiiON arrays, two Windows hosts, and a SAN fabric to connect all components. To create this environment, you will be merging two lab setups into a single configuration. This includes merging the SAN fabrics and Navisphere Security Domains.

The followings steps must be completed in coordination with another lab team. You will be creating a single lab configuration out of what was previously two independent configurations. You will be completing this exercise as one team!

When complete, your lab environment will be configured similar to the following diagram:

Work with a lab team that is next to you. Agree on which teams configuration will be the Source array and which will be the Destination array. Complete the table below.

Source Destination Hostname Windows Server: NAV6-PROD1 NAV6-PROD2 Array Name: NAV6-POD1 NAV6-POD2 SPA TCPIP Address: 10.127.36.6 10.127.36.13 SPB TCPIP Address: 10.127.36.7 10.127.36.14

W2K3 (Primary)

W2K3 (Primary)

Switch

Source Array

Destination Array

SPA SPB SPA SPB

Team 1 (Source) Switch

Team 2 (Destination)



3

1) Configure SAN Fabric. a) Verify Fibre Channel cable connections between array and switch. Port 0 and the

high number port of both SPs must be connected to the switch. Note: It is important that the correct SP ports are connected to the switch. If your array is a CX700/600 or a CX3-80, ports 0 & 3 of both SPs should be connected to switch. If you are using a CX300/400/500 or CX3-20/40 array, ports 0 & 1 of both SPs should be connected to switch. You will only be using the Primary Windows hosts that are connected to each array. The Secondary Windows hosts and the Solaris hosts should be powered down and the Fibre Channel cables removed and rolled up.

b) Verify that both Fibre Channel switches have unique domain numbers. If your configuration uses Brocade switches, log in to the switch and verify domain numbers. Each switch must have a unique Domain number

(1) Telnet (2) Enter user ID = admin and Password = password (3) Enter command: SwitchShow (4) If the domain numbers are not unique, disable the switch

(SwitchDisable), run the configure command and change the domain numbers, and re-enable the switch (SwitchEnable)

c) Connect at least one Inter Switch Link (ISL) between the switches to merge the switches into a single fabric. On the switch, execute the command FabricShow to verify that the fabrics successfully merged.



4

2) Merge the two arrays into a single Navisphere Storage Security Domain. For this exercise, both the Source and Destination arrays must be part of the same security domain. Previously both arrays were configured as their own domain. a) Open Navisphere Manager on the Primary Windows host that is attached to the

Source array. Click File, Set Up Domain, Configure Domain

b) In the Configure Domain window, enter the IP address of SPA of the Destination

Array and click the right arrow.

c) You will get a warning that the array is already participating in another Domain. Click yes to continue.



5

d) Next, you will be prompted for a username and password for an user with administrator level access. Enter the username admin and password pass.

e) The Destination array will now display in the Selected Systems: Click OK to add it to the Domain.

f) If the Domain merge was successful, Navisphere will now display both arrays in the same window. The following is an example:



6

3) Rename each array as source and destination. Right-click on each array and select Properties and change the name to identify the Source and Destination arrays. The following is an example of two appropriately named arrays:

4) Verify LUN configuration. The appropriate LUNs should have been configured in the preceding CLARiiON Environment & Application Integration class, but it is important to verify, as this exercise requires specific LUNs of specific size, names, and ownership. a) On the Source array:

i) Verify that LUN 85 exists, is of size 1.875GB, owned by SPA, and named -SC_SRC.

ii) Remove all LUNs for the Storage Group for the Primary Windows host. Add LUN 85 (SC_SRC) and reboot.

iii) Open Windows Disk Management and initialize LUN 85 (SC_SRC) as a Basic Disk, create a Primary Partition, assign drive letter, and format a NTFS file system with volume label of Volume_SC_SRC.

iv) Open Windows Explore and verify the drive letter is available. Add test files to the volume by copying a large director such as Program Files.

b) On the Destination array: i) Verify that LUNs 83, 84, and 86 exists, are of size 1.875GB, owned by SPA.

ii) Rename LUN 86 ISC_Dest.

iii) Remove all LUNs for the Storage Group for the Primary Windows host and

reboot.

5) Install the admhost utility on the Primary Windows hosts that are attached to both the Source and Destination arrays. A zip file containing the install files is located in the folder C:\Release26\win2K3. Open the zip file and execute the appropriate file admhost_win*.exe.



7

Part 2: Using SAN Copy to move the contents of a LUN to a remote CLARiiON In this section of the exercise, you will configure SAN Copy and copy the data on a local LUN to a LUN in a remote CLARiiON system. You will be performing this exercise as one team. 1) Update the SAN Copy connections. SAN Copy uses SCSI Initiator and Target

protocols similar to a host, and therefore, before the two arrays can communicate, initiator records for the SP ports must be created and the SP ports registered with each other. The following steps will create initiator records and register the remote arrays. a) For both the Source and Destination arrays, right-click on the array and select

SAN Copy > Update Connections.

b) At the confirmation message, click OK.



8



9

c) Read the next informational message and click OK.

2) Verify that the SP ports of the remote array registered with the local SAN Copy array. There should be an initiator record in the Connectivity Status panel for each connection to each SP port on the remote array.

a) Right Click on the array and select Connectivity Status.

b) The following is an example of the Connectivity Status window. Check the box for Show Storage System Initiators and verify Worldwide Names for the remote SP Port. Also verify that Registered is Yes indicating the array agent has registered.



10

3) Create a Storage Group for SAN Copy. For hosts, Storage Groups determine which hosts have access to which LUNs. Because the SAN Copy SP port emulates a host, a storage group must be configured on the Destination array. However, rather than connecting a host to the Storage Group, you will connect the SP ports of the Source array. a) On the Destination array, create Storage Group and name it

SANCopy_Destination.

b) Configure SAN Copy connections. Right-click the Storage Group you just created, and select SAN Copy > Connections.

c) Choose SPA of the Source storage system from the SAN Copy System drop-down list, check Port 0, and click Advanced...

d) We only want to use Port 0 for SAN Copy, so make sure that only the zero ports

are checked. Click OK.



11

e) Repeat the above steps for SPB.

f) Verify that the connections were defined correctly. On the Destination array,

expand the SAN Copy Connections container for the Storage Group SANCopy_Destination and verify that both SPA and SPB of your Source array are connected.

g) Add the destination LUNs to the SANCopy_Destination Storage group. Using the same process as you would for a normal Storage Group, add LUNs 83 and 84 to Storage Group. The following is an example of a properly configured SAN Copy Storage Group:

4) Prepare the Source LUN. Full SAN Copy does not support changes to the Source LUN during the copy, therefore it is necessary to deactivate the source LUN before starting the copy session. a) Using the admhost utility, verify the drive letter for the SC_SRC LUN.

admhost lun_list

b) Flush the buffers and deactivate the SC_SRC LUN using the admhost utility. admhost lun_flush o admhost lun_deactivate o



12

5) Create a SAN Copy session using the Wizard. a) Right-click on your Source array and choose SAN Copy > Create Session.

b) The SAN Copy Create Session Wizard launches. Read the steps that the wizard

will perform, and click Next.



13

c) Next, the wizard will describe the two types of SAN Copy: Full and Incremental. While they are both configured very similarly, how they work internally is completely different. In this part of the exercise, we will be doing a Full SAN Copy. Later we will perform an Incremental SAN Copy. Choose Full as the Session Type.

d) Select your Source array from the Storage Source drop-down list, and choose

LUN SC_Src from the LUNs listed in the lower pane. Click Next.



14

e) In the next dialog, right-click the Source LUN and click on Select Destination

Storage

f) The next dialog allows you to choose the array and LUNs.. In our example, we will be making two copies of the source LUN. Choose your Destination array as the Storage Destination, then select LUN 83 and LUN 84, and move them to the right-hand pane. Click OK.



15

g) Check the Verify Connections box, and click Next.

h) The Wizard will check the connection to the remote array. You should see a message confirming that all destination LUNs are accessible. Click OK.

i) The next dialog allows you to change the Session Name and Throttle value. Highlight the Session, and click the Edit button. Change the Session Name to SourceLUN85 and the Throttle value to 10. Click OK.



16

j) The Summary screen appears next. Verify that all the settings are correct, and click Finish.

k) Verify that the SAN Copy Session was configured. Expand the SAN Copy Sessions container on Source storage system.

6) Start the SAN Copy Session. Right-click session SourceLUN85, and choose Start.



17

a) The session will start, and the status changes to Active.

b) View the session status and the copy progress. Right-click on the session, and choosing Status. Wait until the copy status is Completed before continuing.

7) Verify that the data on the Source LUN was copied to the Destination array.

a) Add LUNS 83 and 84 to the storage group for the Primary Windows host

attached to the Destination array.

Note: This is technically an unsupported operation as it will result in two copies of the same LUN, with the exact same data being presented to the same host at the same time.



18

b) Bring the LUNs on-line. On the Primary Windows host attached to the Destination array, use the admhost utility to make the volumes on the Destination LUNs available. admhost lun_activate admhost lun_list If the LUNs were not brought on-line, it may be necessary to reboot the host.

c) 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.

d) Deactivate both destination LUNs using the admhost utility. admhost lun_list admhost lun_deactivate o admhost lun_deactivate o

e) Remove LUNs 83 and 84 from the Storage Group of the Primary Windows host attached to the Destination Storage System.



19

Part 3: Using Incremental SAN Copy In this section of the lab exercise, you will configure an Incremental SAN Copy (ISC) session and first perform a fully copy and then an incremental update of changed data. There are several advantages to using Incremental SAN Copy; reduced time to synchronize, reduced performance impact on array and SAN, and the ability for the source volume to be active during the copy. 1) On the Primary Windows host attached to the Source array, re-assign the drive

letter to LUN 85 (SC_Src) and verify that it still has files. Execute the following command:

admhost lun_activate

2) Configure the SAN Copy Storage Group. On the Destination array, add LUN 86 (ISC_Dest) to the Storage Group SANCopy_Destination.

3) Create a SAN Copy Session. This time, rather than using the Wizard, we will create it directly. a) On your Source Array, right-click SC_SRC (LUN85). Choose SAN Copy >

Create Session from LUN. LUN 85 will automatically be selected as the Source LUN. Set Session attributes as follows: i) SAN Copy Session Name: SourceLUN85_Incremental ii) Session Type: Incremental iii) Initial Sync Required - checked iv) Session Throttle: 6 v) Link Bandwidth: 1024



20

b) Click the Select Destination Storage button. Specify the Destination array as the Storage Destination, and LUN 86 (ISC_Dest) as the Destination Storage for Move. Click OK.

c) Click OK to complete the Session creation

d) View the Session in Navisphere Manager. The Session will appear as [Initial

Copy Required].



21

e) View the Status of the Session. Right-click on the session SourceLUN85_Incremental and select Status. You should see that the LUN size in blocks and the number of blocks to be copied are the same because initial sync is required.

4) Start the Session. Right-click on the session SourceLUN85_Incremental and select Start... The status will change to Active.

5) Modify the source LUN while the copy Session is running. As we are performing an Incremental SAN Copy session, the source LUN can be active during the copy. This is because Incremental SAN Copy uses snapshot technology and performs a Copy-On-First-Write to preserver the point-in-time view for the LUN. a) View the SnapView session. Expand the SnapView Snapshot and Sessions

containers. You should see Reserved sessions and Snapshots for SAN Copy.



22

b) View the Reserve LUN Pool for SPA and verify that a LUN has been allocated.

6) View the Status of the Session. a) Right-click on the session and select Status. The session should be Marked

indicating that copy is in progress and that Copy-On-First-Write is keeping track of the changes in the Reserve LUN pool.

b) Once the Session completes, view the Status again. The state should be

Completed. c) Start the Session again. The transfer should complete quicker than the initial

transfer as only the new changes since the start of the initial copy is transferred.

7) Make the target LUNS available to the Windows server attached to the destination Array.

a) Add LUN 86 (ISC_Dest) to the storage group for your Primary Windows server attached to the Destination Storage System.

b) On the Windows server attached to the Destination array, use admhost to make the volume accessible.

admhost lun_activate admhost lun_list



23

c) Verify that the data on both of the SAN Copy Destination LUN is identical to the data on the Source LUN.

d) Deactivate the destination LUN.

admhost lun_deactivate o

e) Remove LUN 86 (ISC_Dest) from the Storage Group.

End of Exercise.



24

EMC Lab Guide2 series

Documents

san copy configuration

san copy emc2

san copy connections

san copy scenario

remote copy

remote san copy session

incremental copy

incremental san copy