| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Dan Nelson | Date: | January 14 2004 5:43am |
| Subject: | Re: why: mysqldump and mysqlimport? | ||
| View as plain text | |||
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 dnelson@stripped
| Thread | ||
|---|---|---|
| • Importing a dumpfile | Matthew Stuart | 14 Jan |
| • Re: Importing a dumpfile | Daniel Kasak | 14 Jan |
| • Re: Importing a dumpfile | Douglas Sims | 14 Jan |
| • Re: Importing a dumpfile | Roger Baklund | 14 Jan |
| • why: mysqldump and mysqlimport? | EP | 14 Jan |
| • Re: why: mysqldump and mysqlimport? | Dan Nelson | 14 Jan |
| • Re: why: mysqldump and mysqlimport? | Tobias Asplund | 14 Jan |
| • Re: why: mysqldump and mysqlimport? | Daniel Kasak | 14 Jan |
