why reboot after every upgrade?

[mrholm]

Hi
Why do Veeam always need a reboot to finish an upgrade of an agent? Most other backup vendors do this without restart.
Restarting a server due to an upgrade means an extra downtime for production environment.
Since Veeam is not letting us run different versions of agents (why?) the whole environment needs to be restarted during one day along with all other Veeam functions. It's not OK in large environments, when are this going to be changed so we can have one out of two things:
1. Upgrade agents without restart
2. Allow different versions of agents to run (other vendors allows at least 2 versions of agents)

//Mats

[Vitaliy S.]

Hi Mats,

Usually upgrade is required when a new version of .Net is required and when the CBT driver is installed. Here is a bit more info in the existing threads.

Thanks!

[Dima P.]

Hi mrholm,

Since Veeam is not letting us run different versions of agents (why?)

Can you please elaborate? Latest v10 does not require v3 agents to be upgraded immediately: backup jobs remain operational but new features wont be supported by older agent till you upgrade in the to latest version. Cheers!

[Mildur]

In my enviroment, I have disabled automatic update.
As soon we have a maintenance window for os updates, we will manual start the update for all necessary agents from vbr console.
It works for us this way

[mrholm]

OK, thanks Dima, did not really know that it was allowed with different versions on agents now, that makes it easier to plan in the future.
But then we need to stay on older level and then do a upgrade+reboot? I can not do an upgrade of the agent and wait with the reboot?
In our environment we don't use CBT with agents so that is not causing the reboot.
//mats

[Vitaliy S.]

But then we need to stay on older level and then do a upgrade+reboot? I can not do an upgrade of the agent and wait with the reboot?

Please take a look at existing topic for the answer > Agent - upgrade to B&R U4a