Comprehensive data protection for all workloads
Post Reply
FBraendle
Enthusiast
Posts: 39
Liked: 1 time
Joined: Jul 05, 2010 3:36 pm
Full Name: Felix Brändle
Contact:

periodic active fulls dont run

Post by FBraendle » Apr 23, 2013 11:55 am

Hi Guys

I got a question regarding job scheduling & periodic active fulls
I searched the forum but couldnt find a similar topic.

my setup looks like this:
i split up the VMs into 30+ jobs and configured 4 jobs to run daily around 19:00. all the other jobs are chained to those 4 jobs via "run automatically after this job"
all the jobs are configured to run weekly periodic active fulls(for now, because we got performance problems with the synthetics which we have to solve before activating them)

The jobs run fine, one after another, 4 in parallel. The problem is, no active fulls are written. Instead veeam creates normal incrementals.


i thought before i fumble around with the job settings ill ask around here. it might be a known issue...

Greets
Felix

BTW: is there an option to run synthetic fulls on demand? via PS or whatever?
would make testing easier ;)



Greets
Felix

veremin
Product Manager
Posts: 16884
Liked: 1433 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: periodic active fulls dont run

Post by veremin » Apr 23, 2013 12:08 pm

BTW: is there an option to run synthetic fulls on demand? via PS or whatever?
Yep, it’s possible with PoweShell. For more information regarding it kindly see this post, or more specifically, the part that starts with the following line:

So, if your goal is to run synthetic full manually

Additionally, full backup can be also run on demand:

Code: Select all

$Job = Get-VBRJob | ?{$_.name -eq "Name of your job"}
Start-VBRJob $Job -FullBackup
Hope this helps.
Thanks.

foggy
Veeam Software
Posts: 18251
Liked: 1558 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: periodic active fulls dont run

Post by foggy » Apr 23, 2013 12:11 pm

Felix, most likely, chained jobs are started on the next day (not the one the active full is scheduled to be performed at), due to the time required to run earlier jobs. This is typical for chaining jobs so if you want to limit the load on the infrastructure, you'd better limit tasks concurrency on the proxy (or the repository) and let all the jobs start together.

FBraendle
Enthusiast
Posts: 39
Liked: 1 time
Joined: Jul 05, 2010 3:36 pm
Full Name: Felix Brändle
Contact:

Re: periodic active fulls dont run

Post by FBraendle » Apr 23, 2013 1:05 pm

so obvious... lol
jup, thats definitly the problem :)

thnx, ill adjust the jobs accordingly...

Best Regards
Felix

Post Reply

Who is online

Users browsing this forum: No registered users and 27 guests