Solved!
Go to SolutionRP4VM disaster case
hello,
we use RP4VM 5.3 and all works well. Ich have a few questions in case of disaster:
We have 2 Sites. Each Site has its own ESX Cluster and Storage System. Both Sites use the same vCenter hosted on a third Site.
- What would happen if the primary Site goes complete down and the VMs and RPAs on the productive Site are not reachable? Can I nevertheless failover?
- What would happen if the primary Site is repaired and comes up again? Would RP4VM declare them due to failover as copy?
- If the primary site goes down. Is there a way to failover all protected vms with simply one task and without the testing procedure? Like a disaster button?
Best reguards,
Matthias
DELL-Sam L
Community Manager
•
8061 Posts
•
34395 Points
1385
0
Posted October 23rd, 2020 16:00
Sprinklr Case#6459000 Hello Matthias,
What Hardware are you using?
DELL-Josh Cr
Community Manager
•
9700 Posts
•
43747 Points
1315
0
Posted November 2nd, 2020 09:00
Hi,
Sorry for the delay. This thread has some good information https://dell.to/2HY7jI4
Page 48 https://dell.to/2TL1rov
Idan
4 Apprentice
•
675 Posts
1256
1
Posted November 16th, 2020 00:00
Hi @mfu,
1. Yes, you can certainly failover/test using the target side vRPAs using the plugin on the other vCenter
2. RP4VMs would try to replicate back upon failover and would auto-replicate once the prod site goes back up again. You can pause transfer upon failover to prevent that transfer as needed
3. You can certainly create a group set with all CGs and then perform a failover against that group set, it's highly recommended to test and make sure the PiT (Point-in-Time) is valid and move backwards/forward in time until the right PiT is selected and then failover to it. Once failover commences, there is no option to pick a different PiT