> >> On 10/15/07, *Toni Van Remortel* <[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> wrote: >> >> >> So I like to change to dumping MySQL with mysqldump. Much cooler, >> but >> how to store those dumps? Should I store them compressed (gzip) >> or not? >> I do use compression in BackupPC through ssh (-C option). >> >> My main concern is bandwidth usage, not local filesystem space. >> So which >> option uses the least bandwidth? >> dan wrote: > if the concern is network bandwidth, compress the sql dump first so > backuppc transfers a compressed and theirfore smaller file accross the > network. that would use the least bandwidth. good luck :) > I suppose if your uncompressed file is 500M which compresses down to 200M, and assuming you are using rsync.
How much data will rsync transfer (incl your ssh level compression) compared to the compressed version of the file? ie, I would assume more of the sections of the file will be identical in the uncompressed rather than the compressed file. Ultimately, if you can test this and let us know your results, that would be helpful for other people (like me :) Currently I compress the sql backups to save disk space on the sql server, but it would be interesting to note which is more efficient bandwidth wise.... Regards, Adam ------------------------------------------------------------------------- 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] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
