>> I'm also hit by this issue. Is there any prediction as to whether and, if >> so, >> when something is going to happen? :) > > Until such time as the situation with --link-dest changes consider syncing > into an empty directory (if at all possible). > > If you are using rsync for backup then you may wish to take a look at LBackup > <http://www.lbackup.org> or the source code <http://www.lbackup.org/source/>. > > At present LBackup will only keeps a single copy of the previous backup > attempt and this attempt is not referenced or used in any way to reduce > bandwidth for subsequent backup attempts. This approach may change in a > future release of LBackup (eg. keeping a history of previous failed backup > attempts and adding previous failed backup attempts as link-dest paths). > However, at present this is simple approach is employed to ensure that > LBackup is generating a reliable backup snapshot(s). > > In the mean time, hopefully, either LBackup or the source code for the > project will be of assistance.
If anyone has thoughts regarding features mentioned above, such as retention of failed backups and the possible speed improvements which could be gained by using --link-dest with a number of failed backups then please let me know. _______________________________________________ lbackup-discussion mailing list http://www.lbackup.org Change options or unsubscribe : http://lbackup.org/mailing_lists
