How to handle long backup with CLI

[kevinvinv]

So I am using the CLI and a launchd to start it daily.

We just came back from vacation with a million photos and it looks like the backup to my remote host will take about 12 days…

So it seems that I need a way to not launch a new duplicacy task every single day whilst the 12 day job is trying to catch things up.

Is there any good way to not launch new duplicacy CLI jobs while the previous one is not yet finished?

Thoughts?

[gchen]

There is a discussion on this topic:

Prevent multiple instances of duplicacy from running at the same time

Hi! First of all I wanted to say a huge THANK YOU for this nice piece of software. I am testing it because, like many, I will be switching from Crashplan for reasons you know. So I am currently backing up my (linux) desktop computer at home to Backblaze B2, and so far it seems to work great. One thing I was wondering though is what happens if I cron/schedule a duplicacy backup to run for example hourly or every few hours. Say one backup is taking longer than expected and the next scheduled back…

[Jeffaco]

This is one of the reasons I wrote duplicacy-util. It will lock activity on a single computer to make sure that two copies of Duplicacy don’t run against the same repository at the same time.

See advantages of duplicacy-util for more information. Feel free to open an issue on GitHub if you have questions.