Recommended borgmatic.service settings for non-root use? #669

New Issue

Closed

opened 2023-04-08 00:21:15 +00:00 by shervinsahba · 3 comments

shervinsahba commented 2023-04-08 00:21:15 +00:00

Copy Link

What I'm trying to do and why

I've been running borgmatic as a non-root user on several systems, mainly to backup home directories. The borgmatic.service template is written for root.

I had set up a systemd timer for my user to run borgmatic, but I'm quite unsure about all the options in the above service file. Could we have some guidance on how to adopt that file for a user?

Other notes / implementation ideas

I had been using a very minimal service file to run as my user. It works, but am I missing anything important from the provided template? If I understand correctly, the security and capability settings probably aren't needed. However, I don't know if controlling things like CPU niceness or if using systemd-inhibit are things my non-root user can do.

In any case, this is what I am using. Am I missing anything crucial when compared to the template file? Thank you.

borgmatic.service:

[Unit]
Description=borgmatic backup
Wants=network-online.target
After=network-online.target
ConditionACPower=true

[Service]
Type=oneshot

Restart=no
LogRateLimitIntervalSec=0
ExecStartPre=sleep 1m
ExecStart=borgmatic

Environment

borgmatic version: 1.7.11

borgmatic installation method: Arch community package

Borg version: 1.2.4

Python version: 3.10.10

Database version (if applicable): n/a

operating system and version: 6.2.9-arch1-1

#### What I'm trying to do and why I've been running borgmatic as a non-root user on several systems, mainly to backup home directories. The [borgmatic.service](https://projects.torsion.org/borgmatic-collective/borgmatic/raw/branch/master/sample/systemd/borgmatic.service) template is written for root. I had set up a systemd timer for my user to run borgmatic, but I'm quite unsure about all the options in the above service file. Could we have some guidance on how to adopt that file for a user? #### Other notes / implementation ideas I had been using a very minimal service file to run as my user. It works, but am I missing anything important from the provided template? If I understand correctly, the security and capability settings probably aren't needed. However, I don't know if controlling things like CPU niceness or if using systemd-inhibit are things my non-root user can do. In any case, this is what I am using. Am I missing anything crucial when compared to the template file? Thank you. borgmatic.service: ``` [Unit] Description=borgmatic backup Wants=network-online.target After=network-online.target ConditionACPower=true [Service] Type=oneshot Restart=no LogRateLimitIntervalSec=0 ExecStartPre=sleep 1m ExecStart=borgmatic ``` #### Environment **borgmatic version:** 1.7.11 **borgmatic installation method:** Arch community package **Borg version:** 1.2.4 **Python version:** 3.10.10 **Database version (if applicable):** n/a **operating system and version:** 6.2.9-arch1-1

witten commented 2023-04-08 03:57:39 +00:00

Owner

Copy Link

Great question! I'm no systemd expert, but here's my take:

• I think you are right about the security and capability settings.
• systemd apparently doesn't support non-root niceness settings out of the box. There are workarounds though if that's something that's important to you. Personally I just run borgmatic at a time when I'm not likely to be using the computer.
• systemd-inhibit just prevents system sleep/shutdown while borgmatic is running. If you want to use it from a systemd user service, it looks like you can. But it's up to you as to whether you want that functionality.
• I don't think you're missing anything crucial. You might want to pass some verbosity flags to borgmatic though if the default verbosity isn't to your liking. For instance, increasing the syslog verbosity is probably a good idea.

Hope that helps.

Great question! I'm no systemd expert, but here's my take: * I think you are right about the security and capability settings. * systemd apparently doesn't support non-root niceness settings out of the box. There are [workarounds](https://superuser.com/questions/1447351/set-niceness-value-in-a-systemd-user-service) though if that's something that's important to you. Personally I just run borgmatic at a time when I'm not likely to be using the computer. * `systemd-inhibit` just prevents system sleep/shutdown while borgmatic is running. If you want to use it from a systemd user service, [it looks like you can](https://github.com/systemd/systemd/issues/20898#issuecomment-931350503). But it's up to you as to whether you want that functionality. * I don't think you're missing anything crucial. You might want to pass some verbosity flags to borgmatic though if the default verbosity isn't to your liking. For instance, increasing the syslog verbosity is probably a good idea. Hope that helps.

witten added the

question / support

label 2023-04-08 03:57:46 +00:00

shervinsahba commented 2023-04-08 18:37:59 +00:00

Author

Copy Link

Thank you for the reply!

Interesting about the systemd-inhibit call. Since borg supports resumed backups, I'll keep it off the laptop at least.

Good call on the verbosity flags... I was wondering where my logs were recently!

Thank you for the reply! Interesting about the `systemd-inhibit` call. Since [borg supports resumed backups](https://borgbackup.readthedocs.io/en/stable/faq.html#checkpoints-parts), I'll keep it off the laptop at least. Good call on the verbosity flags... I was wondering where my logs were recently!

witten commented 2023-04-08 21:31:45 +00:00

Owner

Copy Link

Sounds good! I'll close this for now, but feel free to post any followups including findings on using borgmatic with a non-root systemd service.

Sounds good! I'll close this for now, but feel free to post any followups including findings on using borgmatic with a non-root systemd service.

👍 1

witten closed this issue 2023-04-08 21:31:45 +00:00

witten referenced this issue from a commit 2023-06-14 21:58:19 +00:00

Add sample systemd user serivce for running borgmatic as a non-root user (#669).

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#669

No description provided.