Skip to main content
  • EN

 hi all….

I have question about VRO and VBR placement

For DR to cloud part, I refer to the architecture below

However, what if I need to cater both backup and DR to cloud simultaneously?

 

 

Our customer is having on-prem VBR server, all jobs and policy are running on-prem.

While they want to explore the possibility of DR to Azure, in case the production site is down, when on-prem VBR server is gone

While the VBR server on Azure does not have any data, the failover seems can’t be success

 

Any workaround for this scenario?

 

 

That is why they recommend the VBR be in the DR site as pictured for the best chance of failover.  You can always work around this but it is much more work versus following the best practice.

​@GoldenTree what you mean with “ While the VBR server on Azure does not have any data, the failover seems can’t be success “?

 

Not sure what you mean by “VBR server on Azure does not have any data”.  Having the VBR server out of the primary compute environment is essential as it’s pretty difficult to recover in DR when you don’t have the server to recover with.  When possible, all of my environments have the VBR server in the recovery environment rather than the primary environment for this reason.  This applies to no only cloud targets, but also on-premise targets such as having multiple on-premise sites - the target location doesn’t matter - I need that VBR (and Orchestrator) server to survive, as well as vCenter since I’m nearly always utilizing VMware environments.

Comment


Terms & Conditions