Re: why: mysqldump and mysqlimport?

2004-01-14 Thread Tobias Asplund
On Tue, 13 Jan 2004, EP wrote:

 I am wondering:

 I can see the MySQL data files for my various databases.

 What technically prevents me from simply copying those files and using copies
 - to move my database to another file structure or server
 - to back-up my current db

Copying will not work across certain versions, will also not work between
system archtechtures, port to other RDBMS or if you do not have physical
access to the files.

For the cases above mysqldump works fine.

cheers,
Tobias

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: why: mysqldump and mysqlimport?

2004-01-14 Thread Daniel Kasak
EP wrote:

I am wondering:

I can see the MySQL data files for my various databases.

What technically prevents me from simply copying those files and using 
copies
- to move my database to another file structure or server
- to back-up my current db

Yes, I did put my finger in the electrical socket as a kid.  But only 
several times.

A simple file copy works if:

a) No-one is accessing the database at the time, and
b) There is no database corruption
If you have database corruption, mysqldump will often be the first to 
know about it, as you're selecting all rows ( as opposed to other mysql 
clients which are selecting specific rows ). So using mysqldump and 
watching the output ( make a cron job and it'll email you the output ), 
you can catch database corruption early and have a good chance to do 
something about it, instead of simply copying corrupt files day after 
day until you finally don't have a valid backup around.

Dan

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: http://www.nusconsulting.com.au
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


why: mysqldump and mysqlimport?

2004-01-13 Thread EP
I am wondering:

I can see the MySQL data files for my various databases.

What technically prevents me from simply copying those files and using copies
- to move my database to another file structure or server
- to back-up my current db
Yes, I did put my finger in the electrical socket as a kid.  But only 
several times.

TIA

Eric

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: why: mysqldump and mysqlimport?

2004-01-13 Thread Dan Nelson
In the last episode (Jan 13), EP said:
 I am wondering:
 
 I can see the MySQL data files for my various databases.
 
 What technically prevents me from simply copying those files and using 
 copies
 - to move my database to another file structure or server
 - to back-up my current db

Absolutely nothing.  As long as you ensure there are no active writes
while you make the copy, this is the fastest way to back up a database. 
The mysqlhotcopy script automates the process.

-- 
Dan Nelson
[EMAIL PROTECTED]

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]