Disaster recovery orchestration for the Enterprise (formerly Veeam Availability Orchestrator)
Post Reply
nunciate
Veteran
Posts: 260
Liked: 41 times
Joined: May 21, 2013 9:08 pm
Full Name: Alan Wells
Contact:

New VRO Install

Post by nunciate »

Well, I finally got my license upgraded and now I have VRO installed on a new VM. My existing servers consist of a single B&R VM server in my DR location. This server contains all the backup jobs for prod, replications jobs to DR, and backup jobs for DR. I also have a Veeam Enterprise Manager on a VM in my prod DC. Finally, I have an existing Veeam One install on a VM also in the prod DC.

The new VRO VM is installed in the DR DC alongside the B&R server. I noticed it installed B&R and Veeam One on that same box but I don't want to use those. During the initial config, I was able to add my existing B&R server as well as my prod and DR VMware environments. I am a bit confused about what I am seeing in the console now.

Under inventory, I see groups were created for each of my B&R jobs as well as each of the data stores in my VMware environments. In those groups are all of the VM.
Additionally, I don't understand any of the Veeam One connectivity. Can I point this at my existing Veeam One environment?

I'd like to create custom groups of VMs so that I can build out recovery plans properly. Currently, the only groups I can point to are the ones it auto-created and that won't work well for me.
I read some posts about using Veeam One to group VMs based on VM tags so that might work for me but again, I am pointing at the local install from what I can tell and not my existing Veeam One environment.
Is there another way to create custom groups of VMs?
Alec King
VP, Product Management
Posts: 1497
Liked: 385 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: New VRO Install

Post by Alec King »

Hi there, glad you are up and running!
Your configuration is correct as far as I can see; you have all relevant B&R servers and vCenters connected.
Currently you cannot connect your existing ONE to VRO - it will always use the embedded onboard version. However the feature to use an external ONE server is on the roadmap.

The inventory groups you see now in VRO (per-datastore and per-B&R job) are defaults that we create when infrastructure is connected.
To create your own custom groups, just use the vCenter UI to tag some VMs. The embedded ONE on VRO server is already out-of-box configured to collect vSphere tags for VMs and create groups for them. The groups will be named "Category - Tag".
After the embedded ONE has collected all the tags you will see the new groups in VRO for use in plans.

Note - if you create new tags in vSphere they can take some time to show up in VRO. To force an update go to the ONE Web Client on the VRO server and manually Start the data collection task.

Hope that helps, let us know how it goes!
nunciate
Veteran
Posts: 260
Liked: 41 times
Joined: May 21, 2013 9:08 pm
Full Name: Alan Wells
Contact:

Re: New VRO Install

Post by nunciate »

Great, thanks for the quick response. I'll start tagging my VM and see how it goes.
nunciate
Veteran
Posts: 260
Liked: 41 times
Joined: May 21, 2013 9:08 pm
Full Name: Alan Wells
Contact:

Re: New VRO Install

Post by nunciate » 1 person likes this post

Confirmed creating tags and categories for my VM and running the data collection again did bring in the new groups. Perfect! Not to test some failover.

Thanks again,
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests