We currently have B&R backing up our production site and storing the data on a backup appliance and then using B&R make a backup copy over to a second backup appliance located at what will be our DR site.
What would be the correct deployment?
From what I read we should have Orchestrator setup in DR which makes complete sense. Do we leave our existing B&R the way it is today in our production site or would we need to make some changes there as well?
Thank you!
+20Hi
Thank you.
+21Check out this post here in the community as it is really great for information - https://community.veeam.com/vro-heroes-den-120/how-to-prep-for-veeam-recovery-orchestrator-6890
Orchestrator is great for automating your DR testing, but it’s not required in order to restore backups at your DR site. You can always do Instant Recovery from those backups. For Orchestrator, you will need to first install and configure VeeamONE.
+3Best practices dictate that you should have your Veeam server in the DR environment. Logically it makes sense in that if your production site is lost, your Veeam server is still fully functional and readily available. The same goes for VRO.
I think it would be worthwhile to move your Veeam server to the DR site, and set up all the necessary gateways, proxies, mount servers, etc.
+5Your current setup with Veeam Backup & Replication and backup copies to the DR site is a solid approach.
Yes, Orchestrator should be in DR, as it simplifies and automates recovery. You can keep your existing Veeam server in production, but adding a secondary VB&R server in DR can improve recovery times by allowing local restores.
It all depends on your recovery goals—are you focusing on full-site failover or just individual VM recovery?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
