Re: RecoverPoint Licenses

Hi there,

Yes, you’ll need an EX or CL license as SE is limited to 2 clusters and one array per cluster.

Also, if the installation type is SE (when there are VNX arrays), then conversion using Deployment Manager to RP classic would be required before the license is changed.

Hope that helps,

Idan Kentor

Sr. Principal Product Technology Engineer – RecoverPoint and RecoverPoint for VMs

@IdanKentor

idan.kentor@emc.com

Related:

RecoverPoint: ERROR: Cluster xxxxx is a candidate to change its security level

Article Number: 501450 Article Version: 3 Article Type: Break Fix



RecoverPoint for Virtual Machines,RecoverPoint,RecoverPoint CL 4.4,RecoverPoint CL 5.0,RecoverPoint EX 4.4,RecoverPoint EX 5.0,RecoverPoint EX 5.1,RecoverPoint CL 5.1,RecoverPoint SE 4.4,RecoverPoint SE 5.0,RecoverPoint SE 5.1

System Poblems:

ERROR: Cluster vRPA1 is a candidate to change its security level. If this message appears for a long time, the security level change process may have failed because of a configuration error, a network problem, or because the cluster does not recognize a security certificate of another cluster. Verify the cluster configuration, network connections, and that the clusters recognize the security certificates of other clusters.

Clusters problems:

 vRPA2: RPAs: WARNING: States of all RPAs are unknown WARNING: LAN connection between all RPAs is unknown WARNING: Fiber connection between all RPAs is unknown Volumes: WARNING: States of all devices are unknown Splitters: WARNING: States of all splitters are unknown vRPA1: RPAs: OK Volumes: OK Splitters: OKWANs problems: [vRPA1 - vRPA2]: Items: WARNING: No remote communication between clusters in the system 

The system is trying to set the security level, and one or more RPAs fail.

Due to different security levels clusters fails to communicate.

Workaround:

Run the following script on all RPAs to see if any of them has a different security level:

Boxmgmt -> [2] Setup -> [8] Advanced options -> [4] Run script 
NDRjZTlhY2E4MjM2YjNlMjZiNmY1N2NlMjFmOTAzMmYKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVkClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjUwMTQ1MApHZXQgY3VycmVudCBuZXR3b3JrIHNlY3VyaXR5IGxldmVsCk5pdgojIS9iaW4vc2gKY2F0IC9ob21lL2tvcy9uZXR3b3JrU2VjdXJpdHlMZXZlbC50eHQKZXhpdAo= 
#

The output is:

1

Note regarding results:

0 = SECURITY_LEVEL_NON_SECURE

1 = SECURITY_LEVEL_AUTHENTICATE

2 = SECURITY_LEVEL_ENCRYPT

100/101/102 = Temporary state – Change is being attempted

Reboot the RPA that is different than the others, or has a temporary state (anything other than 0/1/2 )

Boxmgmt -> [5] Shutdown / Reboot operations -> [1] Reboot RPA

Related:

Re: RecoverPoint multi site configuration

Hello,

It is possible to connect three RPA clusters on three different sites?, as the following image shows:RPAs.JPG.jpg

All RPAs clusters are running version 4.0

We want to replicate LUNs on the following way:

SITE A -> SITE B

SITE A -> SITE C

SITE B -> SITE A

SITE B -> SITE C

SITE C -> SITE A

SITE C -> SITE B

Anybody has implemented a similar configuration?

If this is not possible, another option could be the following:

RPAs.JPG.jpg

SITE A -> SITE B

SITE A -> SITE C

SITE B -> SITE A

SITE C -> SITE A

Any suggestions are welcome.

Thank you!

Related:

  • No Related Posts

Re: RecoverPoint for Migration over FC

My Customer has an existing vblock at site A. it’s currently replicating to site B, using RecoverPoint over WAN.

Site A: (Cluster 1) site B: (Cluster 2)

