Hi,
We have a (pre-existing) disaster recovery/backup script that uses =
mysqldump, ssh, mysql to backup an existing database. One of the tables =
is rather large (1 Gig or so), and the time that it takes to DROP =
TABLE on an already loaded recover server causes a timeout. I have =
confirmed
perhaps you would get a better response from doing scp... which runs
over ssh... or doing the mysqldump in a cron job, so it will
already be complete for transport by ssh. I still think scp is the more
proper way to go.
dan orlic
Steve Williams wrote:
Hi,
We have a (pre-existing) disaster
PROTECTED]
Sent: Friday, February 27, 2004 3:52 PM
To: Steve Williams
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better response from doing scp... which runs
over ssh... or doing the mysqldump in a cron job, so
.
Thanks,
Steve Williams
-Original Message-
From: dan orlic [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 3:52 PM
To: Steve Williams
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better
: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better response from doing scp... which runs
over ssh... or doing the mysqldump in a cron job, so it will
already be complete for transport by ssh. I still think scp
-Original Message-
From: dan orlic [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 3:52 PM
To: Steve Williams
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better response from doing scp... which runs
Rafal Kedziorski [EMAIL PROTECTED] wrote:
we have problems with import our dumped InnoDB tables.
We get this error message:
Can't create table '.\mmcms_test\media_lock.frm' (errno: 150)
My tables which will be referenced by foreign keys will be dumped in the
inncorect order.
if I
hi,
we have problems with import our dumped InnoDB tables.
We get this error message:
Can't create table '.\mmcms_test\media_lock.frm' (errno: 150)
My tables which will be referenced by foreign keys will be dumped in the
inncorect order.
if I set:
SET FOREIGN_KEY_CHECKS=0;
sql script
SET
