Default max running hours

[JLundgren]

Hello,

a backup to an SP can take a large amount of time depending on bandwidth.

I found this in documentation concerning VAW limitations:

"Keep in mind that Veeam Agent stops running the backup job after 7 days (168 hours)."

Is there a way to overcome this limitation when first backup is very large but following are much smaller ?
What would you suggest as a solution otherwise ?

[DGrinev]

Hi

Can you share the numbers (bandwidth, amount of source data)?

Thanks!

[JLundgren]

Hello Dmitry,

well, I have to check with customer.
But first, do you have a general response to my questions above ?

[DGrinev]

In the current version of the product no way to remove this limitation. Thanks!

[JLundgren]

Ok, I see.
What is the most obvious solution then ?
Is it to back it up first locally and move the files to a cloud repository ?
Does a KB article exist describing this maybe ?
We will be using policy and subtenant configuration.
On SP side - SOBR is used.

[Dima P.]

Hello Johnny,

There are several option:

1. You can store backups to a local repository and then use backup copy job from transfer your primary site to copy the backup to central location.
2. Another option would be to enable backup cache functionality and land the backup files to a local storage on the agent machine (and sync it with your repository later). The catch here would be that remote target should be inaccessible otherwise Veeam Agent wont fail over to backup cache.

Cheers!