Migrate Ehcache Data
If you have Ehcache data in restartable caches contained in a restartable cache manager, you can migrate that data to a new cluster without moving the platform data roots. Since the data migration works at the data directory level, data for all restartable cache managers that use the same data directory will be migrated together.
1. Shut down the old cluster.
2. Start the active servers in the new cluster with the same number of stripes as the old cluster.
3. Create the cache manager configuration using a client. The cluster URI, including the cluster tier manager name for the cache manager, can be different from the URI for the old cluster. If the name part of the URI is different, specify the old name as the restart identifier when using the cache manager configuration API, so the system can map the data corresponding to a given cache manager correctly. If there is more than one cache managers under the same data directory, use the configuration API to create all the cache managers in the target cluster. For instructions, see the section on fast restartability in the Ehcache API Developer Guide.
4. Shut down the new cluster.
5. For all restartable cache managers on all servers you want to migrate, copy the contents of the Ehcache directories (caching data roots) from the data directories of all active servers in the old cluster to the data directories in the new cluster. The data directory paths on the new cluster can be different from those on the old cluster.
6. Start the new cluster. Terracotta DB will load all the cache data that was migrated from the old cluster.