Comprehensive data protection for all workloads
tullyal
Novice
Posts: 6
Liked: 1 time
Joined: Oct 03, 2011 12:45 pm
Full Name: Alan Tully
Contact:

V8 Backup Jobs Not Starting

Post by tullyal » Nov 26, 2014 2:56 pm

Hi All,

We are currently V8 with a DD160 and have upgraded from V7.

Has anyone had problems running backup jobs where the scheduling is set to run after another backup job.

New backup jobs and cloned & modified jobs will not run since the upgrade.

Existing backup jobs created in V7 still continue to run after each other.

Anyone experiencing this?

Alan

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Nov 26, 2014 3:19 pm

Alan, what specific error messages do you get in your backup jobs that do not run? Have you contacted technical support already?

tullyal
Novice
Posts: 6
Liked: 1 time
Joined: Oct 03, 2011 12:45 pm
Full Name: Alan Tully
Contact:

Re: V8 Backup Jobs Not Starting

Post by tullyal » Nov 26, 2014 4:07 pm 1 person likes this post

Hi Foggy,

thanks for replying to my post.

We are currently running on an NFR license and I am testing the software to see how it works etc. so no support ticket.

There is no error message. The backup job does not start.

Job B is scheduled to start after A. I can run Job A by manually starting it and I would expect Job B to start after Job A completes but it doesn't.

I had a chain of jobs created in V7 that still works but new jobs created in V8 (after the upgrade) do not behave as per the schedule.

Regards,
Alan

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Nov 26, 2014 4:21 pm

We do provide support to those who has free/NFR licenses, based on staff availability though. So feel free to contact them, just respect the fact that they have a much increased number of requests due to the recent v8 release. Thanks!

nefes
Veeam Software
Posts: 638
Liked: 160 times
Joined: Dec 10, 2012 8:44 am
Full Name: Nikita Efes
Contact:

Re: V8 Backup Jobs Not Starting

Post by nefes » Nov 28, 2014 4:59 pm

Behavior of "After this" schedule have been changed since v7.
In v8 manual start of job A will not trigger job B to start. That was quite common request in v7.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Nov 28, 2014 5:14 pm

Alan, can you confirm that you've tried to start the jobs chain only manually?

cliffm
Enthusiast
Posts: 41
Liked: 4 times
Joined: Jun 03, 2011 12:41 am
Full Name: Cliff Meakin
Contact:

Re: V8 Backup Jobs Not Starting

Post by cliffm » Nov 30, 2014 8:51 pm

Ah, I have the same issue.
Veeam "after this" backups will not run if I start a job manually.
Has this really been removed? I have built a whole system of weekend backups that write to a series of swapped drives. I always check that the correct drive is plugged in, then start the correct backup for that drive. After this a cascade of backups for that drive run "after this".

Thanks

Gostev
SVP, Product Management
Posts: 25819
Liked: 3974 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: V8 Backup Jobs Not Starting

Post by Gostev » Nov 30, 2014 9:40 pm

Yes, this was changed in v8 based on feedback - manual job runs no longer triggers chained job. Most users have considered this behavior to be a bug, because we are talking about an option of "Run the job automatically" control, which should not apply to manual job executions (as the name of the option implies). Thanks!

cliffm
Enthusiast
Posts: 41
Liked: 4 times
Joined: Jun 03, 2011 12:41 am
Full Name: Cliff Meakin
Contact:

Re: V8 Backup Jobs Not Starting

Post by cliffm » Dec 01, 2014 2:20 am

Oh no! That is bad news. I rely on automatic backups after a manual start. How can I change this? Otherwise I am stuck in front of the computer for hours starting every job manually.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 01, 2014 7:39 am

Cliff, what i the purpose of chaining jobs in your case? Why not just to start all of them and limit the number of concurrent tasks per proxy/repository to control the load?

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

Re: V8 Backup Jobs Not Starting

Post by veremin » Dec 01, 2014 9:20 am

How can I change this?
You might want to set automatic schedule, instead of manual, and set a pre-job script (for the first job in chain) to check whether or not the correct drive is inserted and let the job proceed or not in accordance.

Thanks.

tullyal
Novice
Posts: 6
Liked: 1 time
Joined: Oct 03, 2011 12:45 pm
Full Name: Alan Tully
Contact:

Re: V8 Backup Jobs Not Starting

