Skip to main content

VRO Heroes Den

  • 42 Topics
  • 172 Comments
ertelle1
ertelle1Product Strategy
Training Materials to get started with Veeam Recovery Orchestrator

​Hello VRO Users! I wanted to share some helpful links to get you started with Veeam Recovery Orchestrator! Free Product Onboard Training at Veeam University: https://www.veeam.com/free-on-demand-trainings.html Under Product Onboarding→ Veeam Data Platform → Additional Products you can find helpful resources on all products including Orchestrator and Veeam One. For Orchestrator you can follow the modules for specific how to’s. Veeam Recovery Orchestrator - Veeam University Free Training from VMCE Technical Team (EMEA/AMER) guided walk through of Veeam Recovery Orchestrator with recorded videos, whiteboards, and knowledge check questions at the end. https://rise.articulate.com/share/nA5BBDTx-SUn41-s17e_yG1irX9PdTPG#/ Veeam Recovery Orchestrator Workshop Finally, we have Veeam Hands On Labs for Veeam Recovery Orchestrator! In this lab, you'll use Veeam Recovery Orchestrator in different scenarios to demonstrate how to automate testing and recover workloads. You'll also learn how to confi

88011
dloseke
ertelle1
ertelle1Product Strategy
Welcome to the VRO Heroes Den!

Welcome everyone to our VRO Group! I am so excited to get this group off the ground and start collaborating with not just our internal Veeamers but the Veeam community as well! Some housekeeping items before we get started. This is a community space, for users that are beginning their Orchestrator journey, in the middle of it, experts, or don't even know what it is. All questions are welcomed as myself and other SME's will be here to help guide you and support you in your BC/DR endeavors. I also want to use this space for collaboration, I love hearing what other's are doing with Veeam product's and going beyond the art of the possible with Orchestrator. Feel free to share any content as this page will be dedicated to learning! At times we may also ask for feedback on deployments, or challenges you may be facing so that we can align it with Product Strategy/Management to deliver better outcomes so keep your eyes out for those posts as well. To Start things off - I will create a new post

2672
leduardoserrano
MicoolPaul
MicoolPaul
Opinions on VRO Platform Support

Hi everyone, I’m not going to try and frame this as some dramatic, doomsday story for either VMware or VRO, but acknowledge the current market conditions. Backdrop for discussion We are all hearing stories of people abandoning VMware due to pricing concerns etc, and the increase in market fragmentation. Organisations scattering across jumping to Microsoft Hyper-V/Azure Stack, organisations embracing the cloud such as hyperscalers, organisations embracing OpenShift, Proxmox, KVM, XenServer etc. Source VM Workloads Now, we know that today Veeam supports Agent backups and vSphere backups as the source for a VRO recovery plan. Overall, this means that we don’t need to worry too much about backup source support because if it’s not vSphere, the source can be protected in-guest with an agent for now. Destination Compute Location This is where the core of this post comes in. Currently VRO supports restoring to vSphere or Azure. So if an organisation moves away from VMware, the only recovery lo

20411
E
S
spider32Experienced User
Unable to upgrade Veeam Orchestrator from v7.1.0.205 to v7.1.0278 to update built in VBR and VeeamOne to v12.2?

We are already on VDRO v7.1.0.205 with built-in VBR and VeeamOne still on v12.1. When I try to do an in-place upgrade, I got the message below. I did a separate upgrade of VBR and VeeamOne on a VDRO server before and ran into issues and learned that I should update through the VDRO patch. So what would be the recommended upgrade path to update the built-ins to address https://www.veeam.com/kb4649?

1157
nka
J
jsteindeerparkNew Here
Existing Environment and Adding Orchestrator

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!

795
matheusgiovanini
ertelle1
ertelle1Product Strategy
Veeam Recovery Orchestrator 7.2 - Available Now!

It’s Launch Day for Veeam Recovery Orchestrator! I am so excited for this latest release – which now includes support for Microsoft Hyper-V environments! There were two major focuses for 7.2: Support Recovery Plans for Microsoft Hyper-V Backups Support for Cross-platform recovery plans of vSphere backups to Microsoft Hyper-V environments Let’s start with #1 supported scenario first. The Orchestrator server must be connected to SCVMM servers only. Direct connections to Hyper-V hosts are not supported. Currently System Center Virtual Machine Manager (SCVMM) 2022 is supported & CSV storage registered in SCVMM. You can leverage SCVMM tags to help with management. Readiness checks are available to verify that RPO’s are met and recovery location resources are available and ready for use. Orchestrator will also leverage the malware flag detection in Veeam Backup & Replication to verify the restore points being leveraged for recovery are valid and not flagged for suspicion or malicious. After

