Open Replicator Hot Push

Hi Dynamox

Thanks for the reply.

Few queries :

1. Once the VMAX FA ports are registered as a host in VNX then we need to create a storage group in VNX with VMAX FA's as host and connect  it to the VNX SG that contains target luns of VNX.  Is this correct ?

2.  Above is the OR Masking view and no other OR masking view needs to be created on the control VMAX array ?

3. I referred docu46988_Solutions-Enabler-Symmetrix-Migration-CLI-7.6-Product-Guide,  pls refer page 62 and pg 65 :

Page 62 :  Example 1: Preparing for data migration between Symmetrix  arrays and CLARiiON/VNX arrays - Same type of migration as the scenario as I asked

Page 65 :  Zoning and Lun Masking -

Because the Symmetrix "host" is connected to the Clariion/VNX array, it is necessary to

perform the following zoning and LUN masking to grant the Symmetrix FA initiators (ports)

access to the remote devices:

1. Zone the Symmetrix array to at least one Clariion/VNX array SPA and SPB port.

2. Register the Symmetrix FA ports manually for both the CLARiiON/VNX SPA and SPB

ports using the following initiator settings:

• Initiator Type: 3 (CLARiiON Open)

• Arraycommpath: 1

• Failover mode: Should be set to either 1 or 4.

Note: Failover mode 4 is supported starting with Enginuity version 5773.

• UnitSerialNumber: Array

3. From the Symmetrix array, create a storage group.   =========> Here as per guide, it tells to create SG on symm

4. Add the Symmetrix array control devices to the storage group.

5. Add the CLARiiON/VNX remote devices to the storage group.  ---> how to add VNX luns to VMAX SG ?

Also refer to the points 4 and 5

Could you please confirm this ?

You need to make sure that every FA that your device(s) are mapped to, needs to be zoned to VNX ports.  Once FAs are logged-in to your VNX, you register them and treat them as if they were a host.  This "vmax" host needs to be in a storage group that contains LUNs that will be used as target for hot-push.

1) correct

2) you don't need to create additional masking views. FA are doing all the work, as long as they can talk to target VNX SPs, you are ready to go.

3) you don't need to do that - your source devices are already member of storage group used by the host

4) you don't need to do that - your source devices are already member of storage group used by the host

5) on VNX you should have a storage group that contains your target LUNs and your "vmax" host.

Hi Dynamox

Thank you for the replies again.

Reg point 5 :  On VNX you should have a storage group that contains your target LUNs and your "vmax" host.

I assume this is not a pre-requisite for the OR Hot Push to work properly. Is that correct ?

I believe this is needed after the final cutover - so that our prod host will get connected to the target array once the complete OR migration gets over. (though zoning part will be done before the cutover and kept ready to keep the cutover time minimal)

VMAX FA ports need to be able to write to VNX device. The only way to do it is to place VMAX FA into a storage group with VNX LUNs.  How else can VMAX write to those devices.  So #5 is not optional.

Ok. So point 5 is the actual OR masking view that we create on the VNX for the Hot push to migrate data to VNX.

Once the cutover happens we can just remove the VMAX FA (that acts as Host) and connect our Prod host to the VNX Storage group.

Also a last query. In case of Hot Push, irrespective of any array we use as Remote, we should always create an OR Masking view only on the remote array. Correct ?

duriduri wrote: Ok. So point 5 is the actual OR masking view that we create on the VNX for the Hot push to migrate data to VNX. Once the cutover happens we can just remove the VMAX FA (that acts as Host) and connect our Prod host to the VNX Storage group.

you can do that or simply remove LUNs from the storage group used for OR into storage group used by the host (make sure to terminate OR session before you do that)

Also a last query. In case of Hot Push, irrespective of any array we use as Remote, we should always create an OR Masking view only on the remote array. Correct ?

well, no all arrays are supported with OR but if your target is VNX, VMAX , XtremIO  those are definitely supported.  Correct, you are pushing from VMAX to your target array so masking needs to be done on the target array only.  VMAX is the "host", it need to write to target array so it needs to have access to LUNs on target array.