-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Legg wrote: > 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?
This was a requested project, but I guess you can imagine what /I'm/ going to say next. :) > 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. That's not actually true -- you could do it completely without dealing with timing issues if you made the RunBefore scripts actually take care of all of the tasks that are necessary (do the dump, do an rsync, etc.) Another thing you could do is back up a diff of the database (provided this sort of thing actually works properly on SQL files -- I'm not certain myself, but perhaps this idea can seed someone that knows what they're doing) or something like that. Or, instead of backing up a database dump, backing up logs that can be applied to the database? Just throwing out some ideas. - -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMdpamb+gadEcsb4RAi0hAJ4jKptSKqdXhlzSRkqc8T3CAhKoWQCfbKhU 5xv1Ywnv1dkwx5XCw1PhI7Y= =Wf8Q -----END PGP SIGNATURE----- ------------------------------------------------------------------------- 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
