RE: Backing up MySQL tables
2003-04-02 16:45:19
Dumping the database and then backing up the dump is the right way to go.
Think of the dump as a snapshot of the database. By backing up the snapshot,
you know you're getting a consistent and restorable backup. If you're
worried about the disk space it takes, you can compress it. I've seen this
method used for MySQL, PostgreSQL, MS SQL, and Oracle.
> -----Original Message-----
> From: Alex Thurlow [mailto:alex.thurlow AT skylist DOT net]
> Sent: Wednesday, April 02, 2003 1:28 PM
> To: amanda-users AT amanda DOT org
> Subject: Backing up MySQL tables
>
>
> I need to start backing up MySQL tables on one of my
> machines, but I've
> heard that to you run the risk of table corruption if you
> just copy the
> mysql directory while MySQL is running. Stopping the
> database is not an
> option, and the only solution I've come up with is having
> another script do
> a mysql dump and then backing up that. It seems like a waste
> of time and
> resources to basically do 2 backups though. I was just
> wondering what
> anyone here does for MySQL backups on their own systems?
>
> Alex Thurlow
>
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- RE: Backing up MySQL tables,
Bort, Paul <=
|
|
|