-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Option to store files with absolute path name #1344
Copy link
Copy link
Closed
Labels
Description
Output of restic version
# restic version
restic 0.7.3
compiled with go1.9 on linux/amd64
How did you run restic exactly?
# cat /etc/restic/files.include
/etc/letsencrypt
/etc/nginx
/etc/ssh
/var/www/nextcloud
/var/data/nextcloud
# cat /etc/restic/files.exclude
# restic backup --files-from /etc/restic/files.include --exclude-file /etc/restic/files.exclude
What backend/server/service did you use?
swift on openstack, also tried with b2.
Expected behavior
Paths are named using an absolute path name, I excepted the full paths to be present in the backup.
Actual behavior
Paths are actually stored using the last part of the path. This causes duplication is my case, for instance:
# restic mount tmp/
Now serving the repository at tmp/
Don't forget to umount after quitting!
# ls -1 tmp/snapshots/2017-10-09T16\:25\:42Z/
letsencrypt
nextcloud
nextcloud-1
nginx
ssh
Do you have an idea how to solve the issue?
I would like an option to store found files under paths with only the leading / removed, mimicking for instance the way that tar handles paths. This makes it easier to find files.
Reactions are currently unavailable