Hi,
I have my full backups configured to run on Saturday. The problem is that a full backup run takes longer than one day. So jobs run after midnight revert back to incremental.
Has any one else run into this and how did you work around it?
I considered creating a separate job just for full's but I think that would be too much overhead.
Thanks if you can help or have any suggestion.
-
- Enthusiast
- Posts: 45
- Liked: 2 times
- Joined: Jul 27, 2015 5:14 pm
- Full Name: Brian Galante
- Contact:
-
- Veteran
- Posts: 635
- Liked: 174 times
- Joined: Jun 18, 2012 8:58 pm
- Full Name: Alan Bolte
- Contact:
Re: Veeam Full backups
This is a fairly common problem with chained backup jobs (set to start after each other). Are your jobs chained, or are they waiting until the next day because of concurrent-tasks limits?
One option is to change the job schedules to ensure that some jobs start their fulls on Saturday and others start their full on Sunday.
One option is to change the job schedules to ensure that some jobs start their fulls on Saturday and others start their full on Sunday.
-
- Enthusiast
- Posts: 45
- Liked: 2 times
- Joined: Jul 27, 2015 5:14 pm
- Full Name: Brian Galante
- Contact:
Re: Veeam Full backups
Yes, they are chained. Thank you for the reply! I will have to get a little more creative with the schedule.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam Full backups
Yes, job chaining is not highly recommended setup. If you want to start jobs one by one, then you use concurrent tasks limit on the proxy/repository servers.
Who is online
Users browsing this forum: No registered users and 34 guests