Cron Job

[Skippy-007]

Hi while doing a large offsite backup (B2) which takes multiple days I find that if the cron job is configured to perform a backup each day at a particular time i.e. 6 am, i have observed weird behaviour. It seems that the cron job does not check that there is another backup active and keep looping trying to perform a backup. The solution is to stop and restart the container or push the cron job out a few days out.

Has anyone seen this behaviour and is there a way to make it check for existing backup process.

[djmaze]

You are right, this is a bug (or at least a non-present feature) in the cron job library.

The question is, what would you expect to happen in these cases?

a) Skip the new backup if an old one is still running
a) Just delay the new backup to run immediately after the old backup has finished

As a workaround, you can for now just slow down your backup schedule (so it is run i.e. every 2 days instead of every day). This is non-optimal, I know.

[Skippy-007]

Hi thanks for the reply. In my view I would expect to skip the new backup until the current one finishes and keep the same cron schedule. Ie don't run a backup immediately after current backup finishes. As a workaround I did have to delay the cron job as per your suggestion. I hope that makes sense.

…

On Mon, 10 June 2024, 6:24 am Martin Honermeyer, ***@***.***> wrote: You are right, this is a bug (or at least a non-present feature) in the cron job library. The question is, what would you expect to happen in these cases? a) Skip the new backup if an old one is still running a) Just delay the new backup to run *immediately* after the old backup has finished As a workaround, you can for now just slow down your backup schedule (so it is run i.e. every 2 days instead of every day). This is non-optimal, I know. — Reply to this email directly, view it on GitHub <#194 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFVDO6IEDBU52OZPJBFFJCLZGTI2FAVCNFSM6AAAAABIU4DO6SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMRRGUYDE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[djmaze]

#201