Hello,
interesting. Thanks for your reply.
My backups take longer. Much longer. My last incremental
took nearly 280 minutes for about 600 MB. This is over a 54 Mbit Wlan
connection. But even over this connection 600MB are transferable in a fraction
of 280 minutes... I really don't know what's the problem.
Have you checked, how much time you save by splitting the
backup?
Greetings,
Hendrik
I actually do this on my tru64 unix and my sco unix machines.
This works quite well. It also uses up way less RAM with rsync, which is
good because some of the tru64 machines don't have a lot of extra RAM.
I have one specific tru64 alpha 4cpu machine that I have 4 hosts setup
for and I trigger all 4 hosts for backup at the same time with cron as they
are 1Ghz cpus and I can peg all 4 and complete backupps much quicker as my
scsi disk array is much much faster that the cpus can handle. I have one
backup the / with exclusions for each directory I will backup with one of the
other backups, then the other machines are backing up all the other
directories. I just did some guess work on how to split it up
efficiently by comparing file count and then filesize. This works very
well and I can get an incremental backup done in about 20 minutes and a full
in under an hour. its about 12GB worth of data, but an alpha es45 is not
exactly the fastest machine around these days. I also dont have many
files that change, maybe 100, but a few of them are 1GB+ each day.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php _______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|