Morning team!
I just created a new backup repository and needed to perform a few fulls to seed. I configured the jobs to run After Job (first time as i never trusted something without a time frame).
I had 2 full backups run at the same time with 6 others running behind them in a chain (so after the 2 complete the next one will kick off etc).
One chain worked perfectly as intended however the other backup failed to start the next one of the chain even though it complete with success.
Can anyone tell me limitations of the AFTER JOB scheduled function in relation to:
1. Do jobs kick off even after failures
2. Number of AFTER JOB schedules that can be run simultaneously
Have you had similar experiences?
Veeam version 9.5.0.1536
-
- Novice
- Posts: 5
- Liked: 1 time
- Joined: Apr 14, 2016 2:42 am
- Full Name: Newton Thaiposri
- Contact:
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: After "Next Run" schedule
Hi,
The "After this job" function will only start a job if the first job in the chain is started automatically by schedule. Would you clarify how are your jobs arranged and which of them have failed? Was it something like this?
Job1 (scheduled) --> Job1.2 (after Job1) --> Job1.3 (After Job1.2) --> ...
Job2 (scheduled) --> Job2.2 (after Job2) --> ...
Thanks
The "After this job" function will only start a job if the first job in the chain is started automatically by schedule. Would you clarify how are your jobs arranged and which of them have failed? Was it something like this?
Job1 (scheduled) --> Job1.2 (after Job1) --> Job1.3 (After Job1.2) --> ...
Job2 (scheduled) --> Job2.2 (after Job2) --> ...
Thanks
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot] and 252 guests