Re: Backing up MySQL using PHPMyAdmin problem with UTF-8

I managed to use the older version of MySQL Administrator 1.2.15 and it appears to back up find using InnoDB online backup. On Thu, Oct 14, 2010 at 6:56 PM, Michael Dykman wrote: > I have had this problem with PHPMyAdmin many times, and the only way I > know around it, is to go in and do your d

Re: Backing up MySQL using PHPMyAdmin problem with UTF-8

Oh this isn't good. Because the database in on a shared server and I don't think I've got console access ? On Thu, Oct 14, 2010 at 6:56 PM, Michael Dykman wrote: > I have had this problem with PHPMyAdmin many times, and the only way I > know around it, is to go in and do your dump at the consol

Re: Backing up MySQL using PHPMyAdmin problem with UTF-8

I have had this problem with PHPMyAdmin many times, and the only way I know around it, is to go in and do your dump at the console. PHP does not deal with UTF very well. - michael dykman On Thu, Oct 14, 2010 at 5:48 AM, Tompkins Neil wrote: > Hi, > > I'm using PHP MyAdmin to backup my MySQL d

Re: Backing up the InnoDB tables

> The problem is I don't have any command line access, just direct MySQL > access to the database tables. > > whats wrong with mysqldump? -- bEsT rEgArDs| "Confidence is what you have before you tomasz dereszynski | understand the problem." -- Woody Allen

Re: Backing up the InnoDB tables

Quoting Tompkins Neil : The problem is I don't have any command line access, just direct MySQL access to the database tables. I dont know xtra backup, but if thats not an option you can just use mysqldump. This can be run from a remote server to your DB server, just using MySQL network ac

Re: Backing up the InnoDB tables

The problem is I don't have any command line access, just direct MySQL access to the database tables. On Wed, Oct 13, 2010 at 1:19 PM, Suresh Kuna wrote: > use xtra backup > > On Wed, Oct 13, 2010 at 5:37 PM, Tompkins Neil < > neil.tompk...@googlemail.com> wrote: > >> Would really appreciate som

Re: Backing up the InnoDB tables

use xtra backup On Wed, Oct 13, 2010 at 5:37 PM, Tompkins Neil wrote: > Would really appreciate some help or suggestions on this please, if anyone > can assist ? > > Regards > Neil > > -- Forwarded message -- > From: Tompkins Neil > Date: Tue, Oct 12, 2010 at 5:45 PM > Subject:

RE: Backing up via slave

[EMAIL PROTECTED] > Sent: Wednesday, January 02, 2008 14:06 PM > To: Martijn van den Burg > Cc: Martin Goldman; mysql@lists.mysql.com > Subject: Re: Backing up via slave > > Hi Martijn, > Master will not have any information of SLAVE how r u doing > this in you second s

Re: Backing up via slave

Hi Martijn, Master will not have any information of SLAVE how r u doing this in you second step. "- check the master servers to find out the names/ports of their slaves" regards anandkl On 1/2/08, Martijn van den Burg <[EMAIL PROTECTED]> wrote: > > Hi Martin, > > > Hi folks, > > > > I have two My

RE: Backing up via slave

Hi Martin, > Hi folks, > > I have two MySQL servers running in a master-slave > configuration, and I want to set up a process for backing up > our application's data in which backups are sent to a server > at another location. Ideally, I'd like to do a full backup > once a week, and then incr

Re: Backing up via slave

Thanks Baron. That actually looks like a pretty useful tool for monitoring replication -- I'll have to give that a shot. I did use ZRM once a few years ago, and I even thought about trying to use it this time around, but I couldn't find anything in the docs that explicitly described my particular

Re: Backing up via slave

Hi, On Dec 24, 2007 1:35 AM, Martin Goldman <[EMAIL PROTECTED]> wrote: > Hi folks, > > I have two MySQL servers running in a master-slave configuration, and I want > to set up a process for backing up our application's data in which backups > are sent to a server at another location. Ideally, I'd

Re: Backing up large dbs with tar

