Migrations using Mirror View and SAN Copy

I migrated ~10 windows hosts from a CX700 to a CX3-40 a couple months ago using Mirrorview/S. It was a very easy process for me and I didn't run into an issues. I don't have any experience with Mirrorview/A or SAN Copy, so I can't compare between these offerings.

I simply setup the mirror, let it fully sync, broke the mirror, attached the host to the new array. I setup the mirrors days in advance of the scheduled cut date for each host to allow for plenty of time to synchronize at medium or low speed.

As long as you know how to use Mirrorview and you're comfortable zoning it's pretty easy to do. Probably the most time consuming part for me was creating MetaLUNS on the destionation array of exactly the same size (to the block) as the source. I used a different size drives, different number of drives, and a different raid type on the new array, so I had to take the block size on the original, divide it by the number of components and create those. I used NaviCLI heavily to simpify matters.

Thank You Shewiit. Do you have any documentation for these migrations. I would appreciate if u send dat to me ...

also can u please tell me wat are the basic considerations that we need to consider wen we are planning to do migrations. do u have any specific procedure to do this migrations....?

When mirroring the data, keep in mind that it will take a while, and that you will be adding IO to the source and destination system. You will also be increasing the write latency for all writes since you have to write to the source system and destination system before sending the acknowledgement back to the host (this is only true for Mirrorview/S which is what I used).

Sorry, I don't have anything specific or documented I can give you, but if you have more questions about specific aspects of the migration, please ask.

Can you please help me with the migrating steps...........

i think MirrorView is more likely a DR solution
while SANCOPY is a migration solution
if u wana to use both , u have to know that they cant use same ports on storage system
"MirrorView/S and MirrorView/A use dedicated ports on supported storage systems - the highest numbered port on each
SP. The port may be shared with host I/O, but may not be shared with SAN Copy."
for SANCOPY or MirrorView steps
send for me ur email

plo,

is this something that you could share with everybody ..so everybody could benefit ?

Thank You Very much. I appreciate you help. My email ID is vvajinap@gmail.com

Shewitt

Did you create any consistency groups when using Mirror view to migrate the windows servers? or Did you sync it first with mirror view/ A and after that did u use mirror view/S?

I did not use any consistency groups. Because you will have to shutdown the host and wait for IO to quiesse, I don't believe it's necessary. Since I was using Mirrorview/S, once the host was shutdown, all IO stopped, so I was able to break each LUN one at a time.

I only used Mirrorview/S. I don't think it's possible to change a LUN from one Mirrorview type to another. I can't think of why you would want to do this for a migration anyway. Setup Mirrorview/S, let it replicate the data, when you're ready, shutdown and rezone the host and you're done.

Basic steps
1. Create destination LUNS on new array
2. Mirror data to new array using Mirrorview/S
3. Wait for all data to me migrated and schedule an outage window
4. Wait for outage window
5. Shutdown host
6. Break mirror
7. Re-zone host (connect it to new array and remove from old array)
8. Present luns to new host via a storage group on the Clariion
9. Boot host and test.

I understand that you cannot switch from MV/A to MV/S without having to do a full resync ! there was another thread on only this last week. Let me check it for you....

check out this thread: http://forums.emc.com/forums/thread.jspa?threadID=87754&tstart=50

Hey Plo,

Can you please send me the SAN Copy and mirror view steps to my email.

some hints
*SAN Copy cannot share an SP port with MirrorView.
*Access Logix is required
*The throttle value controls the I/O rate for an active SAN Copy session. You can set the session throttle to a value between 1 and 10 where 1 is the lowest I/O rate and 10 the is highest. The default throttle value setting is 6.

Steps:
* Connection
Right Click on ur storage group ->SAN COPY -> Connections
-->dialog box opens --> select ur CLARiiON SP that includes in sancopy port
check Tool --> SANCOPY -->Connections Summary
or Expand Storage Group --> Expand ur sg --> Expand SANCOPY connection

* Setting
Right Click on the storage system --> SANCOPY --> Settings
set Buffer size / # buffer per session and # session per sp

* Session
Right Click on the storage system --> SANCOPY --> Create Session
Wizard Screen will appear
where you can select session type full or incremental
select source storage system and SRC LUN
Select destination storage system and DST LUN

* Start Session
Expand storage system-->Expand Sancopy sessions --> Select ur session --> right click ---> start