Unable to backup and restore /root

Getting Help
1

Hello,

I’m migrating servers backup to restic with S3 backend.
To perform my backup, I use a systemd service triggered by a timer each day.

[Unit]
Description=Restic Start Backup Job

[Service]
Type=simple
User=restic
AmbientCapabilities=CAP_FOWNER CAP_DAC_READ_SEARCH
ExecStart=/usr/bin/restic -r s3:s3.fr-par.scw.cloud/bucket-namebackup --verbose / --exclude=/proc --exclude=/sys --exclude=/dev --exclude=/run --exclude=/tmp --exclude=/lost+found --exclude=/boot --exclude=/usr/include --exclude=/usr/src --exclude=/var/lib/docker/overlay
EnvironmentFile=/srv/backup/restic-credentials
ProtectControlGroups=yes
ProtectHome=yes
ProtectHostname=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
ProtectSystem=yes
SystemCallArchitectures=native
MemoryDenyWriteExecute=yes
PrivateDevices=yes


[Install]
WantedBy=multi-user.target

I have a problem when I restore from snapshots, only /root folder are not restored.
So I look for solutions, set another systemd capabilities, change backup user from restic to root but nothing fix my problem.

When I search for contents in snapshots with restic ls -l latest I saw /root but anything else, no sub folders.

I understand my restic doesn’t backup content of /root.
There is a restriction of restic ? Can I do anything to perform my backup properly?

Regards

2

Hi,
I’m unsure if backups are actually performed using this syntax.

I don’t see a backup keyword in your command ExecStart=/usr/bin/restic -r ... --verbose / .

Maybe there’s a space missing in bucket-namebackup?

Kind regards,
Bernd

3

Sorry it’s not the space, this is a mistake when I have anonymize the bucket.
I found the solution.

Just removed ProtectHome=yes from my service config and it’s working great !

1 Like