Activate a new destination cluster
If you have not prepared a cluster in advance to serve as an alternate destination in a failover scenario, then you must install the DLM Engine, configure the clusters for use by DLM, and pair the clusters before you can create new replication policies and begin copying data to the new destination.
You must have the name of the cluster you want to configure as the new destination.
- Identify the Ambari-managed cluster to use as the new destination.
- Install the DLM Engine on the new destination, if it is not already installed. For more information, see Installing DPS Services, Engines, and Agents.
Follow the instructions in Setting Up the DPS Services for the
following tasks, as needed:
- Register Clusters with DPS
- Enable Services
- Pair the clusters you are using as source and destination, if they are not already paired. For more information, see Cluster pairing.
Ensure that the HDFS folders or Hive databases to be copied either do not exist or
are empty on the new destination cluster.
This is required prior to bootstrapping data from the source cluster to the destination cluster. Otherwise, the initial copy job fails.
Create and submit new replication policies between the source and destination
The first time a new policy is submitted, the entire contents of the source dataset is copied to the destination. Depending on the size of each dataset, these initial bootstrap copies can take a significant amount of time. After the initial copy, subsequent copies are incremental.