Hi,
After following the steps at the following website, I tried to do an online
backup of the cluster.
http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-backup-using-management-client.html
It is a plain vanilla command which is below. The cluster is almost an
empty database, but backup is
On 10/24/2012 11:57 AM, Bheemsen Aitha wrote:
Hi,
After following the steps at the following website, I tried to do an online
backup of the cluster.
http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-backup-using-management-client.html
It is a plain vanilla command which is below. The
Just for others to know, it was the memory problem. I re-set the memory
parameters for ndbmtd (two nodes) to minimum. Then I could run the backup
successfully.
Thanks
BA
On Wed, Oct 24, 2012 at 11:57 AM, Bheemsen Aitha pgb...@motorola.comwrote:
Hi,
After following the steps at the following
MySQL Administrator 1.2.15 is fails with the same problem. Do anyone have
any other suggestions ?
-- Forwarded message --
From: Tompkins Neil neil.tompk...@googlemail.com
Date: Fri, Oct 15, 2010 at 11:21 AM
Subject: 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 mdyk...@gmail.com 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
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 mdyk...@gmail.com wrote:
I have had this problem with PHPMyAdmin many times, and the only way I
know around it, is to go
Hi,
I'm using PHP MyAdmin to backup my MySQL database. The database is of
type InnoDB
and encoding used is utf8_unicode_ci. The variables are set as follows :
*MySQL connection collation: **utf8_unicode_ci*
*MySQL charset: **UTF-8 Unicode (utf8)*
*character set client: utf8*
*character set
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
neil.tompk...@googlemail.com wrote:
Hi,
I'm using PHP
Would really appreciate some help or suggestions on this please, if anyone
can assist ?
Regards
Neil
-- Forwarded message --
From: Tompkins Neil neil.tompk...@googlemail.com
Date: Tue, Oct 12, 2010 at 5:45 PM
Subject: Backing up the InnoDB tables
To: [MySQL] mysql@lists.mysql.com
...@googlemail.com
Date: Tue, Oct 12, 2010 at 5:45 PM
Subject: Backing up the InnoDB tables
To: [MySQL] mysql@lists.mysql.com
Hi
On a shared MySQL server with access just to my own database, what is the
recommend backup methods and strategies for the InnoDB tables ?
Cheers
Neil
--
Thanks
Suresh Kuna
really appreciate some help or suggestions on this please, if anyone
can assist ?
Regards
Neil
-- Forwarded message --
From: Tompkins Neil neil.tompk...@googlemail.com
Date: Tue, Oct 12, 2010 at 5:45 PM
Subject: Backing up the InnoDB tables
To: [MySQL] mysql@lists.mysql.com
Quoting Tompkins Neil neil.tompk...@googlemail.com:
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,
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
Hi
On a shared MySQL server with access just to my own database, what is the
recommend backup methods and strategies for the InnoDB tables ?
Cheers
Neil
Hi Tim,
On Mon, Jun 22, 2009 at 4:41 PM, Little,
Timothytlit...@thomaspublishing.com wrote:
We have a 20 gig db (that includes the MYIs and MYDs and FRMs).
We are wondering how long LVM snapshots take.. in that how long might
the DB be read-locked? Do we have to read-lock it and flush
We have a 20 gig db (that includes the MYIs and MYDs and FRMs).
We are wondering how long LVM snapshots take.. in that how long might
the DB be read-locked? Do we have to read-lock it and flush tables?
Are we talking half a second, ten-seconds, 20 minutes?
Currently, when we copy the raw files
Hi Tim,
We use LVM snapshots all the time. They are essentially
instantaneous with our 90GB innodb database files.
A command to generate the snapshot could be:
sudo /usr/sbin/lvcreate --snapshot --name mysqlsqlbackup --size 15G /
dev/system/data01
Please let me know if you have any
What we do to start is the following:
) open 2 windows to the server running the mysql instance
) in one window,
) run the mysql cli and issue command 'flush tables with read lock'
) stop the slave, if this is a running slave
) run either show master status or show slave status,
Little, Timothy wrote:
We have a 20 gig db (that includes the MYIs and MYDs and FRMs).
We are wondering how long LVM snapshots take.. in that how long might
the DB be read-locked? Do we have to read-lock it and flush tables?
Take a look at mylvmbackup which takes care of flushing tables,
Backing up MySQL using file system snapshots
http://forge.mysql.com/wiki/Backing_up_MySQL_using_file_system_snapshots
This Thursday (February 26th, 14:00 UTC), Lenz Grimmer will give a MySQL
University session on Backing up MySQL using file system snapshots. Lenz
is a member of the MySQL
]
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 step.
- check the master servers to find out
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
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 incremental backups every 6 hours. It
seems to make the most
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 incremental backups every 6 hours
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 like
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 incremental backups every 6 hours. It seems
to
make the most sense for this to happen on the slave. I was thinking it
could
work something
Hello,
I'm using CentOS 4.5 with MySQL 4.1.20. I've got 2G RAM on the system,
and am running an x86_64 kernel (2.6.9-55.0.9.EL). When I try to use
mysqldump, MySQL crashes (then restarts). Here is the output from
mysqldump, and what happens in /var/log/mysql.log.
From mysqldump:
Hi Guys,
I encounter an issue once I backup the database.
mysqldump -u admin -phost --databases message_tracker z:sqlbackup.sql
mysqldump: Got error: 1044: Access denied for user 'admin'@'localhost'
to database 'message_tracker' when using LOCK TABLES
I am using windows as the OS.
Any
Looks like this user does hot have permission on message_tracker while
connecting on the local host.
try this.
grant all on message_tracker to 'admin'@'localhost' identified by
'password';
and then try you mysqldump
regards
anandkl
On 7/19/07, Banyan He [EMAIL PROTECTED] wrote:
Hi Guys,
I
Thx Ananada. Actually, I don't have the admin permission on this server.
The grant command is unavailable for me. I have no ideas about this. I
install the software on two machines, one of them can issue this command
and works fine with it. Another cannot.
OS: windows 2003
Cheers,
Ananda
You mean to say, you cannot execute the GRANT command.
regards
anandkl
On 7/19/07, Banyan He [EMAIL PROTECTED] wrote:
Thx Ananada. Actually, I don't have the admin permission on this server.
The grant command is unavailable for me. I have no ideas about this. I
install the software on two
Yes, the server shows me that. I cannot execute the grant command.
This is a serious restriction software works with mysql.
Ananda Kumar wrote:
You mean to say, you cannot execute the GRANT command.
regards
anandkl
On 7/19/07, *Banyan He* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
You cannot execute the grant command because you don't have permission
to do so.
The GRANT command allows you to set permissions on databases and tables,
thereby giving access to possibly sensitive data.
It is in no way a serious restriction, it is a very important security
feature.
If you
The question is in this server, I cannot backup the database by issuing
mysqldump. On another server, I can. I am sure nobody changes the
settings. That's confusing to me.
ant command because you don't have permission to do so.
The GRANT command allows you to set permissions on databases and
Hi Banyan,
Permission can vary from database to database.
Please ask your dba to grant you the permission and then try the mysqldump
On 7/19/07, Banyan He [EMAIL PROTECTED] wrote:
The question is in this server, I cannot backup the database by issuing
mysqldump. On another server, I can. I am
thx Ananda. I will try.
Cheers,
Ananda Kumar wrote:
Hi Banyan,
Permission can vary from database to database.
Please ask your dba to grant you the permission and then try the
mysqldump
On 7/19/07, Banyan He [EMAIL PROTECTED] wrote:
The question is in this server, I cannot backup the
Ananda, I cannot host the reasons. Just add one more parameter to avoid
LOCK TABLES.
mysqldump --lock-tables=false db
That works.
Cheers,
Thx guys.
Ananda Kumar wrote:
Hi Banyan,
Permission can vary from database to database.
Please ask your dba to grant you the permission and then try the
Mathieu Bruneau wrote:
murthy gandikota a écrit :
Hi
I did a hot backup a while ago. When I had to restore from backup there were several error messages. So I ran mysqlcheck for every table with --auto-repair option. Is this the best way?
Thanks
Murthy
Gerald L. Clark [EMAIL PROTECTED] wrote: Mathieu Bruneau wrote:
murthy gandikota a écrit :
Hi
I did a hot backup a while ago. When I had to restore from backup there were
several error messages. So I ran mysqlcheck for every table with
--auto-repair option. Is this the best way?
Hi
I did a hot backup a while ago. When I had to restore from backup there were
several error messages. So I ran mysqlcheck for every table with --auto-repair
option. Is this the best way?
Thanks
Murthy
-
Ahhh...imagining that irresistible new
Hi
I did a hot backup a while ago. When I had to restore from backup there were
several error messages. So I ran mysqlcheck for every table with --auto-repair
option. Is this the best way?
Thanks
Murthy
-
Ahhh...imagining that irresistible new
murthy gandikota a écrit :
Hi
I did a hot backup a while ago. When I had to restore from backup there
were several error messages. So I ran mysqlcheck for every table with
--auto-repair option. Is this the best way?
Thanks
Murthy
-
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
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 dbs with tar
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 party
backup process attempting to lock
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 affecting other db
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 affecting
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
of InnoDB and MyISAM table types. Upon investigating
SP this, I found this web site, with an article about backing up
SP mysql databases:
SP http://www.databasejournal.com/features/mysql/article.php/3421751
SP It looks like there is something called a InnoDB Hot Backup
SP that is a perl script
Hello,
I am running mysql 4.0.15 on a Win2000 operating system. I would like to be
able to back up the system with a perl script. I have a mix of InnoDB and
MyISAM table types. Upon investigating this, I found this web site, with an
article about backing up mysql databases:
http
investigating this, I found this web =
site, with an article about backing up mysql databases:
http://www.databasejournal.com/features/mysql/article.php/3421751
It looks like there is something called a InnoDB Hot Backup that is a =
perl script. Is this something that Mysql offers
Anyone using any third party products like Arkeia that enable you to do
a live backup of MySQL database?
I'm searching for a backup solution for our new data center and would
like to here what other people are using for MySQL.
Thanks,
Jeff
--
MySQL General Mailing List
For list archives:
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
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 well.
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 up live MySQL Databases
I
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(Jeff McKeon
[EMAIL
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
Subject: Re: Backing
Blog: http://webobjects.webhop.org/
On Jun 16, 2005, at 2:02 PM, Ashley M. Kirchner wrote:
With all this discussion going on about the best way to backup
MySQL data, I have a question: Is there anything wrong with simply
copying the db files when you're backing up
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
No I can do a dump, but I was wondering if I can just copy some lies or a
directory.
Thanks,
Néstor Alberto Flórez
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
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
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
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
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 larger databases, hundred's of gigs, and higher
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
If I use innodb_file_per_table, how do I properly back-up that table so it
could be imported to another server should something happen to my main
server if I do not have the hot-back-up utility?
If I lock then copy the table, can I simply use ALTER TABLE tbl_name
IMPORT TABLESPACE for it to
I am having trouble with a nightly backup of our MySQL database. Using the
mysqldump command, we dump our entire database to a backup directory. But
consistently the backup file contains only 33 of the 88 tables in the
database. The 33 getting backed up are the first 33 of the 88 as sorted
I assume you are running this with cron. Do you get an error message from
cron? Do you have enough room on the destination disk for all 88 tables?
How big is the backup file?
For completeness, what is your OS, and what is your mysql version?
Michael
Danny Smitherman wrote:
I am having trouble
I am having trouble with a nightly backup of our MySQL database. Using the
mysqldump command, we dump our entire database to a backup directory. But
consistently the backup file contains only 33 of the 88 tables in the
database. The 33 getting backed up are the first 33 of the 88 as sorted
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 testing, I've used the procedures outlined in the
help to take my backups, which entails
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 utility, then issuing the
UNLOCK TABLES from my MySQL monitor.
Now
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
distribution:
http://dev.mysql.com/doc/mysql/en/mysqldump.html
There is also non-free InnoDB Hot Backup program:
http://www.innodb.com/order.php
Some info about backing up InnoDB database find at:
http://dev.mysql.com/doc/mysql/en/Backing_up.html
Also, as has been suggested
Hi all
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?
Thanx for your time.
Diga-me e eu esquecerei
Mostre-me e lembrarei
Ensina-me e aprenderei
-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 to
://dev.mysql.com/doc/mysql/en/mysqldump.html
There is also non-free InnoDB Hot Backup program:
http://www.innodb.com/order.php
Some info about backing up InnoDB database find at:
http://dev.mysql.com/doc/mysql/en/Backing_up.html
--
For technical support contracts, goto https
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
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
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 like
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:
[client]
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.
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
http://www.mysql.com/doc/en/Option_files.html. The typical user
option file starts with
[client]
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 path?
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
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.
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
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
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, as
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
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-databases
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 PROTECTED]
Subject: Re: Backing up all databases
Well
-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
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
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]
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 only
Am testing this command to backup databases:
/usr/local/mysql/bin/mysqldump --opt --all-databases
/usr/local/mysql/data/mysqldump
Am running as root, but it only backs up databases root has access too.
What's the best way to handle this -- give root full perms on all dbs?
--
Randall Perry
: Tuesday, November 11, 2003 3:05 PM
--To: [EMAIL PROTECTED]
--Subject: Backing up all databases
--
--Am testing this command to backup databases:
--
--/usr/local/mysql/bin/mysqldump --opt --all-databases
--/usr/local/mysql/data/mysqldump
--
--Am running as root, but it only backs up databases root has
---Original Message-
--From: Randall Perry [mailto:[EMAIL PROTECTED]
--Sent: Tuesday, November 11, 2003 3:05 PM
--To: [EMAIL PROTECTED]
--Subject: Backing up all databases
--
--Am testing this command to backup databases:
--
--/usr/local/mysql/bin/mysqldump --opt --all-databases
--/usr/local/mysql/data
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
mysqldump -u$dbuser
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
mysqldump -u$dbuser -p$dbpassword $dbname | zip -q9
$destdir/db_$dbname.zip - $destdir/backup.log
1 - 100 of 132 matches
Mail list logo
