Stewart Smith wrote:
> The first challenge is getting the data there though. Typically, when
> setting up a slave that's running NDB you can use ndb_restore to get to
> a known state. Not so with innodb as the slave.
This can be worked around by taking and restoring a schema-only dump
using mysqldump (make sure ENGINE=ndb is either changed to innodb
in the dump file or InnoDB is the default engine on the restore side
and ndbcluster is not available there), and then using
ndb_restore --print-data ...
and LOAD DATA INFILE to restore the actual data?
Hartmut Holzgraefe, MySQL Regional Support Manager, EMEA
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Thomas Schröder