synchronising unison backups
Greg Michael <[email protected]> Fri, 18 Apr 2025 13:45:55 +0200
| Newsgroups | gmane.network.unison.general |
|---|---|
| Message-ID | <CALX7XFYqpq3DzBZN8-hTRK_xfGmG+9f1+YzF_sThWo=CaracWg@mail.gmail.com> |
This seems like it should be a useful thing to do, but it's difficult to achieve elegantly. 1. backupdir is the same on both sides, but has different contents (each keeps it own history of overwrites). If synchronised directly, the version numbers would clash. - could get around this by making uniquely named symbolic links to the backupdir on each side, and using those names for syncing. 2. Each time a new backup file is created, the filenames are changed for all previous backup versions, leading to a cascade of updates to be propagated. - if $VERSION in backupprefix could be substituted by $UNIXTIME from the overwritten file's creation time, this would cut the number of these down (I have maxbackups = 10). Sort order would be the same, and there would be no need to update the sequence of filenames. - actually, if $UNIXTIME were used to label the versions, the workaround for 1. would no longer be needed - the differing versions of backupdir would merge cleanly. The logic for cleaning out versions exceeding maxbackups might have to change, but a combined maxbackups total would make sense - the origin of the previous versions shouldn't be important. Anyway, these are just some thoughts. Does anybody else do this? Do you have a good way? Greg To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].