Hello.
Among other suggestions think about such way.
If you MyISAM and InnoDB tables are used by different applications or
consistent state between them doesn't play big value, and the size
of MyISAM tables is low enough, you could perform the dump in two steps
listing the tables of the s
ucture.
Our table defintitions are relatively stable so we don't do it every
night. You could put it in the cron job to do it with the backup.
-Original Message-
From: Scott Plumlee [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 12:36 PM
To: mysql@lists.mysql.com
Subject: Re: Ba
>
> -Original Message-
> From: Scott Plumlee [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 17, 2005 10:21 AM
> To: mysql@lists.mysql.com
> Subject: Backup database with MyISAM and InnoDB tables together
>
> I'm not clear on best practice to use on a database containing both
> MyISAM and I
If you are runing binary log and do a
FLUSH LOGS
mysqldump --opt --skip-lock-tables MyISAM table names
FLUSH LOGS
mysqldump --opt --single-transaction INNODB table names
You have a recoverable state with the combination of the mysqldump file
and the binary log file that was started by the 1st
Mikael Fridh wrote:
Martin,
Shut down your 3.23 server.
Make a binary copy of the data.
Install 4.0
Upgrade your privileges with the 4.0 script.
Start 4.0 server.
That's it, right?
Worked for me...
When doing backups I always do a full recursive backup of the entire mysql
data directory. This way
m: "Paul DuBois" <[EMAIL PROTECTED]>
To: "Martín Lahittette" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, October 18, 2003 11:59 PM
Subject: Re: Backup database with foreign keys
At 21:45 + 10/18/03, Martín Lahittette wrote:
>Yes, you are right
At 21:45 + 10/18/03, Martín Lahittette wrote:
Yes, you are right. I am upgrading to MySQL 4.0,
but I can not do it if I do not have a backup of
my current database. If something goes wrong, I
need to be sure that I am able to restore the
database to its current state. Maybe I need two
type
Yes, you are right. I am upgrading to MySQL 4.0, but I can not do it if I do
not have a backup of my current database. If something goes wrong, I need to
be sure that I am able to restore the database to its current state. Maybe I
need two types of backup, one to move my databases to version 4.0
At 16:13 + 10/18/03, MartÌn Lahittette wrote:
Thank you very much Paul, that is exactly what I
need, but FOREIGN_KEY_CHECKS = 0 is a feature of
MySQL/InnoDB-3.23.52 and unfortunatelly my
current version is 3.23.51. I can not upgrade to
version 4.0 if I do not have a reliable backup
of my c
Thank you very much Paul, that is exactly what I need, but
FOREIGN_KEY_CHECKS = 0 is a feature of MySQL/InnoDB-3.23.52 and
unfortunatelly my current version is 3.23.51. I can not upgrade to version
4.0 if I do not have a reliable backup of my current version.
Do you have any other sugestion?
Mar
At 0:15 + 10/18/03, MartÌn Lahittette wrote:
Hi,
I want to backup a MySQL 3.23 database to
upgrade it to MySQL 4.0. My tables are InnoDB
and they have foreign keys. I would like to know
how to backup it, because it seems that neither
mysqldump nor mysqlhotcopy can be easily used.
The resto
On Tue, Jun 05, 2001 at 05:16:37PM +0800, Alice wrote:
>
> Hi, besides using mysqldump, can i just copy the database in the
> data directory straight away in windows explorer ?? is this a
> correct way to do that ?? thanx
It's probably only "safe" if you do a
FLUSH TABLES WITH READ LOCK;
be
Hola alguien habla español. que pueda ayudarme como se hace copia de
seguridad a tablas exageradamente grande.
He consultado el comando backup table tablas, to 'ruta' .
hay otra forma?.
Gracias.
Roger Retamoza
ICQ 102090754
Barranquilla Colombia
--
13 matches
Mail list logo
