Marcin Prejsnar
2014-04-02 21:24:54 UTC
Hi,
Let's assume this common scenario:
- backupPC-4.0.0alpha3, rsync-3.0.6.
- Linux client configured as rsyncd (running as root),
- a week ago you changed some permissions,ownership,acls on dir: /alfa/beta/,
- today you have to recover one file: /alfa/beta/gamma/delta.txt backed up a month ago,
- you are using the most convinient method: recover file at the original location.
- What happens? you lose your last week permission changes.
I tried to analyse BackupPC logs and rsync sources... Not sure, but I think, the only way
to prevent this behavior, is to skip touching any indirect folders if they exists while
recovering files.
If we do change some perms on existing folders while writing recovered files, we have to
restore original state (not from backup, but from the client filesystem).
Is this possible to add this feature to BackuppPC or patch to rsync?
Let's assume this common scenario:
- backupPC-4.0.0alpha3, rsync-3.0.6.
- Linux client configured as rsyncd (running as root),
- a week ago you changed some permissions,ownership,acls on dir: /alfa/beta/,
- today you have to recover one file: /alfa/beta/gamma/delta.txt backed up a month ago,
- you are using the most convinient method: recover file at the original location.
- What happens? you lose your last week permission changes.
I tried to analyse BackupPC logs and rsync sources... Not sure, but I think, the only way
to prevent this behavior, is to skip touching any indirect folders if they exists while
recovering files.
If we do change some perms on existing folders while writing recovered files, we have to
restore original state (not from backup, but from the client filesystem).
Is this possible to add this feature to BackuppPC or patch to rsync?
--
________________
| Pozdrawiam
| Marcin Prejsnar
________________
| Pozdrawiam
| Marcin Prejsnar