SANCOPY - CX to VMAX

Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.

glen

Dynamox,

   Yes here performance is a major concern and they would want to spread out the ports for SAN COPY migration.

Today I did my zoning part and after that I see only SPB ports logged into VMAX FA ports and not any single SPA port logged into VMAX FAs. Looks weird! Any suggestions?

This is going to be incremental push and I would like to know few steps post zoning,

Do we have to register VMAX ports on clariion? - If so please give the guidelines on how to register thru unisphere.

Thanks Glen and I was yet to respond to the replies and yes always I make sure I do acknowledge.

Did you run "Update SAN Copy Connections" ?

You don't need to register VMAX ports on Clariion since you are pushing to VMAX. Just need to make sure Clariion WWNs can see target devices on VMAX (device group, initiator group ..masking view ..all that jazz)

General process should be you complete the zoning, verify everything is logged-in (symaccess -sid 123 list logins). Create devices on VMAX to match Clariion devices. For example i like to create devices that identical in size

naviseccli -address vnx5600n1spa lun -list -l 01071
LOGICAL UNIT NUMBER 1071
Name:  LUN 1071
UID:  60:06:01:60:03:A0:36:00:31:37:EB:0E:DB:CF:E3:11
Current Owner:  SP B
Default Owner:  SP B
Allocation Owner:  SP B
User Capacity (Blocks):  70709760
User Capacity (GBs):  33.717
Consumed Capacity (Blocks):  77220864
Consumed Capacity (GBs):  36.822
Pool Name:  Pool 0 - Prod
Raid Type:  Mixed
Offset:  0

So i am looking for "User Capacity (Blocks) value, 70709760 in this case. Now to create a VMAX device i will convert from block to cylinders

blocks / tracks per block  / cylinders per track

70709760 / 128 / 15 = 36828 (cylinders)

Now you know how many cylinders you need to use to create your device on VMAX. I don't know what is the standard in your shop but in my shop each symdev is 18414 cylinders (~17G) so i would have to create a 2-way meta where each member is 18414 cylinders in size.

After that it's easy, create your SANCopy session, i use the CLI because it's so much faster than the GUI

• Create SANCopy session

NaviSeccli.exe -user Administrator -password password -scope 0 -address 10.1.8.30 sancopy -create -incremental -name Lun546to19C8Mig -srcwwn 60:06:01:60:99:51:0D:00:DE:6A:04:C6:09:49:DA:11 -destwwn 60:06:04:80:00:01:90:10:45:18:53:30:31:39:43:38 -throttle 10 -verify

• Start session

NaviSeccli.exe -user Aadmin -password password -scope 0 -address 10.1.8.30 sancopy -start -name Lun546to19C8Mig -copywholelun -nomark all

• Monitor progress

NaviSeccli.exe -user Admin -password password -scope 0 -address 10.1.8.30 sancopy -info -all

• Start incremental session, you can run this as many times as you like. I like to running it multiple times before the final cut-over to keep target as close to source as possible. On the day of migration, shutdown source application/server, run this one more time.

NaviSeccli.exe -user Aadmin -password password -scope 0 -address 10.1.8.30 sancopy -start -name Lun546to19C8Mig

• Once application is online you can go ahead and terminate the session

NaviSeccli.exe -user Admin -password password -scope 0 -address 10.1.8.30 sancopy -remove -name Lun546to19C8Mig

Also don't forget to check SANCopy session on CX, i think by default it's limited to 4 concurrent session, you might want to bump it up a bit.

I hope this helps

Dynamox,

  You are awesome. Update San Copy connections worked and now all the SP ports are logged into VMAX FA's. So I have to proceed further with your guidelines and hope it works too. Thanks a lot.

have fun, getting everything talking is the more "involved" part, the rest is easy.

First I have completed the zoning between CX4 and VMAX

Below is the info,

7H:0 to SPA0 & SPB1

8H:0 to SPA1 & SPB0

9H:0 to SPA2 & SPB3

10H:0 to SPA3 &SPB2

and verified everything is logged-in (symaccess -sid 123 list logins).

Created devices on VMAX to match Clariion devices and then created storage grp, port grp, initiator grp (clariion sps wwn) and masking view

Now I am in SAN Copy wizard and have selected my source LUN and right clicked to select Destination storage but it is not showing the destination storage box on the drop down . what could be wrong? any idea.

Thanks

Oh yeah, it worked. Thanks

One more question

The idea here is to have a dedicated portgroup at the VMAX for SAN copy and once the data is 100% migrated

a) fracture the san copy session

b) remove the device from storage group with -unmap flag

c) present the device to host with a new masking view through a different port group

My questions,

1. Here when we create the initiator group for host we will enable the below flags,

Port Flag Overrides   : Yes

  Enabled             : Common_Serial_Number(C)

                              SCSI_3(SC3)

                              SPC2_Protocol_Version(SPC2)

  Disabled            : N/A

Consistent Lun     : Yes

so the question is when I create the initiator group for SAN Copy with clariion SP WWNs, is it required to enable the same flags?  If it is not required, why?

2. Will the same flags will be enabled at port group level by default?

a), b), c) - what you listed should work, you could also create a second masking view that would consist of the host init group, port group (different pg from the one being used for SANCopy)  and storage group (that contains the same devices) and have that all ready. As soon as the SANcopy session is finished you can terminate it, zone the host to VMAX boot it up and it should be good to go.  Once app is up you can go ahead and remove the masking view that was used for SANCopy (with -unmap assuming you used a dedicated port group , not the same one that's being used for host presentation).  I wanted to bring it up as an option but if you have all your port groups, storage groups, initiators group ready ..then it's just a matter of putting them into a masking view. Lot of options ...you decide what works best for you.

1) Aren't those flags already enabled by default on the FA ? They are on mine

symcfg list -sid 123 -fa 7g -p 0 -v

2) related to 1 , those should be enabled by default unless someone intentionally unset them

no need to set those flag at the initiator level if they are already set at the FA level.

yup, these SCSI flags are enabled on FA by default but still I don't know why these flags are enabled at initiator group overriding port group!! I'm new to this environment and trying to understand.

Thanks a ton.

Is there way to have more than one LUN getting migrated for a session? creating a file with many source & dest LUNs wwn just like in open replicator.

new nickname ?

nope, one session is one source and one or more targets. You can start a bunch of sessions at once, how many will run concurrently depends on the setting below, the rest will queue up and wait for its turn.