This server requires retry - postponing

[davidhodges86]

Hi,

A client of ours recently notified us of what seems to be a major flaw in Veeam's logic...

They have a job which backs up their ESXi VMs to NAS using reverse incrementals and then a backup copy job which runs every night to copy them to tape. The tape job has consistently been successfully so the logs weren't getting checked, however the client, who gets the reports too, informed us they had started taking 4 seconds instead of the usual 8 hours to run so they don't think it's working and could we check.

We discovered a lot of logs like the following for each job going back 2 weeks:
21/09/2015 18:52:24 :: Backup file \\ds\Veeam\Server Group 1\Server Group 1.vbk on This server requires retry, postponing.

The job would then end and send a successful notification.

I created a case with Veeam support - 01033144. They logged on remotely and we re-created the tape job, this didn't fix the problem.
I ran an active full backup but re-enabled the old tape jobs (to test) - this didn't fix the problem.
I then used the new tape jobs we'd created and these ran ok - indicating we needed a new tape job and to run an active backup of the VMs.

Anyway the point of this post is I asked support whether there was any chance the successful logic for tape backups could maybe make the above situation a warning at the very least so someone can pick up on it and fix it.

Support recommended I post in the forum. Here we are.

David

[Dima P.]

Hello David,

Thank you for your input! Funny thing is that we’ve just discussed an issue similar to yours with the tape team. We are going to correct the described behavior in the upcoming major release, meanwhile keep the “if there are some linked backup jobs still running” setting enabled and in case you are using the granular daily schedule make sure that source backup job does not overcome the tape job’s schedule.

[davidhodges86]

Hey,

Excellent news! Though I've no idea what you mean by

meanwhile keep the “if there are some linked backup jobs still running” setting enabled and in case you are using the granular daily schedule make sure that source backup job does not overcome the tape job’s schedule.

Thanks,

David

[Dima P.]

I assume these are the setting support team checked and reconfigured while creating a new job from scratch.

[davidhodges86]

Ah, ok. No I don't think so.

The settings for the new job were exactly the same as the old job.

David

[Dima P.]

Got it - thanks for the heads-up!

[edwink]

Hi there,

I have the same issue. This happens since updating to Ver. 8.0.
In Ver. 7 the Software waited correctly until the other Job ended.

As a "Workaround" i scheduled the job a few hours later and i control it every day.

Good News if this bug will be solved in a future major release.

Edwin

[Dima P.]

Thanks! Let wait for the BETA first, so you could test and confirm this behavior is gone.

[Supraman]

Can anyone please confirm that this has been fixed in 9.5 SP2? I am getting the same message in regards to going to tape Backup file E:\Backups\XXXX -XXXX to DiskXXXX - XXXX to DiskD2017-07-11T180032.vbk on XXXX requires retry, postponing.

[veremin]

It's hard to tell what is the root cause of the given error without seeing debug logs. Kindly, open a ticket with our support team and let them investigate it directly.