I'm currently backing up mysql by way of dumping the DB to a flat file then
backing up the flat file. Which works well in most cases except when
someone has a database that is bigger than 50% of the hdd. Or really bigger
than around say 35% of the hdd if you account for system files and a
reasonable amount of free space.
I started thinking, mysqldump streams data into a file and then backuppc
streams that file for backup. So why not cut out the middle man file and
just stream right into backuppc? Ive been playing with the backup commands
but im getting some unexpected results due to what I believe is my lack of
total understanding of how backuppc actually streams things.
So my overall question is. Does anyone have any clues or hints or ideas on
a way to modify the backup command such that it calls either mysqldump or a
script that would generate a file stream at backup time into the backuppc
tunnel?
So far using the tar backup method seems to be the best idea, I tried
modifying the tar command but that seemed to screw with the backuppc server
side. so it looks like im gonig to have to just add something to the tar
command so it streams the file into the backuppc tar command(as opposed to
replacing the tar command).
Lawrence
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
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/
