I used to have my jobs scheduled to run a second after the previous one and that has kept the different backup jobs running in the order I wanted. Now I am trying to run the same jobs with duplicati_client, but it seems that the jobs are not run in the order in which I run the duplicati_client commands.
For example, if I run a script like this:
duplicati_client login || exit duplicati_client run 1 duplicati_client run 2 duplicati_client run 3 duplicati_client run 4 duplicati_client logout
and after all of the jobs have finished, I open the web UI to check the results, I find that the jobs did not end in the order in which I wanted them to run.
Before I start writing extensive run-before and run-after scripts that use a lock file, I decided to ask which part of Duplicati actually ensures that the jobs do not run in parallel, and what might be the preferred way to define the order when I use duplicati_client?