Patching Veeam Linux GW and Proxy Servers without backup job errors

[uk1984]

We have one VBR server (on Windows Server) and several Veeam Proxy and Gateway Servers on SLES (in total 8 Linux servers).

For patching the Windows OS of the VBR server our current workflow is this:
The Windows team installs the MS Windows Updates and then we stop all backup jobs and once that is done we reboot the VBR server.

Of course best it would be if the Linux servers would also be patched in the same "timeframe" because then they are not actively ussed
as GW or Proxy. But that is either complicated to coordinate and also if then after the patching something with the backup does not work
it is also harder to determine which patching maybe has caused to issue. So we would like to keep the patching of Linux and Windows separate.

We have 8 Veeam Linux servers which both can act as GW or Proxy.
So we have a bit of a redundancy here.
The goal would be to patch all of them but to have no impact on the backup jobs.
So no errors and job terminations...

For the Veeam Linux Proxies there is the option to "disable" them.
So we could manually disable them and from then on no new jobs would be processed by them and
we would "only" have to wait until the existing jobs are finished.

For the Gateway Servers there is no option like that (disabling).
So for Plugins and fileshares ...
You would have to go into each repository properties and "de-select" the GW servers which you wanted to "not-use" because they will be unavailable due to patching and rebooting the Linux servers.
Since we have a lot of repositories this would be too much work...

What are the recommendations from Veeam regarding efficiently patching the GW and Proxy servers so that there is no impact on the backup jobs.

Best Regards
Udo