Well if you copy my.cnf settings along with ibdata files and log files
then it is possible to copy innodb exactly on the different machine and
i have done this before worked fine for me.
Love ..
[EMAIL PROTECTED] wrote:
InnoDB files can not be copied from one machine to another like the
MyISAM f
Ah, I see. So the tables that are represented by all
three files are presumably MyISAM files, right?
--- Victor Pendleton <[EMAIL PROTECTED]> wrote:
> InnoDB files can not be copied from one machine to
> another like the
> MyISAM files. If you did not dump the data or you do
> not have an
> a
InnoDB files can not be copied from one machine to another like the
MyISAM files. If you did not dump the data or you do not have an
archived backup you will more than likely have to recreate the table
structures.
David Blomstrom wrote:
Yikes...I've been replying to myself! I forgot that
when I
Yikes...I've been replying to myself! I forgot that
when I reply to messages from the MySQL newsgroup on
this e-mail account, it doesn't include
mysql@lists.mysql.com, for some odd reason.
At any rate, I wanted to say that I have just ONE file
type left - FRM. My MYD and MYI files have both
vanish
The MySQLFront solution worked like a charm. Thanks, and thanks to all who
replied to my queries on this one.
Brent
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/
I use MySQLFront and do this.
Create my dump file
create the database
restore from dump
So far so good...
M;)
> [EMAIL PROTECTED] wrote:
>
>> Hi. I've been reading for several hours on this one. I've tried
>> everything I've read. I'm either doing something really stupid or I've
>> missed the p
[EMAIL PROTECTED] wrote:
> Hi. I've been reading for several hours on this one. I've tried everything
> I've read. I'm either doing something really stupid or I've missed the
> point completely.
>
> I have a db on a linux server. I used phpAdmin to create a dump file
> (pe.sql) and retrieve
[EMAIL PROTECTED] wrote:
> Hi. I've been reading for several hours on this one. I've tried everything
> I've read. I'm either doing something really stupid or I've missed the
> point completely.
>
> I have a db on a linux server. I used phpAdmin to create a dump file
> (pe.sql) and retrieved it o
lt;[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 5:05 PM
Subject: Re: Copying Database
> 1) It's on a RAID, the seq test (just using a perl script to write
files
> coninuously) reach >50MBytes/sec
> 2) Sorry I don't understand
> 3) I've no idea. I've tried
lt;[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 9:58 PM
Subject: Re: Copying Database
> This is totally weird!
> Untar should be faster then tar on a any normal
> computer under normal os with normal hdds.
> So, your problem could be:
> 1) Your hdds are way too slow
> 2) In
untarring on has a very weak CPU
- Original Message -
From: "Sam Wong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 4:20 PM
Subject: Re: Copying Database
> It's quite fast for tar, just around 10-20 minutes. But it's
unaccept
m Wong" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 9:13 PM
Subject: Re: Copying Database
> Try copying your databasefiles (mysqlhome/data), tar'ed or untar'ed,
> to the mysql/data location.
> According to specs this should do it
>
>
Try copying your databasefiles (mysqlhome/data), tar'ed or untar'ed,
to the mysql/data location.
According to specs this should do it
regards
- Original Message -
From: "Sam Wong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 1:47 PM
Subject: Copying Database
13 matches
Mail list logo
