On Sun, Jul 8, 2012 at 9:59 PM, Kenneth Porter <sh...@sewingwitch.com> wrote:
> I've got a user running Win7-64 with 3 large drives: C (original boot), D
> (data), and G (Win7 boot). I've configured rsyncd on it to serve them as 3
> modules named for the drive letters. A "full" backup to my CentOS 5 box
> takes about 40 hours, and an "incremental" takes about 8, so I've
> configured his system to only back up on weekends. But even then, he often
> works weekends and will reboot his machine because it's running slow from
> the backup load, killing the backup.
>
> What can I do to optimize the backup to reduce the time taken so it's more
> likely to run to completion? I was thinking I could reconfigure it to be
> three hosts with one drive each, so that there's more chance of running to
> completion.
Splitting the runs should help. You might even want to look at the
directory contents and split at the subdirectory level. Other than
sheer voulme, the things that can make rsync slow are very large
numbers of files where handling the directory listing becomes
cumbersone, and very large files with changes where the server has to
reconstruct a full copy with bits from the old and bits from the
transfer. An incremental against a fairly recent full should run
about as fast as both systems can read the directory contents, though.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
