[Feature Request] Hard-coded 7 day timeout – extension

[DatatoSecure]

By design Veeam stops running backups after 7 days (168 hours).

For better troubleshooting, the Agent Backup job email’s error message should mention this expected behavior instead of unrelated text as in Veeam Agent for Microsoft Windows 2.1.0.423:

Code: Select all

Error: Shared memory connection was closed. Agent failed to process method
Signature.StartReversedSignatureUpdateSession}. Exception from server: Shared memory connection was closed.

If a job can not run for more than 168 hours, then it should restart and back up what has not been yet backed up, instead of thrashing hundreds of gigabytes worth of backed up data and starting the backup process from scratch in an endless loop.

If a job can not run for more than 168 hours, then we have to ask the client to increase his Internet speed, or we won’t be able back him up with Veeam. A solution would be a seed-to-disk functionality in the Veeam Agent.

[Dima P.]

Hello François,

Can you please clarify the amount of data you are backing up? Thanks.

[DatatoSecure]

Hello Dima,

I would say the client has over 400 GB of used space on his hard drive.
In 168 hours, roughly 250 GB get transferred out.
I've asked the client to increase his Internet speed, in the meantime, we are not backing his home office computer.

[vtcv]

Case 03885844
Same issue , and 7 day hard limit could be the difference to a client accepting Veeam as their backup solution or not.

Roadmap on this limitation ?

scenario:
Big file server ( CTO likes things big )
Standard 1GB networking unfortunately.
Approx 27TB of data over 1 GB backed up fine.... but was around 148 hours.... then the second partition was in progress before the 168 hour mark limit kicked in . ( SO CLOSE !!!)
Couldnt get through the full backup of their new file server.

We are considering 10GB options at this point on the cheap and then hostfile overrides between backup server and file server multi-homed. Or alternative providers....

[Dima P.]

Hello vtcv,

Just to make sure we are on the same page - you are trying to backup this file server with Veeam Agent, right? Thanks!

[vtcv]

Yes exactly. I had to relocate data to work around this hard limit of 7 day runtime against agent based backup job, and isolate the server to its own job with specific partition backups. ( two jobs for the single file server..... getting messy)

[dbyers]

All, is there a registry key setting we can use to go beyond 168 hr timeout?

[Dima P.]

Can you please check if latest version fixes you issue: with v5 the job timeout has been increased to 21 days. Cheers!