Post by tullyal » Dec 01, 2014 9:35 am

Hi All,

many thanks for all the feedback on my query.
Glad to find out that the "after this" backups don't trigger after a manual start is a 'feature' rather than a bug, and I can confirm looking at report emails that the jobs I had scheduled as "start after this" did indeed run when not using a manual start to the chain.

Thanks again.
Alan

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 01, 2014 10:44 am

Btw, here's a good reading about why job chaining is not considered as best practice, just FYI.

cliffm
Enthusiast
Posts: 41
Liked: 4 times
Joined: Jun 03, 2011 12:41 am
Full Name: Cliff Meakin
Contact:

Re: V8 Backup Jobs Not Starting

Post by cliffm » Dec 03, 2014 7:42 pm

v.Eremin wrote: You might want to set automatic schedule, instead of manual, and set a pre-job script (for the first job in chain) to check whether or not the correct drive is inserted and let the job proceed or not in accordance.

Thanks.
OK thanks. But I don't know how to do this. Is this a Veeam shell script? Any pointers?

Thanks

nefes
Veeam Software
Posts: 638
Liked: 160 times
Joined: Dec 10, 2012 8:44 am
Full Name: Nikita Efes
Contact:

Re: V8 Backup Jobs Not Starting

Post by nefes » Dec 04, 2014 10:41 am

So if you need to start a chain of jobs, you could temporary schedule first one to run at current time plus several minutes, and disable (or adjust back) it's schedule after it have been started.
You could also write a simple script to do that for you in one click with powershell, if you need to perform that operation often.

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

Re: V8 Backup Jobs Not Starting

Post by veremin » Dec 04, 2014 11:11 am

Is this a Veeam shell script? Any pointers?
The pre-job activity is Veeam functionality, indeed. The script should use ordinary PS commands to check whether or not the correct drive is inserted. If you need an assistance with that, feel free to create a topic in the corresponding subforum. Thanks.

cliffm
Enthusiast
Posts: 41
Liked: 4 times
Joined: Jun 03, 2011 12:41 am
Full Name: Cliff Meakin
Contact:

Re: V8 Backup Jobs Not Starting

Post by cliffm » Dec 04, 2014 11:43 am

nefes wrote:So if you need to start a chain of jobs, you could temporary schedule first one to run at current time plus several minutes, and disable (or adjust back) it's schedule after it have been started.
You could also write a simple script to do that for you in one click with powershell, if you need to perform that operation often.
OK thanks, I worked it out.
I have a batch file that starts a powershell script. The batch file checks for the drive plugged in and then starts the script for the appropriate job.
Thanks :)

cliffm
Enthusiast
Posts: 41
Liked: 4 times
Joined: Jun 03, 2011 12:41 am
Full Name: Cliff Meakin
Contact:

Re: V8 Backup Jobs Not Starting

Post by cliffm » Dec 06, 2014 9:14 pm

Ah no that didn't work. A job chain does not progress if I start a job from a powershell script. Only the first job runs.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 08, 2014 6:31 am

cliffm wrote:Ah no that didn't work. A job chain does not progress if I start a job from a powershell script. Only the first job runs.
You should not start the job chain form the script, but rather do as Vladimir has suggested above:
v.Eremin wrote:You might want to set automatic schedule, instead of manual, and set a pre-job script (for the first job in chain) to check whether or not the correct drive is inserted and let the job proceed or not in accordance.

jcmachadouga
Enthusiast
Posts: 29
Liked: 7 times
Joined: Aug 02, 2011 2:17 pm
Full Name: Juan Machado
Contact:

[MERGED] v8 backups with "RUN AFTER" setting not working

Post by jcmachadouga » Dec 08, 2014 1:12 pm

We do have a lot of jobs that rely on the feature "RUN AFTER". This is not working after our upgrade to v8.

I have been told by Veeam Support that this is a known bug. Is there a patch available for this? Thanks.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 08, 2014 1:49 pm

Juan, please review the thread above, you're probably experiencing the same change in behavior: in v8 chained jobs do not run if the parent job is started manually. Could you please confirm whether this is the case for you?

AJ83
Enthusiast
Posts: 60
Liked: 1 time
Joined: Oct 06, 2009 2:32 pm
Contact:

Re: V8 Backup Jobs Not Starting