2734
D
W
WestieDaveNew Here
Failover to Azure and re-IP of instances

We’re looking at building plans to failover into Azure and due to a number of firewall constraints with 3rd party services the ideal situation is to have the ability to re-IP the VMs stood up in Azure to match the IPs from their source host. Given the limitations in Azure with the vNET assigning dynamic IPs when the VM is stood up and that currently I can see no option in the VRO plan steps for Cloud to specifically to re-IP has anyone else either looked at, ideally, scripted options from the VRO or Azure side or have any experience (good or bad) to share about this. Obviously, we like to avoid a significant amount of “manual” re-IP work once a plan is executed and have VRO take care of the whole process end-to-end to reduce the potential for delay/errors in the process, so any use case scenarios would be greatly appreciated as to whether this is feasible at this time. Thanks in advance VR Heroes!

520
W
ravatheodor
ravatheodorVeeam MVP
Veeam Recovery Orchestrator and Linux Re-IP - Updated

Introduction How does it work? Prerequisites Configuration Conclusion Introduction In this blog post, tfewins introduces a great Linux re-IP script to use with your Veeam Recovery Orchestrator (VRO) environments. Since iteration is a good way to improve things, I’ve taken a shot at it and updated the script with a new feature. This feature uses Veeam Backup & Replication (VBR) re-IP functionality for replication jobs and CDP policies to keep re-IP network information. It transforms VBR into the IP Address Management (IPAM) for VRO scripts. How does it work? We need two scripts configured as custom steps in VRO. The first script (GetReIpRules.ps1) is new. It takes as input the currently processed VM name and connects to VBR to search for the re-IP rule. It actually searches for a replication job or CDP policy to which the processed VM is associated with. Once it finds it, it looks for the re-IP rule and exports the content to a JSON file. Script logic The second script (ReIpLinux.ps1),

991
Chris.Childerhose
tfewins
tfewinsVeeam MVP
Veeam Recovery Orchestrator and Linux Re-IP

Introduction Prerequisites Configuration Conclusion Introduction While working with Veeam customers recently who wanted to automate Linux re-IP as part of their recovery process using Veeam Recovery Orchestrator (VRO), I started into some exploration to see if I could leverage any existing scripts that could be easily modified to accomplish this. I put my Google Fu to work and found numerous Linux re-IP scripts available online. Several such scripts have been specifically designed to work with Veeam during recovery or failover scenarios. However, when I started building out my lab and testing with some of these, I discovered that the existing scripts either rely on methods specific to certain Linux distributions or employ outdated/deprecated techniques to accomplish the re-IP. Given the diversity of Linux distributions and network management tools, the exact method for re-IP can vary depending on the specific environment. My goal was to find a common method that would work for the fore

5617
tfewins
jb16wer
jb16werComes here often
VRO - Veeam Recovery Orchestrator V7.1 - Disaster! in Production a quick video of single-click restore to DR

In this video I show part of the Enterprise Recovery Orchestration On-Demand Lab where we simulate a complete outage of Production Site and failover Platinum, Gold & Silver services in 3 simple clicks to DR. Including Re-IP of my Gold Filer Server.

671
Chris.Childerhose
skitch210
skitch210Veeam MVP
Run a Recovery Plan from VBR after a Backup Job

I had a use case come up recently to run an Orchestrator Restore Plan right after the backup job completes. The idea is to have the VMs ready in vCenter in case of a disaster, so a minimal RTO but up to a 24-hour (or last backup) RPO. I started with writing the script and testing it out and got it to work as expected but found a few tips that I wanted to share. Script location: https://github.com/skitch210/veeam-orchestrator/tree/main/VRO-Run-Restore-Plan First, I use one vCenter to manage both Production and DR and the Restore plan was set to restore the VMs with the same name as in Production. This could cause confusion between running Production VMs and the restored VMs, so let’s adjust the Restore Plan to append something on the end on the name of the VM. To do this we need to Edit the Plan, Edit Steps for the VMs (must do per VM). Under Restore VM – Restored VM Name, edit the default value By default, the Parameter value is %source_machine_name%, this will make the restored VM the

