Start a Conversation

Unsolved

This post is more than 5 years old

15699

February 14th, 2011 22:00

OpenReplicator Hot PULL , step by step

I have create a document for OR HP step by step and i wana share it

OpenReplicator Hot PULL ,

1.Environment:

Destination VMAX,

Source :CX4   ,

OS=Window 2008 ,

Application: Exchange

, Cluster: Window CCR Cluster , replication cluster

*Control Device: VMAX,  control device the one who manage the OpenReplicator Session

Remote Device:CX4

* both Control and Remote  should have prober HA power and SAN connectivity

No Power or SAN failure can be acceptable during migration .

*PULL  , Control is the Destination and Remote is the Source

*Push , Control is the Source , and Remote is the Destination

*Control Always Symmetrix Storage System

*the Below notes are regarding Hot PULL

*Remove SCSI reservation flag if u have it on lun

2-Connectivity

2.a.  Zone VMAX ports to CX4 ports:

each ports on vmax that have access for Destination LUN , should be zoned to both SPA and SPB ( in hot pull or hot push ), symcfg list -fa all -sid 2221 # show wwpn for fa

in our case LUN on VMAX mapped to 7F0 and 10F0

so zoning was like

7F0 to SPA2

7F0 to SPB0

10F0 to SPA0

10F0 to SPB2

Now check that VMAX is able to see CX4

Display Remote Ports WWNs:

?? symsan –sanports –sid -dir <# | ALL> -port <# | ALL>

this should display all storage ports that connected to VMAX    

2.b, Discover CLARiiON by SYMCLI

add authorization for both SPA SPB

DMX800SUN1/> symcfg authorization add -host 10.127.38.41 -username navisphere_mosa

-password ***

DMX800SUN1/> symcfg authorization add -host 10.127.38.42 -username navisphere_mosa

-password ***

DMX800SUN1/> symcfg authorization list

cat calr.txt

SPA-IP  SPB-IB

10.127.38.41 10.127.38.42

symcfg disc -clariion -file clar.txt  ( u need to run this , before u start OR session again )

symdev -list -clariion

2.c. Masking Source LUN to VMAX:

Vmax port act as target not as initiator  , so can't be seen in Navisphere --> Connectivity status

and we need to create this entry for FA manually

so

from connectivity status

create initiator record by entering in HBA wwn :WWNN:WWPN of the FA port.

symcfg -sid xxxx list -dir ALL -v ( for VMAX WWNN and WWPN have different value as emc226479)

Vmax You will create 4 initiator records (7f0 to registered to SPA2 , and SPB0 ... etc)

and all these initiator records to be registered for one host ( name vmax-host-sg)

Now Mask CX4 LUN to VMax by creating New Storage Group that have Cx4 LUN and  vmax-host-sg

Double Check that VMAX is able to see CLARiiON LUNs

symsan -sanluns –wwn –sid -dir <# | ALL> -port <# | ALL>

or From SMC

Right Click on VMAX - Replication - OpenReplicator - Remote Report

3. Add License to symcli , symlmf

Open Replicator/DM — for all functions except Online Pull.

Open Replicator/LM — for Online Pull only.

4. do some checking

4.a symdev show 1c5, get  number of blocks on vmax

right click lun on navipshere - properties and check number of blocks

source should be bigger or equal

4.b. for cold to make device on control vmax unready

symdev not_ready 1c5 -sid 58 -noprompt

to make deivec ready after migration

symdev ready 1c5 -sid 58 -noprompt

5. Create OpenReplicator Session

5.a unmask LUN from CLARiiON ( No IO allowed ) , before that u need umount the disks, unassigned drive letter .

5.b create file that have Control and Remote LUNS
example1: VMAX and Non-EMC storage file format

symdev=VMAX ID:LUN CID      wwn= for the remote LUN on HP , u can get wwn  From SMC Right Click on VMAX - Replication - OpenReplicator - Remote Report

vi elian

symdev=000187430917:07A0 wwn=60060160F2810D00281B2B093212D911

symdev=000187430917:07A1 wwn=60060160F2810D004AD5205A3212D911

example2: left column is the control storage system, clariion should be discovered and u need to run symcfg disc -clariion -file clar.txt

symdev=VMAX iD : LUN CID   clardev=Cx4 serial number : Lun ID  ( as appear on SMC Right Click on VMAX - Replication - OpenReplicator - Remote Report)

vi elian

