-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating backup in target directory fails with systemd timer #81
Comments
snap-sync-root.txt |
Can you post the output of the following?
|
Having this problem too, seems that the $backupdir variable is not used when creating subsequent backups. |
@FrankNoWar can you give the output to the following? sudo snapper -c root list | grep "latest incremental backup" |
@wesbarnett I do not have a root config as my root volume is not btrfs, however here is the output for my home config.
|
Is this only with a timer or even when the command line is run? I can't seem to reproduce this. |
I think the problem raises if the "used spaced" column is added to the table. This happened to me for one config of snapper but not for the other. awk is then selecting the wrong column. This does not happen if you add --disable-used-space |
Hi,
when I create the initial backup with snap-sync the tool asks for a directory. Here I typically use the hostname in order to identify different backups of multiple hosts.
This directory is then created as a subvolume and the the backup of relevant subvolumes, e.g. root, home, etc. is started.
This all works fine and the result is this:
However, when I schedule a backup with systemd-timer using this systemd-config
the backup is written to subvolume with ID=257 and a relevant directory root, home is created.
Problem:
How can I ensure that the automatic backup is written to the initially created directory pc1-desktop?
THX
The text was updated successfully, but these errors were encountered: