[6.5] Run Now behaviour

[lrosa]

Consider this scenario:

* Job A is scheduled everyday at 22:00
* Job B is scheduled after A finishes
* Job C il scheduled after B finishes

During normal working hours I modify job B and I want to test the changes I made, so I right-click the job and select Run Now.

Job B runs,finishes and job C starts, but this is not what I wanted.

A context menu option such as "Run now only this job" would be useful.


Thanks.


Ciao,
luigi

[dellock6]

Hi Luigi, never tested but is worth a try: what if you disable Job C? Does it runs anyway when chained?

Luca.

[Gostev]

Luca is spot on, the job should not run on schedule if you disable it.

[lrosa]

Yes that could be a workaround, but not a real solution, expecially in the context I mentioned.

[dellock6]

Yep, you are right and the request for that spot command is worth, could you at least confirm the workaround works?

Luca.

[vipthomps]

Having Jobs chained and running only one job requires disabling the next one in the chain before the desired job finishes.

Example

Job A - Start at 10PM
Job B - Start after Job A
Job C - Start after Job B

If i want to run only Job B as a one time event (say a software upgrade by a vendor) I need to disable Job C, Run job B, then enable C after the fact. Backups should have as little human interaction as possible. A run-once option on the job would be an excellent edition in my eyes.

Thoughts?

[Vitaliy S.]

Hi Eric,

Have you considered using max concurrent tasks option on the proxy/repository server to limit the number of jobs running at the same time? In this case there is no need to chain jobs, and there will no issues with starting jobs manually.

Thanks!

[veremin]

As mentioned, the best option you have is to set maximum number of concurrent tasks proxy/repository can handle. Though, if it’s just the case of three jobs you can put into use simple PS script that will ask you to input the name of the job you want to run, then, disable the other two, run a given job, and enable everything back:

Code: Select all

asnp VeeamPSSnapin 
$Names = "Backup job 1", "Backup Job 2","Backup Job 3"
$StarJob = Read-Host "Input name of job you want to start"
Foreach ($Name in $Names)
{
$Job = Get-VBRJob | ? {($_.name -eq $Name)}
$Job | where {$_.name -ne $StarJob} | Disable-VBRJob
} 
Start-VBRJob (Get-VBRJob | where {$_.name -eq $StarJob}) 

Hope this helps.
Thanks.

[mcwill]

We have a number of backup jobs that are chained and I keep getting bitten by the next job in the chain starting if I have manually started or retried a failed job without first disabling the next job in the chain. If I do remember to disable, it's a bit hit and miss when it is safe to enable the job again so that it doesn't immediately start processing.

I'm sure it shouldn't be this difficult, how do other users manage their chained jobs?

Thanks,
Iain

[veremin]

Hi, Iain, it might be worth changing the way job are currently chained. Instead of using chaining schedule, you can limit the number of concurrent task proxy/repository can handle and, then, stage the jobs. In this case, there will be no issues in running a given job manually.

Thanks.

[mcwill]

Hi Vladimir,

Would there be any performance concerns in attempting to start 7 jobs at the same time with each job containing between 5 & 10 VMs?

Thanks,
Iain

[veremin]

As long as, the number of concurrent tasks is set properly, there won't be any concerns in staging the jobs. Actually, this is what many of our customers is doing to achieve the same goal.

Thanks.

[foggy]

Yep, performance will be controlled by the max number of concurrent tasks setting on your proxies. In case there are no available slots, the tasks will wait in the queue.

[mcwill]

Will give it a go thanks for the tip.

[Stuzoo72]

Our Veeam servers processes a sequential chain of about seven different jobs each day that are scheduled to follow each other by using the "After this job:" option.

It is currently not possible to test individual jobs in the sequence without altering the schedule for the other jobs.

Currently if you start a job anywhere in the chain all the subsequent jobs will also run.
I would like Veeam to add a button for "Start - single job unlinked". This would run the job in question, but stop the following "After this job:" scheduled jobs from running.
This way if a small change is made to an individual job it can be run without the whole chain running.

Currently when you stop a job in a chain the following jobs will continue to all start one after the other.
I would like Veeam to add a button for "Stop - job chain". This would stop the job in question and stop the following "After this job:" scheduled jobs from running.


Thanks
Stuart

[Vitaliy S.]

Hi Stuart,

Thank you for your feedback, much appreciated. On top of that, can you please tell us a bit more why do you prefer to chain jobs and do not control the amount of concurrently running jobs via tasks settings on the repository/proxy servers? In this case you shouldn't have this problems as you have now.

Thanks!