12. Migrating to TokuMX¶
Percona TokuMX stores all data on disk differently from basic MongoDB, this is key to its performance benefits. Therefore, Percona TokuMX cannot use existing MongoDB data files—all MongoDB data must be migrated to the Percona TokuMX data format.
There are many strategies for migrating data, and choosing the right one depends on your current MongoDB installation and your application’s availability requirements. Single servers, replica sets, and sharded clusters can all be converted to Percona TokuMX but the process is different for each.
The following guides describe the possible migration strategies:
12.1.2. Offline vs. Online Migration¶
For replica sets and sharded clusters, you have a choice between offline and online migrations.
If your application can afford downtime, an offline migration is the best choice, because it will be simpler and faster overall.
If an offline migration will take too long for your application to afford, then you can do an online migration. These procedures require that basic MongoDB is running with replication, because a major part of the migration process involves tailing the MongoDB oplog and replaying operations on the TokuMX cluster to keep the clusters in sync until the application can be switched over.