You have many options like the people below just suggest... 1 - Use mysqldump 2 - Use mysqlhotcopy or 3 - do the mysqlhotcopy/mysqldump yourself Since I found that neither 1 nor 2 gives exactly a perfect result in many backup scheme alone. I started working on something that complement 1 and 2 t

Re: RE: Backing up large dbs with tar

nday, November 13, 2006 12:39 PM To: Van Cc: mysql@lists.mysql.com Subject: Re: Backing up large dbs with tar Van, I'll second what Gerald said about mysqlhotcopy. When we first began using MySQL at my last job, we had terrible problems with MySQL crashing. Turned out to be due to a 3rd par

RE: Backing up large dbs with tar

Is mysqlhotcopy still considered "beta"? We steered clear of it for production use for that reason. Tim -Original Message- From: Dan Buettner [mailto:[EMAIL PROTECTED] Sent: Monday, November 13, 2006 12:39 PM To: Van Cc: mysql@lists.mysql.com Subject: Re: Backing up large db

Re: Backing up large dbs with tar

Van, I'll second what Gerald said about mysqlhotcopy. When we first began using MySQL at my last job, we had terrible problems with MySQL crashing. Turned out to be due to a 3rd party backup process attempting to lock and read the database files while MySQL was attempting to use them. Using mys

Re: Backing up large dbs with tar

Van wrote: Greetings: I have a 600M data file that never gets backed up. The following error occurs in the cron job: tar: /data/mysql/"my_db_name"/"my_large_table_name".MYI: file changed as we read it Is there a way I can set this one table to read-only prior to the backup without affect

Re: Backing Up Database and All Tables

Hello See some of this: MySQL Snap 2.1 http://3d2f.com/programs/2-075-mysql-snap-download.shtml Backup Watcher for MySQL 1.8.3 http://3d2f.com/programs/4-919-backup-watcher-for-mysql-download.shtml MySQL Dump Timer 1.2.4 http://3d2f.com/programs/12-670-mysql-dump-timer-download.shtml MySQLBackup

Re: Backing Up Database and All Tables

Hello. > It looks like there is something called a InnoDB Hot Backup that is a = > perl script. Is this something that Mysql offers, or is it something one = > needs to purchase. InnoDB Hot Backup is a good tool. Have a look here: http://www.innodb.com/order.php But mysqldump is very

Re: Backing up live MySQL Databases

We never dump the data just shutdown the slave, copy the data directory and restart the slave. This practice is trustworthy probably only where the servers are running on the same platform, mysql server version and operating system. -Kieran ___

RE: Backing up live MySQL Databases

well and has been in use for more than a year on a 60gig+ database. It does have the cost of requiring some extra hardware of course. John A. McCaskey -Original Message- From: Glennie Vignarajah [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 10:50 AM To: mysql@lists.mysql.com

RE: Backing up live MySQL Databases

ting the server down and copying the files. Cheers, -Dana -Original Message- From: Glennie Vignarajah [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 12:50 PM To: mysql@lists.mysql.com Subject: Re: Backing up live MySQL Databases Le Thursday 16 June 2005 17:06, Jeff McKeon(&q

RE: Backing up live MySQL Databases

Yes, that's the way we currently do it but we were looking for more options. Jeff > -Original Message- > From: Kieran Kelleher [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 16, 2005 11:26 AM > To: Jeff McKeon > Cc: mysql@lists.mysql.com > Subject: Re: Backing

Re: Backing up live MySQL Databases

Le Thursday 16 June 2005 17:06, Jeff McKeon("Jeff McKeon" <[EMAIL PROTECTED]>) disait: Hello, > Anyone using any third party products like Arkeia that enable you > to do a live backup of MySQL database? I've tried Arkeia few months ago. The online backup and restore of MySql databases worked

Re: Backing up live MySQL Databases

I have a master-slave replication setup. A scheduled backup script on the slave runs automatically at regular intervals. The script slave does this: shutdown the mysql server on the slave backup the mysql data directory to backup media restart the mysql server on the slave. Using a setup like t

Re: backing up Databases in Mysql

Nestor, 1. LOCK TABLES; FLUSH TABLES; (allow reads, stall writes) 2. Copy the db dir 3. UNLOCK TABLES; 4. cd datadir mv mysql.log mysql.old mysqladmin flush-logs PB Nestor Florez wrote: TO back up the databases in Mysql, isn't there a way where you can just copy somefiles to another direc

Re: backing up Databases in Mysql

On Friday 18 February 2005 11:28 am, Nestor Florez wrote: > TO back up the databases in Mysql, isn't there a way where you can just > copy somefiles to another directory and in essence you have a backup? I > thought I read this somewhere mysqlhotcopy does this for myisam tables, there is a hot c

RE: Backing up directly to tape.

I have seen people dump the database with mysqldump and then use a cpio command to write the files to the tape device... -Erich- -Original Message- From: Egor Egorov [mailto:[EMAIL PROTECTED] Sent: Monday, September 06, 2004 4:35 AM To: [EMAIL PROTECTED] Subject: Re: Backing up

Re: Backing up directly to tape.

"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote: > I have been searching the archives and was unable to find an answer. > > I need the ability to backup MySQL instances directly to a tape device. > > Currently, I run a mysqldump to disk and have legato pick up the file. = > As I get to some larger

Re: Backing up directly to tape.

How about mysqldump > /dev/nst0 Tucker, Gabriel wrote: Hello All I have been searching the archives and was unable to find an answer. I need the ability to backup MySQL instances directly to a tape device. Currently, I run a mysqldump to disk and have legato pick up the file. As I get to some l

Re: Backing Up a Database

--- From: "McKeever Chris" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 04, 2004 8:39 PM Subject: Re: Backing Up a Database > > > On Fri, 4 Jun 2004 18:16 , Lou Olsten <[EMAIL PROTECTED]> sent: > > >For the time I've been te

Re: Backing Up a Database

On Fri, 4 Jun 2004 18:16 , Lou Olsten <[EMAIL PROTECTED]> sent: >For the time I've been testing, I've used the procedures outlined in the help to take >my backups, which entails doing a FLUSH TABLES WITH READ LOCK in my MySQL monitor, then going to a shell prompt and executing the mysqldump u

Re: Backing up InnoDB MySQL DB

Victoria Reznichenko wrote: ColdFusion Lists <[EMAIL PROTECTED]> wrote: we're using MySQL 4.0.12 with InnoDB... please do you have any scripts, comments, suggestions, ideas, tutorials... about how to backup from that DB? It's possible to? You can use mysqldump utility that comes with MySQL distri

Re: Backing up InnoDB MySQL DB

ColdFusion Lists <[EMAIL PROTECTED]> wrote: > > we're using MySQL 4.0.12 with InnoDB... please do you have any scripts, comments, > suggestions, ideas, tutorials... about how to backup from that DB? It's possible to? > You can use mysqldump utility that comes with MySQL distribution: ht

Re: Backing up InnoDB MySQL DB

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 26 May 2004 02:34 pm, ColdFusion Lists wrote: > we're using MySQL 4.0.12 with InnoDB... please do you have any scripts, > comments, suggestions, ideas, tutorials... about how to backup from that > DB? It's possible to? If you can afford t

Re: secure automated access (was "Re: Backing up all databases")

On Monday, November 17, 2003, at 11:51 AM, Michael Stassen wrote: I'm glad this worked for you, but now I'm confused. The manual clearly indicates the use of quotes around the password. See . The "typical user option file" starts with [clien

Re: secure automated access (was "Re: Backing up all databases")

Ed Leafe wrote: On Monday, November 17, 2003, at 02:58 AM, Michael Stassen wrote: cat $HOME/.my.cnf [client] password="rootpassword" /usr/local/mysql/bin/mysql --defaults-file=$HOME/.my.cnf ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) Oh. That changes things.

Re: secure automated access (was "Re: Backing up all databases")

> >> In the case of root cron jobs then, you need a .my.cnf readable only by >> root in root's home. It should include >> >> [client] >> password="mysql_root_password" > > This is incorrect, unless the double quotes are part of the password. > Removing them so that the entry reads: > > [clien

Re: secure automated access (was "Re: Backing up all databases")

>> >> Mac OS 10.2.3. Maybe Panther has an issue with the build? > > 10.2.3 is Jaguar, not Panther. Did you mean 10.3.x? As I said, I'm > running mysql 4.0.16 on Mac OS 10.2.8, and this works for me. I suppose > an issue with Panther is possible, though I'd be surprised if something > simple l

Re: secure automated access (was "Re: Backing up all databases")

On Monday, November 17, 2003, at 02:58 AM, Michael Stassen wrote: cat $HOME/.my.cnf [client] password="rootpassword" /usr/local/mysql/bin/mysql --defaults-file=$HOME/.my.cnf ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) Oh. That changes things. The error says "U

Re: secure automated access (was "Re: Backing up all databases")

Randall Perry wrote: Mysterious. I assume `mysql -p` prompts you for root's password and works as expected, since without -p it says you're not using a password, rather than saying there's something wrong with the password. Yes, that works. When you tried the defaults-file option, did you use t

Re: secure automated access (was "Re: Backing up all databases")

> Mysterious. I assume `mysql -p` prompts you for root's password and > works as expected, since without -p it says you're not using a password, > rather than saying there's something wrong with the password. > Yes, that works. > When you tried the defaults-file option, did you use the full pa

Re: secure automated access (was "Re: Backing up all databases")

Mysterious. I assume `mysql -p` prompts you for root's password and works as expected, since without -p it says you're not using a password, rather than saying there's something wrong with the password. When you tried the defaults-file option, did you use the full path? That is, mysql --def

Re: secure automated access (was "Re: Backing up all databases")

on 11/13/03 3:57 PM, Michael Stassen at [EMAIL PROTECTED] wrote: > The client (mysql) reads the .my.cnf file when you start it, so > restarting mysqld and relogging in as root are not necessary. > > Let's see if I have this straight: While logged in as root, you created > .my.cnf in root's home d

Re: secure automated access (was "Re: Backing up all databases")

The client (mysql) reads the .my.cnf file when you start it, so restarting mysqld and relogging in as root are not necessary. Let's see if I have this straight: While logged in as root, you created .my.cnf in root's home directory. This file contains the password for the mysql user "root". Ye

Re: secure automated access (was "Re: Backing up all databases")

I created the .my.cnf file in root's home dir, added the directives below setting the correct password. Restarted mysqld, re-logged in as root, but nothing works. It's not getting the password. > The simplest solution is to keep the password in the .my.cnf file in > your home directory. See http

Re: secure automated access (was "Re: Backing up all databases")

That sounds like the solution. Thanks for your help, everyone. > The simplest solution is to keep the password in the .my.cnf file in > your home directory. See http://www.mysql.com/doc/en/Option_files.html > in the manual. > > In the case of root cron jobs then, you need a .my.cnf readable on

Re: secure automated access (was "Re: Backing up all databases")

The simplest solution is to keep the password in the .my.cnf file in your home directory. See http://www.mysql.com/doc/en/Option_files.html in the manual. In the case of root cron jobs then, you need a .my.cnf readable only by root in root's home. It should include [client] password="mysql_root_p

Re: Backing up all databases

Then put it in root's .my.cnf file. Randall Perry wrote: Well, this command is running in a cron job -- so that's not an option. Be aware that you password is visible (unix anyway with a "ps -ef"..) when you pass the password like -ppassword. Usually you can enter the password later if you u

Re: secure automated access (was "Re: Backing up all databases")

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan, et al -- ...and then Dan Greene said... % % you could put a shell script as the actual cron job, and make the file only read-able by root, using an environment variable as the password passed (defined in shell script file), so that way even if

RE: Backing up all databases

ssword (if they happen to catch the setting of the env var that's another story, but _much_ less likely) > -Original Message- > From: Randall Perry [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 12, 2003 9:10 AM > To: Cormac Tiernan > Cc: [EMAIL PROTE

Re: Backing up all databases

Well, this command is running in a cron job -- so that's not an option. > > Be aware that you password is visible (unix anyway with a "ps -ef"..) when you > pass the password like -ppassword. Usually you can enter the password later > if > you use > usr/local/mysql/bin/mysqldump --opt --all-da

Re: Backing up all databases

Be aware that you password is visible (unix anyway with a "ps -ef"..) when you pass the password like -ppassword. Usually you can enter the password later if you use usr/local/mysql/bin/mysqldump --opt --all-databases -p which avoids the password being visible.. Cormac. On 12-Nov-2003 Randall

Re: Backing up all databases

Ok, I was confused about the password thing. It works now that I'm passing root's password in the command: /usr/local/mysql/bin/mysqldump --opt --all-databases -prootpassword > /usr/local/mysql/data/mysqldump > You're joking, right? (Perhaps you thought the original question was a > joke, too, a

Re: Backing up all databases

You're joking, right? (Perhaps you thought the original question was a joke, too, as root normally has access to all dbs?) As I understand the manual , that will give root access to every db, from every host except localhost, with no password! I can't i

RE: Backing up all databases

Look at GRANT on mysql.com GRANT ALL PRIVILEGES ON *.* TO root@'%' IDENTIFITED BY ''; - Dathan Vance Pattishall   - Sr. Programmer and mySQL DBA for FriendFinder Inc.   - http://friendfinder.com/go/p40688 -->-Original Message- -->From: Randall Perry [mailto:[EMAIL PROTECTED] -->Sent: T

Re: Backing up all MySQL DBs

On Tue, Sep 09, 2003 at 06:47:52AM -0700, Will Glass-Husain wrote: > > > There's also > > # backup databases > for dbname in `echo 'show databases;' | mysql -u$dbuser -p$dbpassword` > do > echo "Backing up database $dbname..." >> > $destdir/backup.log > mysqldum

Re: Backing up all MySQL DBs

ir/db_$dbname.zip - >> $destdir/backup.log done WILL [EMAIL PROTECTED] - Original Message - > From: "Mike Hillyer" <[EMAIL PROTECTED]> > To: "René Mølsted" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Monday, September 08, 2003 9:02 PM

RE: Backing up all MySQL DBs

Sure, use the --all-databases option instead of $DBNAME http://www.mysql.com/doc/en/mysqldump.html Regards, Mike Hillyer www.vbmysql.com > -Original Message- > From: René Mølsted [mailto:[EMAIL PROTECTED] > Sent: Monday, September 08, 2003 11:51 AM > To: [EMAIL PROTECTED] > Subject: Back

RE: backing up

Hi, > is there a way to remotely grab the databases (ie mysqldump) > and have it > place everything in a different file for every database? or > has anyone > written a script to do something like this? There's propably a more refined way to do this, but this simple hack should do the trick. (

RE: backing up mySQL database ?

> -Original Message- > From: Neil Tompkins [mailto:[EMAIL PROTECTED]] > Can anyone recommend a software app. I could buy to be able > to dump data and > table structures to a text file. Ideally as mentioned before > I need to run > this on a hourly basis. Backing up the entire data

Re: backing up mySQL database ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Neil, et al -- ...and then Neil Tompkins said... % % Hi Hi! % % Thanks for that information. But I think I want to purchase a software % application, due to my lack of knowledge for mySQL. In addition to this, % my ISP doesn't allow that much

Re: backing up mySQL database ?

a and table structures to a text file. Ideally as mentioned before I need to run this on a hourly basis. Rgds, Neil From: "Gerald R. Jensen" <[EMAIL PROTECTED]> Reply-To: "Gerald R. Jensen" <[EMAIL PROTECTED]> To: "Neil Tompkins" <[EMAIL PROTEC

Re: backing up mySQL database ?

crontab: # Make backups of databases at 4am daily 0 4 * * * /usr/local/bin/mydbbak.sh - Original Message - From: "Neil Tompkins" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, November 30, 2002 12:11 PM Subject: Re: backing u

Re: backing up mySQL database ?

; <[EMAIL PROTECTED]> To: "Neil Tompkins" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Subject: Re: backing up mySQL database ? Date: Sat, 30 Nov 2002 10:23:22 -0600 You don't have to develop or buy anything. You can use mysqldump in conjunction with a shell script to do what

Re: backing up mySQL database ?

You don't have to develop or buy anything. You can use mysqldump in conjunction with a shell script to do what you want, and automate it with either the Windows Scheduler (on Win32) or a cronjob (Linux, *nix). - Original Message - From: "Neil Tompkins" <[EMAIL PROTECTED]> To: <[EMAIL PROTEC

Re: backing up mySQL database ?

I might be totally off track here, but a simple shell script works fine for me. /bin/sh, tar, and cron are a powerful team. --Joe -- Joe Stump Affordable Computers, Inc. 800-864-2345 x113 - Original Message - From: "Neil Tompkins" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturd

Re: Backing up InnoDb

Hendrik, - Original Message - From: ""Hendrik Schalekamp"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Tuesday, June 18, 2002 11:12 AM Subject: Backing up InnoDb > Hi, > > I'm just trying out the hotbackup utility (http://www.innodb.com/hotbackup.html) > for a MySql Inn

Re: RE: Backing up/Creating new database

PR, Monday, May 13, 2002, 8:28:20 PM, you wrote: P> Thnaks . I tried several variation and they are giving me sql syntax P> error: :) mysqldump is not an SQL command, it's a program for database backup. So, you should run it from DOS prompt, f.e. if MySQL is located in C:\mysql, it would be:

RE: Backing up/Creating new database

- From: Victoria Reznichenko [mailto:[EMAIL PROTECTED]] Sent: Monday, May 13, 2002 11:32 AM To: [EMAIL PROTECTED] Subject: Re: Backing up/Creating new database PR, Monday, May 13, 2002, 5:47:23 PM, you wrote: P> I have database developed on my laptop. What is the quickest way to P> backup the

RE: Backing up/Creating new database

The easiest way is simply to copy the files. Go to the directory that mysql was installed to. There should be a subdirectory called data. Under that should be a subdirectory named after your database. You can simply copy that entire subdirectory to a mysql server and the database will be copied ov

Re: Backing up/Creating new database

PR, Monday, May 13, 2002, 5:47:23 PM, you wrote: P> I have database developed on my laptop. What is the quickest way to P> backup the database and restore it on the server? Can I restore the P> database as empty database? Howa bout creating SQL statements based on P> the database structure? mysq

Re: Backing up specific tables or content

Raphael, Friday, April 12, 2002, 12:02:16 PM, you wrote: RDC> I would like to dump some tables, and also some fields of a given table but RDC> not all of them, from my database. I understand that mysqldump creates a dump RDC> of the whole database and not a part of it. How can I do that ? RDC>

Re: **Backing Up A Database**

g purposes, you may also just call /etc/cron.daily/logrotate by hand from the commandline. Felix -Ursprüngliche Nachricht- Von: Alexander Shaw [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 20. Februar 2002 01:15 An: MySQL List; Felix Richter Betreff: RE: **Backing Up A Database** Hi Felix

RE: **Backing Up A Database**

y are working correctly? Alex -Original Message- From: Felix Richter [mailto:[EMAIL PROTECTED]] Sent: 18 February 2002 15:26 To: David yahoo; mySQL List Subject: Re: **Backing Up A Database** - create a file in /etc/logrotate.d, filename does not matter, take this as a template, fi

Re: **Backing Up A Database**

- create a file in /etc/logrotate.d, filename does not matter, take this as a template, fill in connection parameters in mysqldump call (""): /home/backup/sqlback/mybackup.sql { daily nomissingok nocreate compress rotate 14 errors [EMAIL PROTECTED] prerotate

Re: **Backing Up A Database**

How did u do exactly ? It's not documented. Does it take a long. Do u have to flush and lock tables before, that can be critical for 24/24 server. what conf for logrotate ? a+. >I personally issue "mysqldump"s via cron and maintain the files using "logrotate" (Redhat Linux), which >automatic

Re: **Backing Up A Database**

Please see http://www.mysql.com/doc/B/a/Backup.html I personally issue "mysqldump"s via cron and maintain the files using "logrotate" (Redhat Linux), which automatically zips and rotates them. - Before posting, please check:

Re: Backing up a MySQL database on a remote server

Hi, There was allot left un-said:-) assuming you can not get access to the command line dump. select * from your_table_name into outfile "your_home_dir/your_filename"; This will create a text file. Now download these files and save them. reverse load data infile "your_home_dir/your_filename"