{"componentChunkName":"component---src-templates-microservices-js","path":"/en/microservices/SiteMigration/","result":{"data":{"markdownRemark":{"html":"

GIS Cloud Suite Migration

\n

The content is going to introduce how to migrate the data of Service Instance, Service Node, File Manager, and Storage Resources from a GIS Cloud Suite to another GIS Cloud Suite.

\n

New Environment Preparation

\n\n

Migrate Service Instance, Service Node, and File Manager

\n

Migrate Consul Data

\n
    \n
  1. \n

    Gets the NFS mounting directories of ‘consul-server-{index}’ from old environment(The consul-servcer cluster has three nodes by default, please migrates the data from three directories).

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the paths of NFS mounting directory of ‘consul-server-{index}‘:

    \n
    kubectl get pvc -n {ns} | grep consul-server-{index} | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n
      \n
    1. Replace {ns} in the command by the name of your namespace.
      2. \n
    2. Execute the command three times to get three paths of the directories, replace {index} in the command by 0, 1, 2 each time.
      3. \n
    \n
    \n
    2. \n
  2. Copy the data from the three directories in step 1, and paste to the three corresponding directories of the new environment(refer to the command in step 1 to get the paths of NFS mounting directory of ‘consul-server-{index}’ in the new environment).
    3. \n
\n

Migrate File Manager Data

\n
    \n
  1. \n

    Gets the NFS mounting directory of ‘gisapplication-data’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the path of NFS mounting directory of ‘gisapplication-data’:

    \n
    kubectl get pvc -n {ns} | grep gisapplication-data | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n

    Replace {ns} in the command by the name of your namespace.

    \n
    \n
    2. \n
  2. Copy the data from the directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘gisapplication-data’ in the new environment).
    3. \n
\n

Migrate Industry Data

\n
    \n
  1. \n

    Gets the NFS mounting directory of ‘ispeco-mysql-data’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the path of NFS mounting directory of ‘ispeco-mysql-data’:

    \n
    kubectl get pvc -n {ns} | grep ispeco-mysql-data | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n

    Replace {ns} in the command by the name of your namespace.

    \n
    \n
    2. \n
  2. Copy the data from the directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘ispeco-mysql-data’ in the new environment).
    3. \n
\n

Restart The Services

\n

Restart consul-server, ispeco-dashboard-api, and ispeco-mysql services.

\n
\n

Notes:

\n

If the permission errors occur when restarting the consul-server service, please execute the command chmod 777 -R proxy/ raft/ serf/ in the NFS mounting directories of consul-server-{index} in new environemt separately, then restart consul-server service.

\n
\n

When you finish the steps above, the data of Service Instance, Service Node, and File Manager has migrated successfully.

\n

Migrate Storage Resources

\n

You need to migrate the data of Service Instance, Service Node, and File Manager before migrating the data of Storage Resources.

\n
\n

Notes:

\n

The number of nodes in new environment should be same as the old environment. That is, when a service has multiple nodes, the {index}s should be same in two environments.

\n
\n

Only HBase and HDFS Directory in the Storage Resources can be migrated.

\n

Migrate HBase

\n

Migrate the data of hbase-namenode

\n
    \n
  1. \n

    Gets the NFS mounting directory of ‘hbase-namenode’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the path of NFS mounting directory of ‘hbase-namenode’:

    \n
    kubectl get pvc -n {ns} | grep hbase-namenode | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n

    Replace {ns} in the command by the name of your namespace.

    \n
    \n
    2. \n
  2. Copy the data from the directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘hbase-namenode’ in the new environment).
    3. \n
\n

Migrate the data of hbase-datanode

\n
    \n
  1. \n

    Gets the NFS mounting directories of ‘datanode-volume-hbase-datanode-{index}’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the paths of NFS mounting directories of ‘datanode-volume-hbase-datanode-{index}‘:

    \n
    kubectl get pvc -n {ns} | grep datanode-volume-hbase-datanode-{index} | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n
      \n
    1. Replace {ns} in the command by the name of your namespace.
      2. \n
    2. If the service has multiple nodes, execute the command multiple times to get paths of the directories, replace {index} in the command by 0, 1, 2, …, N-1 each time.
      3. \n
    \n
    \n
    2. \n
  2. Copy the data from the directories in step 1, and paste to the corresponding directories of the new environment(refer to the command in step 1 to get the paths of NFS mounting directories of ‘datanode-volume-hbase-datanode-{index}’ in the new environment).
    3. \n
\n

Migrate the data of hbase-regionserver

\n
    \n
  1. \n

    Gets the NFS mounting directories of ‘hbase-regionserver-data-volume-hbase-regionserver-{index}’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the paths of NFS mounting directories of ‘hbase-regionserver-data-volume-hbase-regionserver-{index}‘:

    \n
    kubectl get pvc -n {ns} | grep hbase-regionserver-data-volume-hbase-regionserver-{index} | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n
      \n
    1. Replace {ns} in the command by the name of your namespace.
      2. \n
    2. If the service has multiple nodes, execute the command multiple times to get paths of the directories, replace {index} in the command by 0, 1, 2, …, N-1 each time.
      3. \n
    \n
    \n
    2. \n
  2. Copy the data from the ‘hbase-regionserver-data-volume-hbase-regionserver-0’ directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘hbase-regionserver-data-volume-hbase-regionserver-0’ in the new environment).
    3. \n
