| Cluster health checks < Premigration testing > Running the migration
- Installing MTC
- Ensuring same MTC versions
- Checking 'OLM Managed' setting
- Migrating a simple application
- Migrating an application with a persistent volume
- Removing migrated application namespace
Install MTC on your source and target clusters:
- Check the migration prerequisites.
- Install MTC on the source and target clusters.
- Configure a replication repository.
The following diagram describes how MTC uses Velero and Restic to back up data from the source cluster to the replication repository and then restores data from the replication repository to the target cluster:
The same MTC z-stream version must be installed on the source and target clusters.
Download and re-install the MTC Operator on the OpenShift 3 cluster just before you run a migration to ensure that you have the latest version.
The Operator Lifecycle Manager (OLM) pushes MTC Operator updates to the OpenShift 4 cluster automatically. On the OpenShift 3 cluster, however, the MTC Operator is installed manually and is not updated automatically.
In the web console, check the 'OLM Managed' setting in the 'MigrationController' manifest of each cluster:
- OpenShift 4 uses OLM:
olm_managed: true - OpenShift 3 does not use OLM:
olm_managed: false
Migrate a simple application without a persistent volume (PV):
- Install a simple application without a PV on the source cluster.
- Migrate the application to the target cluster. You do not need to stage the migration.
- Validate the application on the target cluster.
Migrate an application with a PV:
- Install an application with an associated PV on the source cluster.
- Stage the migration one or more times. Staging reduces migration time and application downtime during migration.
- Migrate the application to the target cluster.
- Validate the application on the target cluster.
If you are performing multiple test migrations, remove the migrated application namespace from the target cluster after each test.