On Fri, 5 Apr 2002, Steve Rapaport wrote:
> On Friday 05 April 2002 06:37 pm, andy thomas wrote:
> >On Fri, 5 Apr 2002, Steve Rapaport wrote:
> >> With InnoDB, I'm sure this problem goes away, but as soon as we
> >> go to InnoDB, we have to pay for backups and support,
> >> which means we start looking around at 'pay' solutions.
> >
> >Why do you suddenly have to pay for backups and support?
>
> We have to pay for backups because backing up an Innodb
> table and restoring it reliably is not a simple matter of locking
> the table and copying the files, like in a MyISAM table. To
> do it reliably it looks to me like you'll need Heikki's InnoDBHotCopy
> module, which costs money.
mysqldump works fine with Innodb although this may not be the complete
answer in your case if you have a busy database.
> We have to pay for support for a similar reason: We're using
> replication for failover, and I've already had cases where replication fails
> for one reason or another. In these cases, recovering
> replication was tedious but possible. Reading through the
> manual for Innodb it looks (actually looked, it's changed for
> the better lately) like this would become hellish and unlikely
> to succeed. So I'd be paying for support to keep replication
> working, I think.
I've not used replication yet so I can't really comment on this aspect.
OK, point taken.
cheers,
Andy
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
