Hot Push From VNX5700 To VMAX20

Daniel,

i have never seen a paper but there is not magic there. Treat  VNX as if it was another host, complete your zoning, masking view stuff and you should be good to go. To force VNX login to VMAX (after zoning is complete), select Update SANCopy connections in Unisphere.

Hello Daniel,

Welcome to the community.

Have you checked this whitepaper,

https://www.emc.com/collateral/software/white-papers/h2099-emc-clariion-san-copy-wp.pdf

It is not specifically for SYMETRIX but it gives you all steps required to setup the hot push session.

Hope that helps

Mohammed Salem

I have this one, thanks.

You can run Incremental SAN Copy hot push. in such a case, you would  perform a full SAN Copy with your applications online on the VNX, then run incremental SAN Copy sessions to keep the tracks in sync before the maintenance window. During the maintenance window, Shutdown your applications, run one more incremental SAN Copy, and then bring your applications  back online on the VMAX.

Hope that helps

Mohammed Salem

I was afraid that a hot-push may not be possible from VNX to VMAX, but it sounds like it is. Thanks.

Yes, that's the plan!

do you have any Windows clusters, depending on the options you use in SANCopy you may have to bring the cluster offline for that initial copy.

i am looking for the KB that described it (unless it only applied to Win2k3 clusters). From what i remember it was talking about SANCopy not being able to start the session because the LUN had an active cluster reservation which would not allow SANCopy to temporarily "claim" the LUN so the suggestion was to not use -nomark for cluster volumes. If you have migrated win2k8 clusters using nomark than it's it must have only applied to win2k3.

I leave the cluster up while doing the initial copy. I use this command.

naviseccli -h n1st04em -user XXX -password XXXXX -scope 0 sancopy -start -name "session name" -copywholelun -nomark all

@Dynamox, Can you share with us any doc for SANCopy recommendations with MS Clusters, I am not aware of any!

For the reservation part, It should not be a problem as long as the target LUNs has SCSI3_Persist_reserv flag set to enable and this is the default with VMAXs shipped with ucode 5876. Appreciate if you can clarify further.

Hope that helps

Mohammed Salem

I'm confused now. I've been using nomark for quite some time now on clusters without a problem. How does using a snapshot handle the reserve differently?

that will not work with clusters, you need to make sure SANCopy creates a SnapView snapshot (in the background) and uses that as the source for the copy process. By specifying -nomark you are telling SANCopy to not create a snapshot, that's fine for regular open systems but not for MS clusters because there there is a reservation placed on the LUN.

I'm migrating a Win2k3 cluster to a win08R2 on top of moving from VNX to VMAX.

Daniel Jastredowski wrote: I'm migrating a Win2k3 cluster to a win08R2

how are you doing that ?