Is there a smaller VBR update file and smoother VBR update process ?

Hello @adrian.yhy ,

I am not quite sure if I get your point correctly. Under normal conditions you have a checkbox in the update process to update all components. With all the components like proxys, repositorries, etc. are updated at the first start of the Veeam console.

Please see the checkbox “Update remote components automatically” in step 4 of the  server update process.

https://helpcenter.veeam.com/docs/backup/hyperv/upgrade_vbr_upgrade.html?ver=120

Enterprise Manager is a separate update  process and Veeam Consoles on other systems than the Veeam server, too.

But it seems that checkbox does not work…..coz if do not like edit surebackup jobs or edit the WAN accelerator, they sometimes will give errors on the next run….then if you edit these as mention in main posts, you can see the first time after “finish” editing, there will be an updating those components as part of the “finish” process.

If you happen to edit it a second time after, you will not see the “updating process” when you click “finish” for some of these items. Like for backup repository, the updating process is always there.

@adrian.yhy -

What Jochen shared is the way to update other components manually. If that box is not checked, there is an upgrade wizard window upon opening the Veeam Console to prompt you to upgrade the other components. If you didn’t or or not seeing this….if you indeed did not have the ‘automatic uprade component’ option checked, then I recommend to reach out to Veeam Support.

Best.

If I understand you correctly, you mean how you can automate/bypass the process of re-clicking through e.g. the Virtual Lab after the components have been updated.

I know the problem myself, that without clicking through again, problems can sometimes occur. However, so far I have only experienced this with the V-Lab, not with the other components mentioned.
With the Virtual Lab, the configuration is not stored on the VBR server, but on the Virtual Lab Proxy VM and this must first be supplied with the new configuration after the update.

Unfortunately, as far as I know, there is no other way to solve this than to click through the configuration of V-Lab.

If your VBR, Enterprise Manager, One and VBO are virtualised, upload the ISO to the VMware Datastore and simply map it to the servers and run the update directly from the virtual CD drive. Then you don't have to copy the data multiple times.

But why would you have several VBR servers on the same site ? Although this may be for another topic, do we actually need 1 VBR server per ESXi host (this was what my vendor did the implementation but I changed it) ?

I have 3 sites (4 ESXi + 1 standby), (1 ESXi + 1 standby) & (1 ESXi + 1 standby). The remote sites literally only have VBR server & a Cashier_Server (Uses applications with Oracle and Windows Server 2022). They also acts as a backup & DR site for HQ. So I end up setting up 3 VBR servers instead of 9 VBR servers ?

I have 3 VBR servers but 1 main VBR server and 2 VBR “Proxy” & “Veeam WAN accelerator” for remote sites. So the headache is to transfer the VBR update files to the 2 remote servers and update from the VBR “Windows Server 2019” VMs.

There are no smaller vbr update file you have to go support portal and download the iso file mount to vbr and start updating process.

Is there specific tell us I'll share my experience here regarding updating procedures.

I never wrote that you need multiple VBR servers. I wrote that if the applications like VBR, ONE, Enterprise Manager,... run on separate servers (best practice), then this would be a plausible way to put the ISO on the datastore and then mount it, instead of copying it multiple times.

You do not need one VBR per ESXi host. Depending on the setup (e.g. with VSAN) possibly a proxy, but not a separate VBR. Theoretically, one VBR is sufficient for several locations. Advanced Deployment - User Guide for VMware vSphere.

I think you have a confusion of names here.
To understand what the VBR server does: It is the management. It coordinates the jobs, schedulers, components…
Backup Server - User Guide for VMware vSphere

A proxy does the following: The proxy processes jobs and delivers backup traffic (Retrieving VM data from the production storage, Compressing, Deduplicating, Encrypting, Sending it to the backup repository)
VMware Backup Proxies - User Guide for VMware vSphere

As you write below, the setup would fit. One VBR server at HQ and one proxy and WAN Accelorator per remote site.

I don't quite understand your problem right now. The transfer of the update files should be done by the component update of Veeam after the upgrade of your VBR server.
And no, unfortunately there are no smaller update files.

Sorry if I had misunderstooded as only 1 copy of the updater is needed right ?

So for faster usage of the ISO (on any of the locations), instead of mounting the ISO file to the OS, I just copy out the contents and use it as a folder. Then when I transfer the updater from one VBR server to another, I just transfer the folder.

I am not confused as I have a VBR server at each location (also NAS as backup repository at each location) only that HQ have all the jobs while the each site VBR acts as proxy and WAN accelerator.