Migration Guide¶
The migration of MSR metadata and image binaries to a new Kubernetes or Swarm cluster can be a complex operation. To help you to successfully complete this task, Mirantis provides the Mirantis Migration Tool (MMT).
With MMT, you can transition to the same MSR version you already have in use, or you can opt to upgrade to a more recent major, minor, or patch version of the software. In addition, MMT allows you to switch cluster orchestrators and deployment methods as part of the migration process.
Available MSR system orchestrations include:
MSR system |
Orchestration |
---|---|
|
Kubernetes orchestration |
|
Docker Swarm orchestration |
|
MKE orchestration |
Migration paths¶
Note
MMT does not support migrating to 2.9.x target systems.
Source MSR system |
Target MSR system |
---|---|
MSR 2.9 |
|
MSR 3.0, Helm |
|
MSR 3.1, Helm |
|
MSR 3.1, Operator |
|
MSR 3.1, Swarm |
|
The workflow for migrating MSR deployments is a multi-stage sequential operation.
Migrations from MSR 2.9.x:
Source verification
Estimation
Extraction
Transformation
Restoration
Migrations from MSR 3.x.x:
Extraction
Restoration
Note
Refer to Kubernetes migrations for all migrations that include Kubernetes-based source or target systems.
Backup and restoration paths¶
You can use MMT to create an MSR system backup as well as to restore an MSR system from a previously created backup.
Source MSR system |
Target MSR system |
---|---|
MSR 3.0, Helm |
MSR 3.0, Helm |
MSR 3.1, Helm |
MSR 3.1, Helm |
MSR 3.1, Operator |
MSR 3.1, Operator |
MSR 3.1, Swarm |
MSR 3.1, Swarm |
- MMT architecture
- Migration prerequisites
- Select the storage mode
- Simplified migration
- Multi-step migration
- Settings not migrated
- Telemetry
- Troubleshoot migration
- Restore MSR reusing an extract copy
- Filesystem storage backends
- Too many open files
- Failure to load data error message
- No space left on device
- Failed to estimate migration error message
- rethinkdb row cannot be restored
- Admin password on MSR 3.0.x target no longer works
- Blob image copy considerations
- Total blob size: 0
- Additional parameters
- Additional volume mappings for containers
- Failed to query for metadata size
- flag provided but not defined: -append
- Storage configuration is out of sync with metadata
- The estimate command returns an image data value of 0
- Unable to get FileInfo: /blobs
- failed to run container: mmt-dtr-rethinkdb-backup
- MMT release notes