Submit your breaking news stories and original articles to us by contacting us
MySQL Backup
Saturday, May. 8 2004 | Author: milbertusWhen I backup my blog every few days, I log in to my host’s CPanel, navigate to the right page, and click the links to download the .tar.gz files for each of my MySQL databases. While this does work, to say the least it’s annoying to have to go to the site every couple of days, click the links, and wait for the files to download (hey, what can I say, I’m lazy).
That all changes now that I’ve started using MySQL Backup. Not only will it let you set up profiles to easily backup databases, but you can also schedule database backups at regular intervals. No more manual backing up for me, now it can all be done automatically. Plus, this way I can’t forget, which is even better.
Via Digital Media Minute.
Category: Uncategorized
10 Responses for "MySQL Backup"
May 8th, 2004 at 2:35 pm
1Anyone have a OSX version of an app like this?
May 8th, 2004 at 2:45 pm
2Possibly: DataWerkz
May 8th, 2004 at 5:18 pm
3You don’t need to buy or install any fancy software to back up MySQL, not even on OS X. Andy Budd covered this some time and yours truly added a few notes that might be worthwhile.
May 8th, 2004 at 7:14 pm
4great… now does anyone have any good tips on moving a 200+ meg mysql database from one remote server to another? I’m looking at doing that soon and it terrifies me. :-)
but I definitely need to start making backup dumps of stuff.. everything but the DB gets backed up and the DB is the thing that really NEEDS to be backed up because it’s the only thing that changes without the same changes happening on my PC….
May 8th, 2004 at 7:21 pm
5What, you don’t like the option of exporting the dump file from the source database, and just running it on the target database? ;)
I know that it’s fairly simple to copy between databases using ADO .NET (even MySQL using the MySQL ODBC driver), so I’m sure that there are some simple database copy apps out there somewhere. Other than that, I’m not sure what else you could do.
May 8th, 2004 at 7:30 pm
6JC all you have do is configure a master-slave relationship in MySQL between two servers. MySQL will take care of the rest. It’s called replication and is standard stuff with databases.
May 8th, 2004 at 7:31 pm
7Try this JC.
May 8th, 2004 at 9:59 pm
8What, you don’t like the option of exporting the dump file from the source database, and just running it on the target database? ;)
No thanks. heh. For the rest of the databases on the server, it’s not a big deal, they don’t get much bigger than 10 megs or so… but that damned phpbb database for my writing forum site is *huge*
When I’m using phpMyAdmin, it times out before it can create a dump… I’ve never tried it from the command line so I don’t know how that’ll work.
I konw about replication, we use it a bit at work with MSSQL, but I’m not sure here… it’s two servers but I’m fairly sure you can only access either of them from localhost since they’re remotely hosted. I’m moving all my sites from a VPS to a full dedicated server.
May 9th, 2004 at 1:17 pm
9JC: Dumping from the command line won’t time time out and, even for a large database, will probably turn out to be quicker than you expect.
As for the remotely hosted servers - as long as you have two IP addresses you can successfully replicate - even if one of those IP addresses is a local one.
March 18th, 2006 at 3:09 am
10thx
RSS feed for comments on this post
Leave a reply