Migrating HBase tables

During the HBase migration, the HBase tables with their related metadata are migrated from a CDH or CDP Private Cloud Base cluster to an Operational Database (OpDB) Data Hub cluster.

Before the migration, the source cluster is scanned to collect the HBase tables. During the migration process, the tables are not affected on the source cluster and can remain part of running jobs.
  • Ensure that CMA is set up correctly using the steps in Setting up CMA server.
  • Ensure that you have met the requirements detailed in Reviewing prerequisites before migration.
  • Ensure that you have a CDH 5, CDH 6 or CDP Private Cloud Base cluster registered as a source from which you want to migrate your HBase tables. If you do not have a source cluster yet, complete the steps in Registering source clusters.
  • Ensure that you have an Operational Database (OpDB) Data Hub cluster registered as a destination cluster to which you want to migrate your HBase tables. If you do not have a destination cluster yet, complete the steps in Registering destination clusters.
  • Ensure that you have one of the following parcels (together with its corresponding .sha files) procured from Cloudera Support based on which CDH version you use:
      • CLOUDERA_OPDB_REPLICATION-1.0-1.CLOUDERA_OPDB_REPLICATION5.14.4.p0.31473501-el7.parcel
      • CLOUDERA_OPDB_REPLICATION-1.0-1.CLOUDERA_OPDB_REPLICATION6.3.3.p0.8959316-el7.parcel
      • Copy the OpDB Replication Manager parcels to the following directories based on the CDH version:
        • [***CMA ROOT FOLDER***]/parcels/hbase/cdh5/
        • [***CMA ROOT FOLDER***]/parcels/hbase/cdh6/
  1. Click on the CDH or CDP Private Cloud Base cluster you want to use for the migration on the Clusters page.
  2. Click Start Scanning to open the Scan Settings.
  3. Select HBase table scan.
  4. Click Scan selected.
    You will be redirected to the scanning progress, where you can monitor if the scanning process was successful or encountered any error.
  5. Click on HBase table to view the collected tables when the scan is finished.
  6. Add the needed HBase tables to Collections.

    Collections serve as an organization method to sort and bundle the tables into groups for the migration. You can create more collections beside the Default collection based on your requirements.

    After you are finished with sorting the tables to collections, you can start the migration process by creating the migration plan.

  7. Click Create Migration or select Migrations > Start Your First Migration.
    1. Select the source cluster, and click Next.
    2. Select the destination cluster, and click Next.
    3. Select the type of migration, and click Next.
    4. Select the collections that you want to migrate, and click Next.
    5. Provide the Knox token to access Cloudera Manager of the Data Hub cluster in CDP Public Cloud.
      1. Navigate to the destination Data Hub cluster.
      2. Select Knox Token from the list of services.
      3. Click Token generation, and provide the name and life of the token.
      4. Click Generate Token.
      5. Copy the generated token, and navigate back to the migration plan. Paste the token to the Knox Token field.
    6. Click Next.
      An overview of the migration plan is displayed. At this point, you can go back and change any configuration if the information is not correct. If the information is correct, click Create.
  8. Click Go to Migrations when the migration plan is successfully created.
  9. Click on the CDH to CDP PC or CDP Private Cloud Base to CDP PC migration to start the migration.
    The steps are displayed that are going to be completed during the migration.
  10. Click to start migration.
    During the HBase table migration, the source cluster is prepared with the HBase Replication Manager parcel. When the replication policy is submitted, click to finalize the replication policies.
When all of the steps are successfully completed, the migration of HBase tables from CDH or CDP Private Cloud Base to CDP Public Cloud is finished. You can start using the HBase tables on the destination Operation Database Data Hub cluster with the available services.