I have to implement SANCOPY data migration between Clariion and VMAX and obviously it is going to be an incremental push. I have few questions before I proceed,
1. ZONING:
Planned to use 4 front end ports from Clariion and VMAX.For example SPA0 & SPB2 (fabric A) and SPB1 & SPA3 (fabric B)
VMAX - 8H0 & 10H0 (fabric A) and 7H0 & 9H0 (fabric B)
what is the best practice for zoning pertaining to SANCOPY
1st method
SPA0 to 8H0
SPB2 to 10H0
SPB1 to 7H0
SPA3 to 9H0
or
2nd method Do we really need SP redundancy at Clariion end? Please explain.
i would not bother with 2nd method unless you really need 4 active paths for performance (not likely your backend push that fast anyway) , VMAX is active/active so you can write to any port on 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.
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.
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
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
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.
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.
I have never used the wizard myself, i think it only works if your target is another Clariion/VNX (that also needs to be in the same Unisphere domain). Go for the CLI.
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.
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?
dynamox
11 Legend
•
20419 Posts
•
87439 Points
1182
1
Posted July 20th, 2014 13:00
i would not bother with 2nd method unless you really need 4 active paths for performance (not likely your backend push that fast anyway) , VMAX is active/active so you can write to any port on VMAX.