SANCOPY Giving Error

When we start SAN Copy from VNX5400 (PULL Method) it does not give any Error and copy gets completed successfully,

But when we start the SAN copy from AX4-5 System (Push Method) it gives above error .

As downtime required is more in Pull Method, we want to go for Push Method, which will give us Incremental Copy option to reduce the migration time.

Can anyone help to get SANCOPY(Push Method) working on AX4-5?

Hi Ashish,

Can you please verify these things once again :

Have you installed SAN Copy enabler on Clariion system? Clariion SAN Copy software on Clariion in push-based too.

Make sure that they have to be in the same Domain, if not in the same domain, System will not be able to reach to destination. SAN Copy Sessions are limited to be 4/SP for this model.

You should have less than 10 TB of data at Clariion end and less than 20 Attached hosts to it, if the values are greater involve EMC CE.

1) Add the VNX to Clariion Storage Group

2) Zone your Clariion to VNX.

3) From Replicas > Update SAN Copy Connections

4) Select Source & Destination LUNs. They have to be of same size. RAID types may differ.

5) Connect the Source LUN (Clariion) and destination LUN (VNX) to Storage Group on Unisphere (VNX)

6) Connect your Clariion Port to the same Storage Group (where source & destination LUNs are grouped). If port/zone is not visible select Advanced tab on Unisphere.

7) Add the LUNs to Reserved LUN Pool on Clariion (because of incremental copy).RLP can be smaller. Each source LUN should have one RLP LUN.

8) Configure the RLP on VNX (Replicas> Configure Reserved LUN Pool).

Now from VNX end, Click on SAN Copy Wizard, select Clariion system. Select the LUN/LUNs.

9) If Destination Storage system is not visible enter destination LUN WWN only.

10) Slect Link Bandwidth and Throtle Value.

You can verify zoning once again. It should work..

Now SANCOPY PUSH with FULL and Incremental is working :

Followed below Steps :

1) Got SANCOPY Enabler license installed on AX4-5

2) Did the zoning of SPA(AX) to SPA(VNX) and SPB(AX) to SPB(VNX)

3) Created same number of RLP (Reserved Pool LUN) on AX system as total Migration LUNs count

4) As in our environment AX was not visible as SANCOPY Connection, we manually registered it as a Host.

5) Created New Storage group called SANCOPY and shown all Destination LUNs of VNX5400 to it.

6) Added the AX4-5 System in the Console of VNX5400 with the help of Multidomain Configuration (This allowed us to see the source and destination properly, without using WWN numbers of LUN)

7) Created SANCOPY Incremental Sessions for Each LUN

Thanks everyone for giving valuable inputs.

Sounds great...good job..