Hi, I know the current method of handling the backup of a database is to run a special job just before the main backup which dumps the database out to a file. This file is then backed up as normal.
The trouble with this approach is that even if one small record has been modified the whole database has to be transferred over the network. Small databases are no problem but if an incremental backup has to transfer a few hundred megabytes every day this will soon add up to a hefty bill. I also know that if I used 'rsync' it is clever enough to only transfer the changes and thus keep network transfers to a minimum. You know what I'm going to say next :-) Are there any plans to give the client file daemons the ability to transfer just the differences instead of the whole file? I guess one 'solution' would be to rsync the database to a local machine and back that up instead... but it's not as neat and you would have to get the timing right so that the rsync'd copy is available as close to backing it up as possible. David Legg ------------------------------------------------------------------------- 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/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
