Frank, thanks for the reply.
I'd thought of that, but I was worried about using HotBackup (we use
this for all of our backups on our production machines) - the hot backup
manual at http://www.innodb.com/manual.php doesn't mention if it can
follow a symlink to the data file.
Thanks for the link - some very interesting presentations there (wish I
had gone to the conference - next year maybe).
David
Dr. Frank Ullrich wrote:
David,
David Griffiths wrote:
The manual is a little unclear on per-table-tablespaces in 4.1/5.0
(http://dev.mysql.com/doc/mysql/en/multiple-tablespaces.html)
Using per-table-tablespaces ignores the innodb_data_file_path (yes,
it uses it for the ibdata files, but not for the
tablespace/data-files for the individual tables). It doesn't talk
about the relationship between the per-tables-tablespaces and the
innodb_data_file_path (or just as importantly the lack of
relationship between the two).
That would all be fine, except the same page also states,
"Using multiple tablespaces can be beneficial to users who want to
move specific tables to separate physical disks or who wish to
restore backups of single tables quickly without interrupting the use
of the remaining InnoDB tables."
How do you move a table (thus the tablespace) to a seperate disk? It
implies that different tables and their related tablespaces can be
put on different disks, but doesn't really get into the specifics.
you have to symlink the innodb table file:
move it to the disk you want, then create a symlink in the correct
database directory that points towards the new location.
See: http://www.mysqluc.com/pub/w/35/sessions.html "New InnoDB Features"
David
Regards,
Frank.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
