Before posting, and to avoid disappointment, please read the following:

  • This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
  • If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.

Running scheduled profiles sequentially vs in parallel

For technical support visit https://support.2brightsparks.com/
Post Reply
santiagodraco
Enthusiastic
Enthusiastic
Posts: 12
Joined: Mon May 15, 2017 8:15 pm

Running scheduled profiles sequentially vs in parallel

Post by santiagodraco »

I'm a bit confused about how to make jobs run sequentially rather than simultaneously via a schedule. It appears that if I schedule jobs independently that if an earlier job is still running another job may start and run in parallel (ie it won't wait for the other job to stop).

I looked at groups and I'm confused as I saw a post here which stated "you can group profiles together so that they will run sequentially" but then in the Wiki on "groups" which shows how to set them up it says "This allows you to run multiple profiles in one go instead of having to run each profile one after another..." which implies to me that ALL profiles in the group will start together? Is this the case?

Lastly it also appears that if I have the main SyncBack Pro window open and I've manually started jobs... that if those jobs are scheduled and start that I might have a job running twice, is that the case?

So my questions are:

1. How to schedule jobs but make it so that jobs start ONLY after other jobs ahead of it have completed. I want to also be able to have jobs going to separate targets run in parallel. Will a group of profiles, one group for each target, do this?
2. Do profiles in groups run sequentially or do they all start at once if the group is scheduled?
3. If a job is started manually in the console and then later that same job is scheduled to start will the job run twice on top of each instance?

Thanks!
santiagodraco
Enthusiastic
Enthusiastic
Posts: 12
Joined: Mon May 15, 2017 8:15 pm

Re: Running scheduled profiles sequentially vs in parallel

Post by santiagodraco »

Looks like a bit of searching got me the answer to my question on running jobs sequentially (put profiles in a group but do NOT check the box to run in parallel).

Still need to understand question 3 above however. Thanks.
cliffhanger
Expert
Expert
Posts: 606
Joined: Tue May 31, 2011 5:59 pm

Re: Running scheduled profiles sequentially vs in parallel

Post by cliffhanger »

santiagodraco wrote:...in the Wiki on "groups" which shows how to set them up it says "This allows you to run multiple profiles in one go instead of having to run each profile one after another..." which implies to me that ALL profiles in the group will start together? Is this the case?
No - the hint simply means you can start a Group with one action (right-click Group > Run, or whatever) which (by default - more on this below) will invoke all the profiles in the Group sequentially (each successive profile waits for the one before it to complete). As opposed to manually Run profile-1, wait till it finishes (or don't, as you prefer), Run profile-2 (wait/not), Run profile-3 (wait/not) and so on

In short ( best I can)

1. use (Schedule) a Group set to run sequentially/one after the other (the default - IOW, don't tick the box at top of the Modify view of the group to 'run...in parallel'). You can make a different Group to run 'parallel' jobs (this time do set the parallel option), but any one Group can't contain a mixture of modes - you can't have x sequential jobs followed by y parallel ones in the same Group (you need two or more Groups). This makes it harder to schedule the 2nd Group, because you don't know for sure how long the first Group will take. You can make (then Schedule) an überGroup (a Group of two or more Groups) but they can't be mixed-mode (one sub-group set to run sequentially, one set parallel)- at least, it won't work if you try; cascaded Groups will always run sequentially, as mentioned in the Help on Groups. You should probably re-think trying to use 'parallel' - even if the remote devices/resources are separate, your PC will probably be time-sharing traffic to them over the same disk controller, LAN adapter, USB bus, whatever (not to mention thrashing any single HDD-Source). As per the Help comment, running in parallel can be slower unless you have specialist (separate) hardware.

2. See above.
3. The second instance of a profile to try and run will check if a copy is running already; if so, it will log an 'already running' error and abort itself
cliffhanger
Expert
Expert
Posts: 606
Joined: Tue May 31, 2011 5:59 pm

Re: Running scheduled profiles sequentially vs in parallel

Post by cliffhanger »

I see we cross-posted ;)
Hopefully #3 clarifies for you
santiagodraco
Enthusiastic
Enthusiastic
Posts: 12
Joined: Mon May 15, 2017 8:15 pm

Re: Running scheduled profiles sequentially vs in parallel

Post by santiagodraco »

Thanks!
santiagodraco
Enthusiastic
Enthusiastic
Posts: 12
Joined: Mon May 15, 2017 8:15 pm

Re: Running scheduled profiles sequentially vs in parallel

Post by santiagodraco »

I should also mention that I DON'T want to run profiles in parallel except when those "jobs" run from/to different targets. I have multiple NICs in my server and some targets are tied to a separate subnet from others so parallel jobs won't saturate a connection.
Post Reply