On Thu, 2005-12-29 at 19:54, Brendan Simon wrote: > I would have thought that subsequent "full" backups would still use > rsync, but the results saved as full files rather than deltas or only > changed files.
Yes, rsync should send only the differences and new files when you do a subsequent full. At the backppc server end, all files that are identical, whether found on different machines or subsequent runs of the same machine, end up being a link to one copy of the data. > If my understanding of the backuppc architecture is correct, then I > don't see the point of doing "full" backups in the sense of transferring > all the files accross the network. With transports other than rsync, that is necessary to be sure you have a full copy of the all files. For example, none of the others will pick up old files in their new positions under a renamed directory using their incremental modes. > Is there a way to setup backuppc to always use rsync to send file > deltas, and to limit the transfer between a start and end time of day > (eg. 12am to 4am) ?? I believe the answer is yes. Maybe that's what > you mean by backup window ;-) You can control the start time, but once started it will continue until the run is complete unless you manually stop it. > If the backup does not complete, then the next backup period will get > further along, until eventually the entire backup is complete. From > then on, only rsync deltas need ever be transferred and "full" backups > can be maintained on the server side in an appropriate manner. rsync > and/or md5 and/or sha1 can be used to check file integrity, etc. That should already be happening. Rsync does transfer the entire directory tree before starting and there is a certain amount of memory overhead per file. If you are short of RAM on the backuppc server, this could make the process very slow. You might have a big improvement if you can break it up into separate runs for individual filesystems or directories. I'm also not sure how well it deals with sparse files. For example if you have a x86_64 Linux machine you might want to see if /var/log/lastlog appears to be a terabyte in size and exclude it if it is. Or, if you have a longer time window on weekends, perhaps you can do fulls then and incrementals on weekdays. Even with rsync the incrementals run faster because files with matching size/timestamps are skiped where in full mode they are all read and compared via rsync's block checksums. This doesn't take much network bandwidth but still takes a lot of time. -- Les Mikesell [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