Post by AJ83 » Dec 08, 2014 2:53 pm

How can this be called a feature?

We rely on chaining for some filecopy jobs in which we run a powershell script to check if certain processes on other machines are ready, we then start a file copy job from this powershell script. Then we rely on a chained copyjob which copy`s a triggerfile to the target to give notice that the copy of files has finished. This whole proces is broken now since the chained job doesn`t start. Please provide a fix for this unwanted feature of not running chained jobs.

We use the power of Veeam for these copy`s because it is a copy from Linux to windows.

jcmachadouga
Enthusiast
Posts: 29
Liked: 7 times
Joined: Aug 02, 2011 2:17 pm
Full Name: Juan Machado
Contact:

Re: V8 Backup Jobs Not Starting

Post by jcmachadouga » Dec 08, 2014 3:30 pm

foggy wrote:Juan, please review the thread above, you're probably experiencing the same change in behavior: in v8 chained jobs do not run if the parent job is started manually. Could you please confirm whether this is the case for you?
I am confused. This has been working fine until v8. Is this a bug or a change in a feature? According to Veeam support (Case ID# 00692626) this is a bug.

Please let me know. Since we have so many backups and no more than 24x7 hours a week, we have to rely on this feature.

Thanks.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 08, 2014 3:33 pm

This is not a bug, but an intentional change, please see Anton's post above for explanation. Thanks for the case ID, I will check the case for possible misunderstanding of this behavior.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 08, 2014 3:53 pm

AJ83 wrote:We rely on chaining for some filecopy jobs in which we run a powershell script to check if certain processes on other machines are ready, we then start a file copy job from this powershell script. Then we rely on a chained copyjob which copy`s a triggerfile to the target to give notice that the copy of files has finished. This whole proces is broken now since the chained job doesn`t start. Please provide a fix for this unwanted feature of not running chained jobs.
Am I understanding you right, you have just a single chained job that should run after the parent job? Why not to trigger it directly from the script, when the parent job completes?

AJ83
Enthusiast
Posts: 60
Liked: 1 time
Joined: Oct 06, 2009 2:32 pm
Contact:

Re: V8 Backup Jobs Not Starting

Post by AJ83 » Dec 10, 2014 1:25 pm

That`s right, how would i do that?

I start the jobs with the following command in a powershell script:

Code: Select all

$job = Get-VBRJob | ?{$_.Name -eq $jobName}
Start-VBRJob -Job $job
The script is running out of user session.

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

Re: V8 Backup Jobs Not Starting

Post by veremin » Dec 10, 2014 6:56 pm

Being converted to a .bat file the referenced script can be selected as a post-job activity of the parent job. Thanks.

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

Re: V8 Backup Jobs Not Starting

Post by foggy » Dec 10, 2014 7:45 pm 1 person likes this post

File copy job does not have a post-job activity option, that's probably the reason for using chained job to monitor its completion in this case.

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

Re: V8 Backup Jobs Not Starting

Post by veremin » Dec 10, 2014 7:51 pm 1 person likes this post

Then, two jobs might be executed within the mentioned script. Without additional parameters PS should process lines one by one, meaning that it wouldn't start child job, until the parent one is finished. Thanks.

Philippe_Allard
Lurker
Posts: 1
Liked: never
Joined: Feb 21, 2015 1:04 pm
Full Name: Philippe Allard

Re: V8 Backup Jobs Not Starting

Post by Philippe_Allard » Feb 21, 2015 1:12 pm

This is very sad, the way I see it, I upgraded to version 8 and lost a feature that was working perfectly fine and was doing what it said it was going to do… Start a job automatically after another job is finished. It doesn’t say anything about Scheduled or manually started job… it just started the job automatically after another one completed.

Completely changing this feature because some people complained about this behavior without considering that many of us think it was perfectly fine is definitely not the right way to address this problem. Veeam people should have added a checkbox next to this option saying ‘’ Also run if job is started manually’’ or something like that… This way everyone would be happy… ( Feature for a next release maybe ?? )

You changed it because some people saw the previous behavior as a bug… Now Ii is I who see the new one as a bug because the option clearly says to start a job automatically after another, except it doesn’t right now if I start the first one manually and it used to work just fine in version 7.

Post Reply

Who is online

Users browsing this forum: cmaier, Google [Bot], mingji, PetrM and 35 guests