On Nov 14, 2007, at 11:41 AM, Michael Barrow wrote:
On Nov 14, 2007, at 10:19 AM, Gene Horodecki wrote:
Hi there.. I just did my first big backup with backuppc and to be
honest the results were alittle dissapointing.. It's taken 6 hours
now at approximately 80% CPU to back up my 70Gb photo archive.
Does this sound about right? My entire system is around 240Gb..
at this point I doubt I could do it all in one day. A regular
ntbackup does my photos in about 3 hours.
The way to go for me might be to turn off compression entirely.
Does anyone know if I backuppc will handle this well now that I
have a full backup in place? Or should I delete the backup, set
the compression to zeo, and start over? Thanks!
Totally turn off compression! That will use less CPU and take less
time. You don't want to do gzip compression on image files because
they're not going to compress! I think that if you turn off
compression now, the next backup will snag all of the files again
and write them into the uncompressed pool.
I think I was wrong about the rewriting the files. I reread the docs
(what a concept!) and it says that it's OK to change the compression
value after things have already been written and it will do the right
thing -- that is the hash will work since it's taken of the
uncompressed version of the file.
--
Michael Barrow
michael at michaelbarrow dot name
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
