Extract the data¶
To extract metadata and, optionally, binary image data from an MSR 2.9.x system, execute the following command on the source MSR 2.9.x system:
docker run \
--rm -it \
-v <local-migration-directory>:/migration:Z \
registry.mirantis.com/msr/mmt:<mmt-version> \
extract msr \
--source-mke-url <mke-url> \
--source-username <mke-admin-username> \
--source-password <mke-admin-password> \
--source-url <msr-2.9-url> \
--storage-mode <inplace|copy> \
--source-insecure-tls \
/migration
Note
Migrations that use the copy
storage mode and a filesystem
storage
back end must also include the --mount
option, to specify the MSR 2.9.x
Docker volume that will be mounted to the MMT container at the /storage
directory. As --mount
is a Docker option, it must be included prior to
the registry.mirantis.com/msr/mmt:<mmt-version>
portion of the command.
--mount source=dtr-registry-<replica-id>,target=/storage
To obtain the MSR replica ID, run the following command from within an MSR node:
docker ps --format '{{.Names}}' -f name=dtr-rethink | cut -f 3 -d '-'
Parameter |
Description |
---|---|
|
Set the URL for the source Mirantis Kubernetes Engine (MKE) system. |
|
Set the username of the admin user for the MKE system running MSR 2.9.x. |
|
Set the password of the admin user for the MKE system running MSR 2.9.x. |
|
Set the URL for the source MSR 2.9.x system. |
|
Set the registry migration storage mode. Valid values: |
|
Optional. Set whether to use an insecure connection. Valid values: |
|
Optional. Disables MMT metrics collection for the
|
Example output:
The Mirantis Migration Tool extracted your registry of MSR 2.9, using the
following parameters:
Source Registry: https://172.17.0.1
Mode: copy
Image data: 2 blobs (2.8 MB)
Important
To avoid data inconsistencies, the source registry must remain in read-only mode throughout the migration to MSR 3.0.x.
The data extract is rendered as a TAR file with the name
msr-backup-<MSR-version>-mmt.tar
in the <local-migration-directory>
.