On 08/19/2009 05:24 PM, Joshua Jensen wrote: > On Wed, Aug 19, 2009 at 4:52 AM, Alexander 'Leo' > Bergolth<[email protected]> wrote: >> You should be able to use a hardlinking utility like freedup, >> hardlink.py, hardlink or hardlink++ on the destination filespace after >> having backed up with rdiff-backup. > > Yes, but that only solves half the problem. Sure, I could run a > hardlinker util and the *storage* space problem is solved However, > the *transfer* problem isn't solved. When I backup a new machine, all > those files in common are still transferred instead of simply > hardlinked.
You could clone the backup-destination of an existing box before starting the first backup on a new machine. (Untested.) Cheers, --leo -- e-mail ::: Leo.Bergolth (at) wu.ac.at fax ::: +43-1-31336-906050 location ::: IT-Services | Vienna University of Economics | Austria _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
