Hi All,
In VBR there is an option to backup the Veeam Configuration so all the config can be restored easily.
I cannot see a similar option in VRO? Is the only way to complete this by backing up the VRO Database? If thats the case is this the correct document for the process to follow so we can backup all the plans etc we have configured?
https://www.veeam.com/kb1471
Thanks,
-
- Influencer
- Posts: 11
- Liked: 1 time
- Joined: May 28, 2019 3:05 pm
- Full Name: mjm599
- Contact:
-
- VP, Product Management
- Posts: 1526
- Liked: 402 times
- Joined: Jan 01, 2006 1:01 am
- Location: Prague, CZ
- Contact:
Re: How to backup Veeam Recovery Orchestrator Configuration
Hello,
That's correct, currently the best method is to back up all the databases deployed by a VRO server installation - there are three - VAO, VeeamONE (embedded) and VeeamBackup (embedded)
VAO is the Orchestrator database, and the 'embedded' VeeamBackup and VeeamONE are full-featured installations, and should be backed-up and restored as such.
Protecting these databases will protect all your plans and associated configuration (infrastructure connections, recovery locations, etc)
We are working on more granular recovery options for VRO, including plan export/import, separate database for reports, and so on. If you have specific recovery scenarios in mind please post your requests here, thanks!
That's correct, currently the best method is to back up all the databases deployed by a VRO server installation - there are three - VAO, VeeamONE (embedded) and VeeamBackup (embedded)
VAO is the Orchestrator database, and the 'embedded' VeeamBackup and VeeamONE are full-featured installations, and should be backed-up and restored as such.
Protecting these databases will protect all your plans and associated configuration (infrastructure connections, recovery locations, etc)
We are working on more granular recovery options for VRO, including plan export/import, separate database for reports, and so on. If you have specific recovery scenarios in mind please post your requests here, thanks!
-
- Influencer
- Posts: 11
- Liked: 1 time
- Joined: May 28, 2019 3:05 pm
- Full Name: mjm599
- Contact:
Re: How to backup Veeam Recovery Orchestrator Configuration
Hi Alec, thanks for the reply. Ok so its the database backup needed at the moment and no built in GUI Config backup like VBR.
That brings me onto another question. The deployment in place consists of:
- VM1 = VBR VM
- VM2 = VeeamOne and Veeam Enterprise Manager VM
So we already have VeeamOne in use and setup etc. We are now looking to move onto VRO and deploy that however i know that as VeeamOne is closely tied to VRO, there is an 'embedded' VeeamOne as part of VRO.
1. From what i can see we have an issue here as currently its only possible to use the VRO VeeamOne 'embedded option?
2. There is no option yet to deploy VRO and select to connect to existing VeeamOne deployment?
This link detailed that its on the roadmap: veeam-recovery-orchestrator-f50/veeam-o ... 92883.html
3. So if its correct that we need to use the 'embedded' VeeamOne as part of VRO deployment, what happens to the existing VeeamOne we have setup?
Thanks,
That brings me onto another question. The deployment in place consists of:
- VM1 = VBR VM
- VM2 = VeeamOne and Veeam Enterprise Manager VM
So we already have VeeamOne in use and setup etc. We are now looking to move onto VRO and deploy that however i know that as VeeamOne is closely tied to VRO, there is an 'embedded' VeeamOne as part of VRO.
1. From what i can see we have an issue here as currently its only possible to use the VRO VeeamOne 'embedded option?
2. There is no option yet to deploy VRO and select to connect to existing VeeamOne deployment?
This link detailed that its on the roadmap: veeam-recovery-orchestrator-f50/veeam-o ... 92883.html
3. So if its correct that we need to use the 'embedded' VeeamOne as part of VRO deployment, what happens to the existing VeeamOne we have setup?
Thanks,
-
- VP, Product Management
- Posts: 1526
- Liked: 402 times
- Joined: Jan 01, 2006 1:01 am
- Location: Prague, CZ
- Contact:
Re: How to backup Veeam Recovery Orchestrator Configuration
Hi!
Regarding deployment, you don't need to worry about the 'embedded' ONE on the VRO server. It will be installed and automatically configured by VRO; and you don't need to make any modifications to your existing ONE server.
VRO will use the embedded ONE only for the data collection required to build and run recovery plans.
When installing the VRO server, just use the same single license file you have which covers VBR, ONE and now VRO (probably a VDP-Premium license?)
Regarding the roadmap, because of the differing roles and architecture of ONE versus VRO, we will transition VRO to it's own internal data collection methods for better latency and scalability. Eventually the embedded ONE will no longer be required. However this is a long-term plan, and the change will probably be rolled out gradually over several version updates.
Hope that helps, any further questions let us know,
Thanks!
Regarding deployment, you don't need to worry about the 'embedded' ONE on the VRO server. It will be installed and automatically configured by VRO; and you don't need to make any modifications to your existing ONE server.
VRO will use the embedded ONE only for the data collection required to build and run recovery plans.
When installing the VRO server, just use the same single license file you have which covers VBR, ONE and now VRO (probably a VDP-Premium license?)
Regarding the roadmap, because of the differing roles and architecture of ONE versus VRO, we will transition VRO to it's own internal data collection methods for better latency and scalability. Eventually the embedded ONE will no longer be required. However this is a long-term plan, and the change will probably be rolled out gradually over several version updates.
Hope that helps, any further questions let us know,
Thanks!
Alec King
Vice President, Product Management
Veeam Software
Vice President, Product Management
Veeam Software
Who is online
Users browsing this forum: No registered users and 2 guests