[Toolserver-l] s3 replication is halted

[Platonides]

River Tarnell wrote:
> Platonides:
>> Move mysql data files to the new box
> 
> i usually try to avoid that when splitting a database, since it means the
> innodb data file is much larger than it needs to be (yarrow has both s1 and s3,
> but the new server will only have s1).  it's also a good opportunity to
> defragment/reindex the tables, which helps performance a bit.

You can have each table on a different file
http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html

Specially, "If you start the server with this option, new tables are
created using .ibd files, but you can still access tables that exist in
the shared tablespace" so no worries about s1 being already there.

When moving to a new server, tablespace id mismatches are likely, but
seems people have been able to go over them.
http://mysqlhints.blogspot.com/2008/10/fixing-innodb-import-tablespace-error.html