Disaster recovery orchestration for the Enterprise (formerly Veeam Availability Orchestrator)
Post Reply
Stabz
Veeam Legend
Posts: 170
Liked: 20 times
Joined: Apr 07, 2017 7:40 am
Full Name: Philippe DUPUIS
Contact:

Question regarding VRO isolation and vCenter dependency for DR plans

Post by Stabz »

Hi everyone,

I am planning to implement Veeam Recovery Orchestrator (VRO) for a Disaster Recovery scenario between two sites:

Site A (Production): VMware environment backed up by VBR to a Dell DataDomain.
Site B (Recovery/Clean Room): vSphere environment with a second DataDomain (Vault) receiving replicated data via native DataDomain replication.
In this setup, I intend to use the embedded VBR instance within VRO at Site B to import the replicated backups. However, I want to keep VRO as isolated as possible and I am reluctant to connect it to the production vCenter or the production VBR.

I have two specific questions regarding VRO (v13.0.1):

Inventory & Tag dependency: Since VRO requires an initial connection to the production vCenter to gather inventory and vSphere tags, what happens if tags are accidentally deleted on the production side and a synchronization occurs? Would this break the existing recovery plans?
Manual Backup Mapping: Is it possible to create a recovery plan by manually selecting VMs from the imported backups on the VRO embedded VBR, without any connection to the production vCenter/VBR?
Thanks in advance for your insights!
Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests