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 MySQL crashes, you just have to restart it, and InnoDB
repaires automatically all the tables containing errors.
2. In spite of the first section, its a good idea to create backups of your
InnoDB tablespace, because it can happen that the hard disk you have your
tablespace files fails and in a case like this you don't have anything
else, just your backup files.
It's a little bit difficult to save all the InnoDB tablespaces onto another
backup disk, because they can be very big, although they are compressable
very well, because the empty spaces inside the tablespace contain zeros.
A simple solution is not to backup directly the InnoDB tablespaces. Just
convert the InnoDB tables into MyISAM and backup the MyISAM version of them.
3. The third aspect is that you can have many tablespaces, not only one big.
For example instead of an InnoDB initialization command in my.cnf like this
innodb_data_file_path = ibdata1:2000M
you can use this
innodb_data_file_path =
ibdata1:200M;ibdata2:200M;ibdata3:200M;..ibdata10:200M
Good luck,
Daniel
At 15:21 2002.06.06. -0600, you wrote:
>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, if a single datafile becomes corrupt, all the databases with
>InnoDB type tables are down and you have to restore everything. Is that
>right? If so are there any plans to have multiple named tablespaces?
>
>We have a single server with 150+ databases (one for each hosted customer).
>If one customer database goes down then we can restore the MYISAM type
>tables without affecting the 24X7 availability for the other 149 customers.
>However, if we convert tables to type InnoDB and a data file is corrupted or
>lost, then all databases are down and we have to restore EVERYTHING. Is this
>correct?
>
>
>Sincere thanks in advance...
>
>---------------------------------------------------------------------
>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
---------------------------------------------------------------------
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