VMAX40K (vBlock) — 5 x RPAs Gen5 ======>> 5 x RPAs Gen5 – Vplex — VMAX3 AFA

They just bought new VMAX AFA recent at site A, and new RPAs for both sites. And the target config is as below, over WAN as well.

Site A: (Cluster 3) site B: (Cluster 4)

VMAX3 AFA (vBlock) — Vplex —- 4 x RPAs Gen6 ======>> 4 x RPAs Gen6 — Vplex — VMAX3 AFA

For migration purpose, we want to leverage RP between the Cluster 1 & Cluster 3 over FC. Generally we need to put all cluster 1 FC ports and all cluster 3 FC ports in the same zone. The challenge in this environment is RPAs in Cluster 1 & 3 are on separated vBlock MDS fabrics, so we cant zone them together directly.

The option we are thinking is to connect half of Cluster 1 RPA ports to Cluster 3 RPA fabric. That means half of RPA ports are used for local splitting/journaling, and the other half dedicated for remote replication. Does that sound like a viable solution? if not, what other options we have? Thanks in advance.

Related:

Isilon-migrating SyncIQ production site to another

Hi All, Has anyone migrated a SyncIQ primary cluster to another before? IHAC who is planning to migrate one of their DC to another location. They have a cluster in this DC which is doing bi-directional SyncIQ with another cluster at another site. For the easiness of the discussion, I would call these sites with A, B and C. So the current setup is Site A and Site B is replicating to each other and the plan is to migrate Site B to Site C and Site B cluster is going away. As part of the planning, Site C cluster will hold an identical configuration as that of the Site B cluster.

Now, no challenges for the policies that are replicating from Site A to Site B today. We will create policies between Site A and Site C and once they are in Sync, will break the relation between Site A and Site B and continue with Site A & C. But what I need to confirm is about the policies that are replicating from Site B to Site A.

So this is how I think how they can be planned.

1. Setup policies to replicate them from Site B to Site C and then replicate from Site C to Site A at a different time (This is the only way SyncIQ can do a cascade mode to my knowledge? and I will use a new target Directory on Site A. Not the one that Site B is replicating today)

2. Failover Site B to Site C to make Site C R/W and point the users to Site C.

3. Break the relationship of Site B with Site A and Site C and remove all the policies on Site B. Cleanup and remove the old target directories in Site A that was used by Site B replications earlier.

Anyone who has dealt with any similar case in the past, please help with your thoughts if this approach is fine or if there is anything that we are missing on this. Appreciate your help. Thank You.

Regards

Sujith Kumar

Related:

  • No Related Posts

RecoverPoint for Migration over FC

My Customer has an existing vblock at site A. it’s currently replicating to site B, using RecoverPoint over WAN.

Site A: (Cluster 1) site B: (Cluster 2)

VMAX40K (vBlock) — 5 x RPAs Gen5 ======>> 5 x RPAs Gen5 – Vplex — VMAX3 AFA

They just bought new VMAX AFA recent at site A, and new RPAs for both sites. And the target config is as below, over WAN as well.

Site A: (Cluster 3) site B: (Cluster 4)

VMAX3 AFA (vBlock) — Vplex —- 4 x RPAs Gen6 ======>> 4 x RPAs Gen6 — Vplex — VMAX3 AFA

For migration purpose, we want to leverage RP between the Cluster 1 & Cluster 3 over FC. Generally we need to put all cluster 1 FC ports and all cluster 3 FC ports in the same zone. The challenge in this environment is RPAs in Cluster 1 & 3 are on separated vBlock MDS fabrics, so we cant zone them together directly.

The option we are thinking is to connect half of Cluster 1 RPA ports to Cluster 3 RPA fabric. That means half of RPA ports are used for local splitting/journaling, and the other half dedicated for remote replication. Does that sound like a viable solution? if not, what other options we have? Thanks in advance.

Related: