Mail server backup jobs fails, Cause of Veeam server reboot

[Lennydk87]

Hello,

Im already working with support on this one, but it wont hurt to hear other too.
Case ID 02313555

Last thursday, our Veeam backup server rebooted because of an Windows update, while it was backuping up our mail server.
Because of that the mail server job has failed ever since.

The first error we got was this one:

"Rolling back changes made by incomplete job run
Error: Retrieved less bytes from the storage [0] than required [5246976]. Offset: [28768311808]. File: [D:\Backups\Mail\MailD2017-09-13T210052.vrb]. "

I followed this guide: https://www.veeam.com/kb2255

But this removed ALL restore points from the Veeam console, files is still visible in the folder.
Is it possible to get the restore points back?

After that I've tried alot of things, and now I get these two errors when we run the mail job:

"Processing HVMEX02 Error: The RPC server is unavailable. RPC function call failed. Function name: [InvokerTestConnection]. Target machine: [192.168.1.29]. "

"Processing HVMEX02 Error: Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown."

Anybody got a solution for this problem? it is very critical, because we dont got any restore points on our production mail server.!

[Vitaliy S.]

Hello Lennart,

But this removed ALL restore points from the Veeam console, files is still visible in the folder.
Is it possible to get the restore points back?

If you followed all steps from the KB (especially point 2, then there can't be any files on the datastore). Anyway, have you tried to rescan the repository to get available restore points back?

While waiting for the support team to respond after reviewing debug log files, try to trigger active full backup, that would start a new backup chain and you will have at least 1 backup for your production server.

Thanks!

[Lennydk87]

Hey Vitaliy,

I've just tried an active full backup, it runs for like 15 min and fails with this message:

"HVMEX02 Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.29:2500"

. 1.29 is our Veeam proxy
But firewall on both veeam proxy and veeam server is turned off.

[Vitaliy S.]

Ok, then please continue working with our technical support team, cause logs review is required here.

[Lennydk87]

Hello Vitaliy.

Case closed.

It looks like when we were running Full backup of the VM, when it was out of throttle time (We trottle our veeam backup from 6 in the morning to 8 in the evening), it took all bandwidth, and caused disconnection between VM and Veeam backup server.

So full backup was run in throttle time, and the normal incremental job runs fine outside og throttle time, as it did before the failures started.

[Vitaliy S.]

Thanks for the update!