search

Tecnativa / docker-duplicity

Docker image for running duplicity in a cron
Apache License 2.0
77 stars 40 forks source link

Duplicate process handling for very long backup #67

Closed derickson2402 closed 3 years ago

derickson2402 commented 3 years ago

Hello, I have finally tested and set up my backup solution, and I am preparing to run the first backup. However, with my pitifully slow upload speed (15mbps with Xfinity), the first upload will take around a full week.

I am fine with this, but I want to know if Duplicity will handle this correctly. Of course there will be multiple daily backups which attempt to run while the backup is going, but will Duplicity know not to run these?

joao-p-marques commented 3 years ago

Hi @derickson2402

Well, we are only packaging duplicity in a cron runner, so I guess this would be a better question to ask upstream: https://gitlab.com/duplicity/duplicity

OTOH, if you want to skip the crons until you have the first full backup completed, you can override the default JOB_* variables and only run the command you need for the first backup, and then re-enable them when it is completed, although perhaps @Yajo could help more here.

derickson2402 commented 3 years ago

Thanks @joao-p-marques. I ended up just running the container through a bash script rather than compose which I was using, and executed the jobrunner instead of letting cron run. This worked pretty well other than the fact that the packaged version of pydrive is broken.

joao-p-marques commented 3 years ago

I am glad it worked well :+1:

This worked pretty well other than the fact that the packaged version of pydrive is broken.

Well, we did have to loose some dependencies to make it work due to the new pip dependency resolver, so this must be a side effect. You can open a separate issue for than if you want, and maybe someone in the community wants to try to solve it :smiley: