Unsolved
This post is more than 5 years old
1 Message
0
1229
August 26th, 2019 07:00
RecoverPoint SE to MetroPoint
Hello everybody,
I have a customer with the following configuration:
Site1 (Prod): Unity 500 (RP/SE)
Site2 (DR): Unity 500 (RP/SE)
Now, third site (Site3) is gonna be added along with another Unity 500, to become new DR site. On Site1 and Site2 VPLEX will come to virtualize Unity 500 under them, to make Site1 and Site2 logically the new Primary site. RecoverPoint will get new EX licensing, in a MetroPoint configuration:
Site1 (Primary Prod): VPLEX + Unity 500 (RP/EX)
Site2 (Secondary Prod): VPLEX + Unity 500 (RP/EX)
Site3 (DR): Unity 500 (RP/EX)
So, from current replication of Unity volumes from Site1->Site2, there is gonna be replication of VPLEX ditributed volumes from Site1->Site3 and Site2->Site3 (MetroPoint topology).
There is also SRM over RecoverPoint that orchestrate the replication of vSphere datastores. SRM will perform the same function over RP in the new topology, so I would like to migrate data with as little distruption as possible.
My plan is the following:
1) Upgrade the current RecoverPoint System on sites 1,2 from RP/SE to RP/EX licensing. As RP on sites 1,2 by product type is classic, and only licensing is RP/SE, I suppose it would be enough to remove current RP/SE licenses and add temporary RP/EX licenses for Unity frame capacity ?
2) Install the new Unity and new RecoverPoint cluster on Site3, licensing RP/EX (permanent)
3) Install the new VPLEX on site 1, and add RP/EX permanent license (locked by VPLEX s/n) on top of temporary RP/EX license (locked by Unity s/n)
3) Install the new VPLEX on site 1, and add RP/EX permanent license (locked by VPLEX s/n) on top of temporary RP/EX license (locked by Unity s/n)
4) Connect Site1 to Site3, and Site2 to Site3, for a MetroPoint topology
***NOTE*** After this step RP clusters on sites 1,2 will have two arrays and two splitters attached (Unity and VPLEX each), and two RP/EX liecnses installed (one permanent tied to VPLEX s/n, other temporary tied to Unity s/n). Is this possible and supported ?
5) Create empty thin VPLEX distributed volumes that span sites 1,2. Create consistency groups identical to future RP CGs in MetrePoint. Add distributed volumes to this VPLEX CGs.
6) Create empty thin Unity volumes on Site3, that correspond the volumes created in previous step
7) Create Metro replication groups in RP system that replicate Site1->Site3 and Site2->Site3
***NOTE*** After this step there's gonna be two active RP replications. First of current production volumes on Unity, via current CGs, from Site1 to Site2. Second of the future VPLEX distibuted volumes on Sites 1,2 (in this step configured but without VMs) to Site3 (MetroPoint topology).
For every current CG:
- Stop SRM on current CGs
- Migrate VMs online via vSphere storage vMotion from current Unity 1,2 volumes to new VPLEX distributed volumes
- Set SRM over new RP CGs as orchestrator.
9) After migration finished, remove old Unity CGs, Unity splitter and tepmorary RP/EX linenses from Sites 1,2.
This makes sense? Any suggestions or objections to this plan?
Pictures added for clearer understanding.
Thanks in advance for any help!
rs77
Idan
3 Apprentice
•
675 Posts
0
October 27th, 2019 13:00
This plan sounds good, would also be recommended to perform repository migration from the current Unity LUN to a new VPLEX virtual volume.
It would also be advised to configure the MP CG and concluding the full sweep before performing the svMotion.