VMCE Practice Question - 05 October 2024

A: You want your Manager that connects into the engine to maintain visibility. 

c. first upgrade Veeam Backup Enterprise Manager > second upgrade Veeam Backup & Replication > third upgrade Veeam ONE > and fourth upgrade Veeam Recovery Orchestrator

c. first upgrade Veeam Backup Enterprise Manager > second upgrade Veeam Backup & Replication > third upgrade Veeam ONE > and fourth upgrade Veeam Recovery Orchestrator

1. VRO → VeeamONE → VEM → VBR

c. first upgrade Veeam Backup Enterprise Manager > second upgrade Veeam Backup & Replication > third upgrade Veeam ONE > and fourth upgrade Veeam Recovery Orchestrator

A

Option C

I will start with upgrade enterprise manager first and next VBR next Veeam One

According to Veeam documentation the correct order is: VONE, Veeam Enterprise Manager, Veeam Recovery Orchestrator and finally Veeam Backup and Replication.

However, the answer - B - is valid if you are already on VRO 7.0. Since this isn’t specified in the question, lets assume we’re on VRO 7.0 and we can upgrade VRO last.

https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr_byb.html?ver=120#integration-with-veeam-management-and-monitoring-products

In a regular environment without Orchestrator the order would be Veeam ONE, Enterprise Manager and in the last step Backup & Replication. Also mentioned here (in Step #3): https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr_byb.html?ver=120#integration-with-veeam-management-and-monitoring-products

Are you using Veeam Backup Enterprise Manager server added to Veeam ONE? If yes, first upgrade Veeam ONE, second upgrade Veeam Backup Enterprise Manager, and third upgrade Veeam Backup & Replication.

My reminder here is, start as you count, with ONE... after that remember: your Enterprise Manager is connected to your VBR Systems, so this system is aware of all VBRs, so upgrade the Enterprise Manager in the second stage. After that, proceed with the upgrade of VBR.

• I made the mistake earlier, a few years back, and upgraded to VBR and VBEM first. Then we had connection problems between VBR/VBEM and ONE. Fortunately, the support team was able to help.

With the Orchestrator in place (and this system has also an embedded ONE and VBR by design), in my opinion the documents are a bit vague (in Step #5):

https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr_byb.html?ver=120#integration-with-veeam-management-and-monitoring-products

...Veeam Recovery Orchestrator 7.0 — with Veeam Backup & Replication 12, 12.1 and 12.2. If necessary, upgrade Veeam Recovery Orchestrator before upgrading to Veeam Backup & Replication 12.2.

As this question from me was a bit confusing - and please forgive me Tyler and all, i didn't mentioned the Orchestrator version. I would also agree with Tylers statement from his perspective  - so meanwhile i reached out also to support to check this:

--

Feedback from Support: “The only restriction for Orchestrator is that it be upgraded prior to the VBR Server.  I would recommend you go VONE > VBEM > VBR.  You can do VRO before VBR or before VONE.  Your call on that one.”

--

So the only possible solution in that case, is answer A: first upgrade Veeam Recovery Orchestrator > second upgrade Veeam ONE > third upgrade Veeam Backup Enterprise Manager > and fourth upgrade Veeam Backup & Replication

more details here:

https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr_byb.html?ver=120#integration-with-veeam-management-and-monitoring-products

https://helpcenter.veeam.com/docs/vro/userguide/upgrading_vro.html?ver=70

Side note, if your VBR is also connected to an external Cloud Connect Provider - this site has to be upgraded first (so i would recommend to speak with them). But the setup/update wizard should also display a warning message about this external connection.

Please bear with me: I will try to provide a clearer task for a possible next question.

I’ll say B. …. or D. 🤷🏻‍♂️😂

Thanks for the post Markus. Think I’ll try to be back next week...or travel (Berlin) week 😏