341
Chris.Childerhose
skitch210
skitch210Veeam MVP
Recover to AHV

I started to work on this script soon after I setup my cluster in my lab. I will say this one has been a challenge, more so than AWS or GCP. It required an API and figuring out the right payload for multiple disks inside a VM and dynamically setting this up. Big thanks to Ronn Martin and Chris Arceneaux for their help and contributions to this effort. Script location here: https://github.com/VeeamHub/veeam-orchestrator/tree/main/RecoverToAHV This script is for demo purpose and should be used as a template to build off of for production environment. The script is setup to use Nutanix Prism single cluster and has limitations based on network and storage container. Also, the VM that is being restored can only have 1 storage controller type. Obviously, you need to have a Nutanix cluster, have it setup in Veeam BNR, and have a Nutanix proxy deployed. Let’s look at the script. First line takes a variable from Orchestrator – Source VM Name – and will use this throughout as the VM to restore i

1653
skitch210
waqasali
waqasaliInfluencer
VRO Works On GCP

How VRO works on GCP as supposed entire environment hosted on GCP.

464
waqasali
ertelle1
ertelle1Product Strategy
How To: Use Veeam Recovery Orchestrator for Clean Rooms!

First I want to give recognition for this script and setup to Senior Solutions Architect Claudio Fortuna! Thank you for your contribution. A new Orchestrator strategy for Security teams and DR teams alike! Organizations looking to scan their backups for malicious threats either before, during, or after an incident can now use Veeam Recovery Orchestrator (VRO) to scan backups from their copies, within an isolated environment. So how does this work? First, let’s talk about the architecture: organizations with a secondary environment or a true clean room (that is off the domain) can leverage Orchestrator and the embedded Veeam Backup & Replication (VBR) server to import and restore from backups or backup copies. With this scenario in mind if you were to lose the original backup server, the embedded backup server in Orchestrator can take control of the backups. To automate this process a script is included that will be part of the restore plan. A restore plan automates the recovery actions

9273
sajjad ali
S
spider32Experienced User
VDRO ver 7.1, Failover failing unable to find Distributed Virtual Portgroup.

VDRO ver 7.1, Failover failing unable to find Distributed Virtual Portgroup. We are no longer using DVPG in our environment but instead use logical switches in NSX-T. Building the recovery location shows that the Orchestrator can see the Logical switches but actual failover looks for DVPG instead of using the logical switches as defined in the recovery location. [Error] The Distributed Virtual Portgroup prod-10.111 was not found on the DatacenterDCDataCenter. Network Mapping shows the source network mapped to the target logical switch. BackupNetwork (ESDDataCenter) to prod-10.111 (vDS_NSX_Compute) What am I missing here? Why is VDRO looking for DVPG instead of the logical switch? This is causing the VM not to power on and not be connected to the network. Thanks again for your ideas.

505
S
skitch210
skitch210Veeam MVP
Veeam Backup For AWS Appliance Power On and Policy Run

As mentioned in my previous post -VRO Restore into AWS - https://community.veeam.com/vro-heroes-den-120/vro-restore-into-aws-custom-script-8341, the restore adds a tag to the restored VMs into AWS. This can be used to setup a protection policy in Veeam Backup for AWS and then we can use a script in VRO to power on the Backup Appliance so that our restored VMs will be protected. This script is located at: https://github.com/VeeamHub/veeam-orchestrator/tree/main/Start-VBAWS Looking at the script, it starts by getting the AWS account information from the CSV file. Next it will get the Veeam backup for AWS appliance EC2 instance ID based on the name of the instance. Then it will start the instance. It will wait in a loop until the instance state is running, and that is it. Pretty simple. But before you can use the script, the Veeam backup for AWS appliance needs to be deployed and setup. First thing is that a Veeam Backup for AWS appliance must be deployed into your AWS account. After the

311
Chris.Childerhose
skitch210
skitch210Veeam MVP
VRO Restore into AWS custom script

So, I wrote this script a while ago (supported on Veeam version 11 ), before there was a Veeam Community Hub to write about it. After seeing a few forums posts, I decided to revisit the script, make sure it still works as expected, make a few minor adjustments, and to do a writeup on how to set it up and use it. We can start by looking at the readme file in GitHub, https://github.com/VeeamHub/veeam-orchestrator/tree/main/RecoverToAWS As this states, be aware of the AWS Hardware compatibility compared to the VMs that you want to restore to avoid conflicts. Pay attention to the known issues and the requirements listed. Obviously, an AWS account and setup is necessary. I recommend going through the Restore to AWS feature in the Veeam console on the Veeam Backup Server. This will help you understand the information that is needed inside the script for the recovery to work. The script is setup to use a CSV file that has the AWS account information in it and imports these as variables throu

1985
Dynamic
B
bgteixeiraNew Here
VRO: Advanced Multi-Hosts

Hi everyone! Nice to be here, it’s my first interaction and I’m having some doutbs regarding virtual lab/data lab configuration with multi-hosts.I'm implementing VRO in a multi-host environment, but all my knowledge is based on single-host. We have 2 vCenters with 5 hosts each, one at the source and one at the target (DR), at different sites, and we’ll use virtual labs to test only on the target site (replicas and backup copies). Replication jobs have mapping and re-ip configured, because the production network at the primary site is (for example) 192.168.5.* and at the DR site it is 192.168.6.*. VL was configured in target production network (DR Site - 192.168.6.*) and same network was configured in the network mapping as well. VLAN ID we configured one which was not being used. The vDS selected was the one that have all networks available at the target site. There are no errors in virtual lab tests. 1st question: This configuration is good enough or I’m making some mistake here? 2nd

884
coolsport00
ertelle1
ertelle1Product Strategy
Veeam Recovery Orchestrator Vulnerability (CVE-2024-29855)

A vulnerability (CVE-2024-29855) in Veeam Recovery Orchestrator (VRO) version 7.0.0.337 allows an attacker to access the VRO web UI with administrative privileges. Note: The attacker must know the exact username and role of an account that has an active VRO UI access token to accomplish the hijack. The vulnerability discussed in this article was resolved starting in: Veeam Recovery Orchestrator 7.1.0.230 Veeam Recovery Orchestrator 7.0.0.379 https://www.veeam.com/kb4585

250
ertelle1
ertelle1
ertelle1Product Strategy
Orchestrator 7.1 is HERE!

Last week Veeam Released an update to Veeam 12.1 and I was excited to get my hands on it to update the lab with Veeam Recovery Orchestrator 7.1! It may be a small release but it sure is mighty! Starting off with my favorite update: A YARA rule tab in Orchestrator , which allows for YARA rule files to be managed by VRO. This is great for users that have multiple YARA Rule files and Veeam Backup servers, as orchestrator can control the rule assignments to different groups via scopes. You can also preview the YARA rules themselves which can come in handy for verification checks and versioning. YARA Rule Management Tab Next up is a small feature that came by way of request from a managed service provider I was assisting during their trial period; which is the ability to skip a specific vm within a plan from execution during DataLab Tests. For this user they wanted to avoid a penalty during their test for having an application online and getting hit with duplicated licensing fees. This allo

2093
dloseke
tim.myers
tim.myersComes here often
Veeam Recovery Orchestrator Overview Video

Welcome to “How to Tuesday!” In keeping with Emilee’s request for posting content for VRO...I said “Put me in coach!” I am sharing a video that we put together for a customer in preparation for a Veeam Recovery Orchestrator Consulting Engagement. It is a bit long, but for anyone that really wants an in-depth “How to get your head around Veeam Recovery Orchestrator”, I hope this one fills that void. I feel as though many people have this perception that “VRO is hard and complex”. If I can help others realize that VRO is NOT hard and complex, but a very valuable and important piece of the Data Protection strategy, then everybody wins. Hope you enjoy!

2537
T
jdtrier
jdtrierComes here often
VRO: Restore from Backup Copy, fundamentals and deployment considerations

The overall intent of this article is to consolidate major considerations when it comes to using Veeam Recovery Orchestrator to Recover from Backup Copies. Key: VBR: Veeam Backup & Replication VRO: Veeam Recovery Orchestrator Orchestrating recovery from Backup Copies - Use-Case Overview: Below you will see a is common customer design example. Both sites are Active/Active with production virtual workloads being protected with Backup Jobs as well as Backup Copy Jobs. (BCJ) (1) VBR server at Site-Z which is the DR location. Backup Proxy at each location. (1) Backup Repository for Primary Backups at each location. (1) Backup Repository for Backup Copies at each location. (1) vCenter at Site-Z and vSpheres cluster at each location. Agent deployed protecting a physical workload. Our Veeam Transport (Data Mover) service is represented by a (M) icon here for these machines. Our Agent services are represented by a (A), although the Agent Backup and the one on VBR server is an Orchestrator Agent

