Autopilot - How to handle Backups taking longer than Schedule #746

New Issue

Closed

opened 2023-08-17 12:59:34 +00:00 by xLogiiCx · 3 comments

xLogiiCx commented 2023-08-17 12:59:34 +00:00

Copy Link

What I'm trying to do and why

I am trying to Automate my Backups using Cron or Systemd.
The question I asked myself was how to make sure that the backups don't get in each other's way.
For example if my schedule is hourly what should i do if the Backup takes longer than that?
Should i kill the borg/borgmatic process beforehand and then remove the log when my Backup starts again?

Steps to reproduce

No response

Actual behavior

No response

Expected behavior

No response

Other notes / implementation ideas

No response

borgmatic version

No response

borgmatic installation method

No response

Borg version

No response

Python version

No response

Database version (if applicable)

No response

Operating system and version

No response

### What I'm trying to do and why I am trying to Automate my Backups using Cron or Systemd. The question I asked myself was how to make sure that the backups don't get in each other's way. For example if my schedule is hourly what should i do if the Backup takes longer than that? Should i kill the borg/borgmatic process beforehand and then remove the log when my Backup starts again? ### Steps to reproduce _No response_ ### Actual behavior _No response_ ### Expected behavior _No response_ ### Other notes / implementation ideas _No response_ ### borgmatic version _No response_ ### borgmatic installation method _No response_ ### Borg version _No response_ ### Python version _No response_ ### Database version (if applicable) _No response_ ### Operating system and version _No response_

witten commented 2023-08-17 16:12:00 +00:00

Owner

Copy Link

borgmatic doesn't have any formal support for this use case, but my recommendation would be: Allow the occasional long-running backup to complete without being disturbed. I'm not sure you'd gain a whole lot by killing it and starting a new backup, and you may actually make things worse if a complete backup never finishes because it gets killed once an hour. Also note that if you're using a systemd timer, I believe it already takes care of this for you. From the systemd timer docs:

Note that in case the unit to activate is already active at the time the timer elapses it is not restarted, but simply left running. There is no concept of spawning new service instances in this case.

I hope that helps!

borgmatic doesn't have any formal support for this use case, but my recommendation would be: Allow the occasional long-running backup to complete without being disturbed. I'm not sure you'd gain a whole lot by killing it and starting a new backup, and you may actually make things worse if a complete backup never finishes because it gets killed once an hour. Also note that if you're using a systemd timer, I believe it already takes care of this for you. From the [systemd timer docs](https://www.freedesktop.org/software/systemd/man/systemd.timer.html): > Note that in case the unit to activate is already active at the time the timer elapses it is not restarted, but simply left running. There is no concept of spawning new service instances in this case. I hope that helps!

witten added the

question / support

label 2023-08-17 16:12:12 +00:00

xLogiiCx commented 2023-08-17 17:03:52 +00:00

Author

Copy Link

Also note that if you're using a systemd timer, I believe it already takes care of this for you. From the systemd timer docs:

Great hint, i am gonna use this. Thanks

> Also note that if you're using a systemd timer, I believe it already takes care of this for you. From the systemd timer docs: Great hint, i am gonna use this. Thanks

xLogiiCx closed this issue 2023-08-17 17:03:52 +00:00

witten commented 2023-08-17 17:48:32 +00:00

Owner

Copy Link

Sounds good!

Sounds good!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#746

No description provided.