Migrating data to CDP Private Cloud Base from CDH using Replication Manager
You can use CDP Private Cloud Base Replication Manager to migrate HDFS and Hive data from CDH source clusters to CDP Private Cloud Base target clusters. Before you replicate data using Replication Manager, you must consider a few guidelines.
Review the following points before you migrate the HDFS and Hive data from CDH clusters to CDP Private Cloud Base clusters:
- The supported source and target clusters and the corresponding Cloudera Manager versions must be in sync with respect to the cluster configurations.
- You must first upgrade your target cluster to CDP Private Cloud Base because this action ensures that your data on the source cluster is not corrupted or rendered invalid.
- You can upgrade the source cluster to CDP Private Cloud Base after the
data is migrated to the CDP Private Cloud Base (target).
In a typical production environment where multiple replication schedules are underway, the cluster upgrade process does not interrupt the data movement experience (migration). The only exception is when you are running the Hive replication policies or have any of them scheduled.
- After the data is migrated, verify that both the source and target clusters are upgraded to CDP Private Cloud Base.
For more information about upgrading CDH clusters, see Upgrading CDH to CDP Private Cloud Base.
You must also consider the following supported and unsupported scenarios pertaining to Replication Manager after you upgrade your CDH clusters to CDP Private Cloud Base clusters:
Cloudera Manager 6.3.1 as target cluster supports:
- non-high availability (HA) NameNode configurations.
- HDFS, Hive, and Sentry to Ranger replication.
- replicates only from source cluster versions 7.0.3 or 7.1.3.
Cloudera Manager 6.3.1 as target or source cluster does not support:
- high availability (HA) NameNode configurations.
- Ranger to Ranger policy replication.
- Ozone to Ozone replication.
- Iceberg tables to Iceberg tables replication.