Hi Richard,
On Tue, 26 Feb 2008, Richard Crane wrote:
I have a ~400GB partition that will take, based on smaller jobs, about
32 hours for the initial copy. I would like to split this into several
partial jobs but there doesn't seem to be any way to join them back
together, so that subsequently I can run a single job to increment
everything.
E.g: source contains
/top/A
/B
/C
[...]
What if I do
rdiff-backup --include /top/A --exclude /top/* source::/top backup/
rdiff-backup --include /top/A /top/B --exclude /top/* source::/top backup/
....
Obviously I'll pick up changes in the prior sections with each successive
jobs, but there will be few changes over the several days this takes.
Or, can I remove the rdiff-backup-data directories at some point and have
rdiff-backup build a new one, once all the files are copied for he first
time?
It's probably slow and wasteful to use rdiff-backup for the initial
mirrors, writing rdiff-backup-data directories that you are just going to
throw away. Mirror the data piecemeal with rsync first, and once it's all
in place, use rdiff-backup --force to create the rdiff-backup-data
directory using the existing files as sources.
Cheers, Chris.
--
_____ __ _
\ __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\__/_/_/_//_/___/ | We are GNU : free your mind & your software |
_______________________________________________
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