Moving back end Volume from the Command Line
This section contains information on migrating the following volumes to a different topology:
- Metadata volume, which stores the DB tables for the metadata associated with the tier.
- Erasure-coded volume, which stores the erasure-coded data.
Moving Metadata Volume to Another Topology
By default, the volume, which stores the DB tables for the metadata associated with
the tier, is created in
/var/mapr/tier/mapr.internal.tier.<volName>
and is in the
/data
topology. However, you can move the metadata volume to
another topology using the volume move
command. For example:
/opt/mapr/bin/maprcli volume move -name <metadataVolName> -topology <newTopo>
curl -k -X POST 'https://<host>:8443/volume/move?name=<metadataVolName>&topology=<newTopo>' --user mapr:mapr
Moving Erasure-Coded Volume to Another Topology
The erasure-coded volume is by default created in the same topology as the front-end
volume. You can specify a different topology for the erasure-coded volume when
creating a front-end volume. You can also move the erasure coded volume to a different
topology using the volume move
command. For example:
/opt/mapr/bin/maprcli volume move -name <volName> -ectopology <newTopo>
curl -k -X POST 'https://<host>:8443/volume/move?name=<volName>&ectopology=<newTopo>' --user mapr:mapr
Here, the name
parameter takes the name of the front-end volume
and the ectopology
parameter takes the topology to which to move
the erasure-coded volume associated with the front-end volume. For more
information, see volume move
.