rustic currently saves the file # of links, as restic does. Other support for hard links is missing.
Restic uses the information of # of links and more (like device id) to (try to) restore hard links during restore. This so far only works for files within the restore and poses other problems, see restic/restic#3041 (comment).
Correct treatment of hard links during backup and restore is hard, but should be better supported. For instance:
- Save more/better information in the metadata during
backup.
- Provide various options in
restore to suit user's needs for restoring hard links.
rustic currently saves the file # of links, as restic does. Other support for hard links is missing.
Restic uses the information of # of links and more (like device id) to (try to) restore hard links during restore. This so far only works for files within the restore and poses other problems, see restic/restic#3041 (comment).
Correct treatment of hard links during backup and restore is hard, but should be better supported. For instance:
backup.restoreto suit user's needs for restoring hard links.