MySQL BackUp - 1.1back up MySQL databases |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews
Troubleshooting
Usage Tips
Developer Notes
Commentary
Featured Reviews
brain freeze - Version: 1.0.2, 3/24/2004 11:49AM PST
(1 of 2 users found this comment useful)
grikdog
fast, but - Version: 1.0.2, 3/24/2004 11:16AM PST
COOLFACTOR
When I chose the Tar & Gzip option, not it compressed the file into a series of folders that matched the destination directory, which is odd.
So, if I chose "/Users/myaccount/Backups" as the destination, it would create an archive that contained that folder structure, so when I expand it, I actually have: "/Users/myaccount/Backups/Users/myaccount/Backups/".
Other than that, and the option to add "DROP TABLE", it's a lot better than using phpMyAdmin for backups.
Thanks for a needed app.
So, if I chose "/Users/myaccount/Backups" as the destination, it would create an archive that contained that folder structure, so when I expand it, I actually have: "/Users/myaccount/Backups/Users/myaccount/Backups/".
Other than that, and the option to add "DROP TABLE", it's a lot better than using phpMyAdmin for backups.
Thanks for a needed app.
Most Recent Replies: View All 1 Replies
- fast, but
buggy 



- Version: 1.0.1, 12/5/2003 03:26PM PST
(0 of 2 users found this comment useful)
macubergeek
unuseable
very buggy
very buggy
Correction 



- Version: 1.0.1, 9/6/2003 06:43AM PST
cruzer
I was incorrect in identifying -- as a problem in mysqldump files. In another test this morning I was able to use the files output by this program with no difficulties.
I am submitting a second set of feedback with a much higher rating. For what it does this program works great.
I would be willing to pay for a version which would allow the backups saved, emailed or ftped to remote storage and run as cron jobs.
Thanks for the fine job.
I am submitting a second set of feedback with a much higher rating. For what it does this program works great.
I would be willing to pay for a version which would allow the backups saved, emailed or ftped to remote storage and run as cron jobs.
Thanks for the fine job.
Great start on a needed application 



- Version: 1.0.1, 9/5/2003 07:10PM PST
cruzer
I gave this a try because I was doing backups using mysqldump and finding it a pain. phpMyAdmin is great but won't work for mid to large databases.
Mysqldump turns # comments to -- which means I have to take the file into bbEdit and do the find replace... also it seemed necessary to add in the DROP IF EXISTS, CREATE and USE statements.
Unfortunately when I ran MySQL Backup I got this as the first few lines:
-- MySQL dump 9.07
--
-- Host: localhost Database: officeapp
---------------------------------------------------------
-- Server version 4.0.12-standard
--
-- Current Database: officeapp
--
CREATE DATABASE /*!32312 IF NOT EXISTS*/ officeapp;
The -- are in there and why this /*!32312 IF NOT EXISTS*/
This is a good start but much remains to be done?
First... replace those --
Second ... allow for full DROP, CREATE and USE statements
Mysqldump turns # comments to -- which means I have to take the file into bbEdit and do the find replace... also it seemed necessary to add in the DROP IF EXISTS, CREATE and USE statements.
Unfortunately when I ran MySQL Backup I got this as the first few lines:
-- MySQL dump 9.07
--
-- Host: localhost Database: officeapp
---------------------------------------------------------
-- Server version 4.0.12-standard
--
-- Current Database: officeapp
--
CREATE DATABASE /*!32312 IF NOT EXISTS*/ officeapp;
The -- are in there and why this /*!32312 IF NOT EXISTS*/
This is a good start but much remains to be done?
First... replace those --
Second ... allow for full DROP, CREATE and USE statements
Retrospect won't always work - Version: 1.0.1, 5/18/2003 06:57PM PST
ware
Note that if mysqld (the server) is running it isn't a good idea to back up the data set with Retrospect. Retrospect will not handle locking the files and preventing changes while the backup operation is running. You need to either use mysqldump as this program does which works on all table types but is slow, or use mysqlhotcopy (MyISAM tables) or InnoDB Hot Backup (InnoDB tables). I haven't used it, but it looks to be a good wrapper around mysqldump/tar/gzip which is what our backup routine is.
Alternatives - Version: 1.0, 5/14/2003 06:36AM PST
sherlock42
MySQL databases can also be backed up in a couple of other ways:
1. Using the "Export" feature in phpMyAdmin (freeware -- search this site).
2. As part of a complete HD backup, using, for example, Retrospect.
Don't mean to knock this program; just pointing out that it's not the only way to accomplish this goal.
1. Using the "Export" feature in phpMyAdmin (freeware -- search this site).
2. As part of a complete HD backup, using, for example, Retrospect.
Don't mean to knock this program; just pointing out that it's not the only way to accomplish this goal.
Not working... - Version: 1.0, 5/13/2003 06:24PM PST
bahamaen
Doesn't work for me either...
Applescript error. The variable commandLocation is not defined. (-2753)
I get this error both when I try to select a location to save a backup, and click the main backup button.
I have Mac OS X 10.2.6 installed.
Applescript error. The variable commandLocation is not defined. (-2753)
I get this error both when I try to select a location to save a backup, and click the main backup button.
I have Mac OS X 10.2.6 installed.
Most Recent Replies: View All 1 Replies
errors when submitting - Version: 1.0, 5/13/2003 12:04PM PST
pcp_ip
not working for me. trying to backup a local mysql as the root mysql user i get:
Applescript error. The variable commandLocation is not defined. (-2753)
Most Recent Replies: View All 1 Replies
Security - Version: 1.0, 5/13/2003 11:37AM PST
Simon Ganiere
This version of mysql backup don't use ssh or any secure protocol, if you want to do so you can build a SSH Tunnel with a custom port, example: you build a ssh tunnel to mysql.server.com:3306 on localhost:8888 and in the app you put localhost in server and 8888 in port number, I think it will works. But not sure ;) if you have problem or question you can mail me: simon.ganiere@urbanet.ch
Thanks for the question ;) Simon Ganiere (developer of mysqlbackup)
Thanks for the question ;) Simon Ganiere (developer of mysqlbackup)