symdev=000187430917:07A0 clardev=APM00034801589:0063

symdev=000187430917:07A1 clardev=APM00034801589:0064

5.c CX4 LUNs are unmasked from the host ( Source LUN) , while VMAX LUn masked to the hosts but not mounted , not assigned drive letter and there is no partition on these disk (Destination LUN).

5.d. symrcopy create -copy -name mosa  -pull -hot -donor_update -file elian

donor_updaet necessary for online

for cold use

symrcopy create -copy -name mosa -pull -cold -file elian

5.e symrcopy query -detail -file  elian

session is create but still not activated

5.f. symrcopy activate -file elian

5.g symrcopy query -detail -file  elian

now CopyInProg

5.h  tune the speed

take care , and OpenReplicator should be done with Minimal IO activity

Copy On Access have some performance issue

if application have heavy IO that will slow OpenReplicator

pace 0 fastes , 5 default

do not change celing and change only pace

symrcopy –file elian  set pace 0

symrcopy list ceiling -dir all -sid 2221

To set a bandwidth ceiling of 100% for all directors on Symmetrix 6190, use the

following example:

symrcopy set ceiling 100 -dir all -sid 6190

You can view the new ceiling setting by using the list ceiling command, as follows:

symrcopy list ceiling

5.i Now we can Run our application (while Copy run in background )

since hot pull use CopyOnAccess

so in window rescan disk

after sometime ( Window is a bitch and need some time)

you will found that VMAX disks have Partitions and Same Volume Labels

assign Drive Letter to these Volume

and RUN ur application.

note:cx4 disk should be unmasked , so in this step you don't have Duplicated Disk or Duplicated disk ID

on Linux

scan scsi bus

pvscan

vgscan

lvscan

mount new voulmes

or just reboot

unix > vgimport, better to reboot before importing

You do not need to wait for the copy operation to

complete

5.j symrcopy query -detail -file  elian

        keep checking status

       once done

5.k

symrcopy terminate -file elian  -force

use -force if u used donor_update in hot pull

5.l

Clean Up

delete vmax-host-sg

delete zone between vmax and clariion

5.m

R007 NAm

1 Rookie

 • 

20.4K Posts

February 15th, 2011 13:00

step 4a, shouldn't it say:

source (Clariion LUN)  should be equal or smaller or another way ..Control device should be equal or greater.

265 Posts

February 15th, 2011 21:00

if somebody push data from 64 GB LUN to 96 GB LUN and he want to pull it back , then we use -force_copy since in that case destiniation LUN is smaller

,

anyway i dont feel good with force_copy , should i ?

Message was edited by: Mosa Elian

265 Posts

February 15th, 2011 21:00

yes

Destination should be equall or greater , although we can use force_copy if destination is smaller than source

1 Rookie

 • 

20.4K Posts

February 15th, 2011 21:00

i would make a side note of that because somebody needs to understand why they force copy something to smaller device (not fully partition device ..whatever).

2 Posts

March 8th, 2011 11:00

how long does it typically take for Windows to see the partition on the new drives?  I've had to reboot windows servers a few times before i could assign a drive letter, does anyone have this problem?

5.7K Posts

March 9th, 2011 04:00

You've said it: Windows....

Should be instantanious, but it's windows, so anything can happen. This does sound very bad, but IMHO it's what it is.

60 Posts

June 22nd, 2012 23:00

Hi,

May I know what exactly shoud be given in connectivity status in order to register FA port.

Please let me know what things has to b filled to register FA port. It would be helpful, if its explained with an example of an FA port.

1 Rookie

 • 

20.4K Posts

June 23rd, 2012 06:00

this is what i use when i use OR between DMX3 and VNX

Array commpath: Enabled

HBA Type: host

Failover mode: 1

Unit serial number: array

Initiator type: Clariion Open

60 Posts

July 21st, 2016 13:00

Hi Dynamox

Am trying to perform hot push from vmax to vnx8000. Could you please help me with array registration.

VNX.bmp

1 Rookie

 • 

20.4K Posts

July 21st, 2016 16:00

there is nothing to enter in the advanced section. For host name and IP address enter anything you like, when you register the next FA you will select "Existing Host" but you still need to make sure to select correct Initiator type and Failover mode.

5 Practitioner

 • 

274.2K Posts

February 14th, 2017 05:00

Thanks for the great info on Open replicator steps. thank you..

No Events found!

Top