3233
Scott
jdtrier
jdtrierComes here often
VRO: DataLabs, Recovery Verification from Backups

The overall intent of this article is to consolidate major considerations when it comes to using Veeam Recovery Orchestrator to conduct Recovery Verification for Backups. Note: We will cover Backup Copies in another article, which is generally for recovery of VMs to another site during a critical site failure. Note: Given the length and depth of this article, I recommend clicking on the reference diagram for each section, right click and open image in new tab. That way you can have the image open while you read the content. Key: VBR: Veeam Backup & Replication VRO: Veeam Recovery Orchestrator Orchestrating recovery verification from Backups - Use-Case Overview: Below you will see a is common customer design example. This is a single site scenario, protecting local virtual workloads. (1) VBR server at Site-Z which is the DR location. Backup Proxy on location. Backup Repository on location. (1) vCenter at Site-A as well as single vSphere cluster. Our Veeam Transport (Data Mover) service

3262
Chris.Childerhose
S
SeanpNot a newbie anymore
Veeam Orch & Vsphere Network Mapping Rules

Hi, I’m wondering if anyone could help? I’m currently doing a PoC with Veeam Orchestrator. I have on-prem vsphere 7.0.3 and a Azure VM with Veeam Orch 7.0.0.337 installed. I’m trying to create a recovery location but cannot get past the network mappings. I can successfully see and add my “target network” (azure) but when I choose my source vSphere network, there are no options to select network. Vcenter is currently showing as connected in Veeam, I have used local SSO credentials as well as my domain credentials - both times status shows as connected but same outcome when selecting the source network. Has anyone seen anything similar or has any suggestions? Many Thanks!

604
Chris.Childerhose
skitch210
skitch210Veeam MVP
Tags, Categories, Business View, and Plan Groupings

As many know I am a big fan of VRO, I mean how can you not be? Orchestrated DR with automated testing and built in reporting. What is not to like about that? Something I have struggled with though is Groups in plans. By default, systems are grouped based on Veeam BNR jobs or vSphere datastores. What does this mean? Well, if I have 20 VMs in a backup job, those 20 come into VRO in a group based on that backup job. I can add this group to a recovery plan to be restored into another vSphere environment or a cloud recovery plan to Azure. But what if I want to recover 10 to another vSphere location and 10 to Azure? I could break the job in half so that I get 2 groups based on new backup jobs with 10 each. However, that may not be practical for my retention requirements, or just more administrative overhead. So how can we solve this problem? Glad you asked. Since VRO relies on the embedded VeeamOne, we can use vSphere tags or Business View Categories to group systems together. Let’s look at

1633
leduardoserrano

About this group

Welcome to the VRO Heroes Den!

This group is about collaboration and contributing to the Veeam Community focused on Veeam Recovery Orchestrator! This space will serve as an area to provide helpful insights for users just getting started with Orchestrator or already on their Orchestrator journey. Here you can find fundamental tips for developing BC/DR strategies and working with Veeam Recovery Orchestrator, as well as share feedback and ask questions to Veeam SME’s and product teams. 

Disclaimer 

Veeam is not responsible nor can be held accountable for the accuracy and usability for code samples published in the VRO Heroes Den.
All published scripts and code are licensed to you by the sample's author and you should not contact technical support to submit issues on the code.
The result of the script is your responsibility. Veeam nor the author can be held accountable for any loss of data.

Members

jorge.delacruz
mkevenaar
Cragdoo
Rick Vanover
AndreAtkinson
victorwu
Chris.Childerhose
wesmrt
coolsport00
MicoolPaul
regnor
tsmith
marco_s
JBuff
CPfleger
Tobias Gietz
keiranshelden
MattM
JHoughes
kirststoner12
Scott
AlecKing
JMeixner
dips
K
Shaokat
SteveHeart
Andanet
JNEAU
jos.maliepaard
+ 102
Terms & Conditions