Steve,
- Original Message -
From: "Orr, Steve" <[EMAIL PROTECTED]>
To: "'Heikki Tuuri'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, June 13, 2002 3:27 AM
Subject: RE: MySQL/InnoDB Hot Backups - What's a "binlog seg
Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 2:56 PM
To: [EMAIL PROTECTED]
Subject: Re: MySQL/InnoDB Hot Backups - What's a "binlog segment?"
Steve,
the binlog is the MySQL logical log which it writes if you specify
[mysqld]
log-bin
in my.cnf. They are
TECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, June 12, 2002 8:20 PM
Subject: MySQL/InnoDB Hot Backups - What's a "binlog segment?"
> I'm confused about the meaning of the help text from ibbackup --help.
>
> Here's the text:
> "You should m
Isn't there an administrator on this list that can fix this? Who is
"w3e3demo" and why can't he/she be zapped?
-Original Message-
From: Mailer-Daemon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 11:34 AM
To: Orr, Steve
Subject: NDN: MySQL/InnoDB Ho
I'm confused about the meaning of the help text from ibbackup --help.
Here's the text:
"You should make backups of the .frm files... both BEFORE and AFTER ibbackup
finishes its work, and also store the MySQL binlog segment which is
generated between the moment you copy the .frm files to a backup
an time to recovery (MTTR)
is unecessarily long.
IMHO :-)
-Original Message-
From: Kiss Dániel [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 12:04 AM
To: Orr, Steve; [EMAIL PROTECTED]
Subject: Re: InnoDB Hot Backups... ALL OR NOTHING ???
First of all, there are many aspects of
First of all, there are many aspects of your problem.
1. The InnoDB uses transaction safe table types, and uses the log files to
restore if anything goes wrong during the tsanasction. So it is almost
impossible to have a permanent database error, that cannot be repaired by
InnoDB itself. If My
Can you backup/restore just one MySQL database with InnoDB hot backup? From
what I gather it's an all or nothing proposition. As I understand it,
there's only one "tablespace" (with any number of data files) and all
database tables of type 'InnoDB' are comingled in the one tablespace.
Therefore, i
If your database is large enough then any sort of hot backup
will lock the tables for too long. The method I use is to
use LVM to take a snapshot of the MySQL partition while
MySQL is stopped. All my attempts to snapshot a live MySQL
database resulted in inconsistent results...
The following is
less you tell
> it to.
>
> Thanks for everyone's help. I now have a working backup script.
>
> -Original Message-
> From: David Turner [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 29, 2001 1:00 PM
> To: Joshua J. Kugler
> Cc: David Turner; Matthew W
OTECTED]]
Sent: Wednesday, August 29, 2001 1:00 PM
To: Joshua J. Kugler
Cc: David Turner; Matthew Walker; MySQL Mailling List
Subject: Re: Hot Backups
Didn't read your last item before I fired my last message off. If
mysqldump locks the
table before it dumps then it is interupting servi
ries, or is there some recommended procedure for this?
RTFM, RTFM, RTFM!
That being said, most everyone I know uses mysqldump for hot backups.
Now, STOP what you're doing and go bookmark
http://www.bitbybit.dk/mysqlfaq/faq.html,
if you have time to do nothing else - this is Carsten Pederson
On Wed, Aug 29, 2001 at 12:50:06PM -0600, Matthew Walker wrote:
>
> What's the best way of doing a hot backup on a database? Our server
> is set up in such a way that it's not a simple matter to shut down
> apache/mysql and do the backup then. So, is it safe to just copy the
> mysql directories, o
gust 29, 2001 11:52 AM
> To: David Turner; Matthew Walker
> Cc: MySQL Mailling List
> Subject: Re: Hot Backups
>
>
> I'm doing a mysqldump and then backing up the resulting text
> file. Works
> fine, doesn't interupt anything, and doesn't have any
> p
t 29, 2001 12:52 PM
To: David Turner; Matthew Walker
Cc: MySQL Mailling List
Subject: Re: Hot Backups
I'm doing a mysqldump and then backing up the resulting text file.
Works
fine, doesn't interupt anything, and doesn't have any problems with a
live
server. IIRC, mysqldump locks a
Didn't read your last item before I fired my last message off. If mysqldump locks the
table before it dumps then it is interupting service. If I have a high number of
transactions they're blocked until the lock is released.
Dave
On Wed, Aug 29, 2001 at 10:52:26AM -0800, Joshua J. Kugler wrote:
>
Any problems with data inconsistencies?
Dave
On Wed, Aug 29, 2001 at 10:52:26AM -0800, Joshua J. Kugler wrote:
> I'm doing a mysqldump and then backing up the resulting text file. Works
> fine, doesn't interupt anything, and doesn't have any problems with a live
> server. IIRC, mysqldump lock
I'm doing a mysqldump and then backing up the resulting text file. Works
fine, doesn't interupt anything, and doesn't have any problems with a live
server. IIRC, mysqldump locks a table before it dumps, so there won't be any
funny records. Or course, mysqldump could catch the database in the
The way I am planning on doing it is setting up another server that I replicated to
and backing that server up. I would like to hear how other people are backing up
servers
without interupting service.
Dave
On Wed, Aug 29, 2001 at 12:50:06PM -0600, Matthew Walker wrote:
> What's the best way of
What's the best way of doing a hot backup on a database? Our server is
set up in such a way that it's not a simple matter to shut down
apache/mysql and do the backup then. So, is it safe to just copy the
mysql directories, or is there some recommended procedure for this?
Matthew Walker
System Adm
20 matches
Mail list logo
