Hello, we have the following issue. We have a backup job that starts daily at 11:00 p.m. and creates a synthetic fullbackup every Wednesday. There is a 2nd backup job that starts after the first job and also does a synthetic fullbackup on Wednesday.
Now to our problem.
If the first backup job takes longer than one hour (this happens sometimes) the second backup job of course starts later (e.g. Thursday 00:05 a.m.) then the second backup job doesn't make a synthetic fullbackup anymore, because in the configuration of the job it says - Create synthetic Full every Wednesdays.
I find this circumstance very unfortunate, because in this case I lack a fullbackup.
Is there a setting that configure the job to create a syntetic full even if it is no longer Wednesday?
Thanks.
BR
Carsten
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jan 18, 2019 11:08 am
- Full Name: Carsten Scholl
- Contact:
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: Issue with synthetic full backup
Hi Carsten and welcome to the community!
You can start both backup jobs at the same time, even if the resources aren't enough to process both jobs in parallel. This way the second job will result in a full backup, since it was in the queue starting from Wednesday.
The job chaining isn't the recommended approach due to a numerous disadvantages it has. You can read detailed information about Job Chaining here. Thanks!
You can start both backup jobs at the same time, even if the resources aren't enough to process both jobs in parallel. This way the second job will result in a full backup, since it was in the queue starting from Wednesday.
The job chaining isn't the recommended approach due to a numerous disadvantages it has. You can read detailed information about Job Chaining here. Thanks!
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Issue with synthetic full backup
Just limit the max number of concurrent tasks on proxy/repos, if resource contention was the primary reason for job chaining.
Who is online
Users browsing this forum: Amazon [Bot], Majestic-12 [Bot], Steve-nIP and 295 guests