Certificate updated - reboot required

[toreml]

Hi.
I get the following message when I start the VBR console:
Backup server certificate has been changed and reboot is required.

Is there any possibility to fix this without rebooting?
I have severeral backup / merge jobs running - so I can't reboot now.
I don't want to kill the running jobs.

I should do a restore - but it failed due to the certificate issue.

I'm running VBR 9,5 update 4

Regards
Tore Mejlænder - Larsen

[wishr]

Hi Tore,

Have you replaced the certificate, or what's the prehistory?

Thanks in advance,
Fedor

[toreml]

Hi - I ended up with rebooting the server.
So all OK now

[Buh95]

Hi all,

We are currently using Veeam Backup 9.5 U4a.
This morning, opening the console, we got this message : "Backup Server certificate has been changed and reboot is required. Some restore operations will be failing until the server is rebooted".

The message is pretty clear, but we didn't change anything about certificate, so I guess this is an automated process that renews Veeam internal certificate.

The question is : would it be possible to avoid the reboot ? We have a lot of long archive jobs that are still running, and this is currently impossible to restore.

Thanks in advance.

Regards,

Téo.

[wishr]

Hi,

Unfortunately, at least backup services should be restarted, but that in turn requires jobs to be stopped.

This is a one-time operation and the newly issued certificate will work for ~ten years. If not replaced in time a lot of functionality will fail including Agent Management, FLR, etc. until the replacement is done, so we are kinda forced to do it as lesser of two evils.

Thanks

[Buh95]

Hi,

Thank you very much for your response.

We've just retarted the server, it seems to be ok.
But we had to kill some backup copy jobs that was in merge operation... I hope this won't break any backup chain or consistency...

Perhaps a future Veeam version may include a anticipated process about that certificate expiration.

Have a good week-end !

[veremin]

Stopping a job during merge process might cause certain issues, so, I recommend you checking recoverability of the last and second last restore points. Thanks!