Job chain together with windows task schedular?

[Bart1982]

Hi All,

The standard veeam job schedules are not working for us, we are trying to reduce the amount of storage on our backup NAS devices with our backups but on the same time also have a certain amount of restore points.

We have 20+ locations running veeam across europe and south africa, The mayority of our servers are simple file and print servers and the amount of changed data is limited (we are seeing about 5gb of changed data per location per day)

the backup copy jobs are simply generating full backup files which is just to much for us. A new schedule has been created to overcome these issues.

The backup schedules look like this: all jobs are reversed incrementals
Daily: monday, tuesday, wednesday, thursday and fridays
Month: first saturday of each month
Week2-4: second and forth saturday (I don't want to run it each week as we already have a monthly job which runs on the same day sometimes)

the daily and monthly jobs can be done via the veeam schedules, however week2+4 is not possible. I thought I got around this with creating a dummy job.
Dummy job runs via the windows schedular (I copied the command line which veeam generates and run this via the schedular)
then for all the locations the weekly job is linked to the dummy job *run after*

This works when i run the dummy job from the veeam console, veeam asks if I want to run the chained jobs.

When running the job from the command line (windows task schedular), the linked jobs are not running. Is there a command switch which also triggers the chained jobs?

Thanks

all of the maintance jobs are running on several sundays.

[nielsengelen]

You can start jobs using Powershell so best would be to create a script that does the trick for the first job which will then trigger the chain job afterwards. This can be done by Start-VBRJob.

The reason why it won't work by running the command line is because of a random id being generated therefor your best option is to use powershell.

[Bart1982]

I've resolved it via the following method

Job remains the same, but I enabled the dummy job to run every week on Saturday.
- Dummy job, Run every Saturday 12:00
- Bi-Weekly job location 1, Linked to Dummy job
- Bi-Weekly job location 2, Linked to Dummy job
- Bi-Weekly job location 3, Linked to Dummy job
...
- Bi-Weekly job location 20, Linked to Dummy job

I run the following script daily via the windows scheduler: (I run this everyday if a schedule is missed it will correct itself the next day)
With a powershell script I'm checking which week of the month it is:
- if week number is 2 or 4 the script enables the Dummy Job via a powershell command
- if week number is not 2 or 4 the script disables the Dummy job

In this method I'm able to control when the dummy job runs automatically and thus when the chained jobs are running.

Thanks for you help vmniels!