Simplivity RapidDR replication

[Jpe_bastias]

Hi everyone, I needd to know how Simplivity RapidDR replicate the vm from one site to another.

I tried to create a Recovery-Plan, but I need first to generate the seed on the remote site. (making an analogy with Vmware SRM)

I have this error when test the recovery plan

Unable to locate backup(s) for VM "VM-NAME" The diagnostic is : Check if any
backups exist for the virtual machine. Use 'Backup VMs and recover' option to create backup for the VM

your assistance, please.

[Aditya_A]

Hi,

RapidDR works on SimpliVity backups.
You must first have remote backups using backup policy or SimpliVity plugin in place so that RapidDR may work using those backups when failover is executed and then the VMs quickly spawn using the latest backup or your preference.
The backup must be in protected state and atleast 10 mins old in order to be used by RapidDR.
Please check this doc: https://www.hpe.com/psnow/doc/a00105770en_us
This user guides talks about the entire process in detail.

[Jpe_bastias]

Ok thks,

so should I have the vCenter servers configured in linked mode before setting up these backups?

[Jpe_bastias]

so should I have the vCenter servers configured in linked mode before setting up these backups?

[Aditya_A]

If your SimpliVity clusters are spanned across multiple vCenters then you need to have the vCenters linked, with HPE SimpliVity Plug-in installed on each vCenter. Once these steps are in place then you can follow the user guide and create policies and datastores for RapidDR exclusively.

[Aditya_A]

Please let me know if you have further queries.

[Jpe_bastias]

@Aditya_A 

Thank you very much.

I'm still facing the issue, and I can't execute the recovery plan. From what I read in the documentation, I need to create a Backup policy for RapidDR and store it on the remote site. However, when I create it, I can't see the remote site's cluster. I'm not sure how to view the Remote Site Cluster.

[Aditya_A]

Hi,
I'd recommend opening a support case regarding this issue.
Ideally all clusters in the federation shall be available when you configure a backup policy. It could be something as simple as MTU mismatch or something that may require troubleshooting.