What happens if backups don't finish before next run?

General Topics
1

Hi! I’m playing around with the before and after scripts and I’m wondering what happens if the entire backup job (i.e. including the before and after script) doesn’t complete before the next scheduled snapshot?

I’m going for quite a blunt approach of a scheduled snapshot that:

  • PRE: takes down all docker contains (except the kopia and reverse proxy)
  • snapshots all the docker volumes (except for those used by kopia and reverse proxy) to the local kopia repository
  • POST: starts up all the docker containers and then rclones the local kopia repository offsite

I’m planning on doing this once in the early hours. In the worst case though, what happens if the whole job takes more than 24 hours. What happens when the time to snapshot rolls around again?

Thanks!

2

I guess you are talking about kopia UI. In such case nothing happens. No new job will be triggered before the previous one is finished.

1 Like
3

thanks @kapitainsky. This is what I assumed.

If I created the snapshot from the CLI, and set it not to automatically schedule then I guess I need to manage the sequencing myself?

4

CLI does not have any scheduler. So it is up to you to manage it. IMO it is not good idea to allow running overlapping jobs. Use your OS capabilities to prevent it.

1 Like