\n

Migrate the data of hbase-master

\n
    \n
  1. \n

    Gets the NFS mounting directory of ‘hbase-master-config’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the path of NFS mounting directory of ‘hbase-master-config’:

    \n
    kubectl get pvc -n {ns} | grep hbase-master-config | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n

    Replace {ns} in the command by the name of your namespace.

    \n
    \n
    2. \n
  2. Copy the data from the directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘hbase-master-config’ in the new environment).
    3. \n
\n

Restart The Services

\n

Restart hbase-namenode, hbase-datanode, hbase-regionserver, hbase-master, and iserver-datacatalog services.

\n

When you finish the steps above, the data of HBase has migrated successfully.

\n

Migrate HDFS Directory

\n

Migrate the data of hdfs-namenode

\n
    \n
  1. \n

    Gets the NFS mounting directory of ‘hdfs-namenode’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the path of NFS mounting directory of ‘hdfs-namenode’:

    \n
    kubectl get pvc -n {ns} | grep hdfs-namenode | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n

    Replace {ns} in the command by the name of your namespace.

    \n
    \n
    2. \n
  2. Copy the data from the directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘hdfs-namenode’ in the new environment).
    3. \n
\n

Migrate the data of hdfs-datanode

\n
    \n
  1. \n

    Gets the NFS mounting directory of ‘hdfs-datanode’ from old environment.

    \n

    Execute the following command in Kubernetes Master machine of the old environment to get the path of NFS mounting directory of ‘hdfs-datanode’:

    \n
    kubectl get pvc -n {ns} | grep hdfs-datanode | awk '{print $3}' | xargs kubectl describe pv | grep Path
    \n
    \n

    Notes:

    \n

    Replace {ns} in the command by the name of your namespace.

    \n
    \n
    2. \n
  2. Copy the data from the directory in step 1, and paste to the corresponding directory of the new environment(refer to the command in step 1 to get the path of NFS mounting directory of ‘hdfs-datanode’ in the new environment).
    3. \n
\n

Restart The Services

\n

Restart hdfs-namenode, hdfs-datanode, and iserver-datacatalog services.

\n

When you finish the steps above, the data of HDFS Directory has migrated successfully.

","frontmatter":{"title":"GIS Cloud Suite","next":null,"prev":null},"fields":{"path":"content/microservices/SiteMigration.en.md","slug":"/en/microservices/SiteMigration/","langKey":"en"}}},"pageContext":{"slug":"/en/microservices/SiteMigration/"}}}