Side-car migration mechanism is best employed when you may have tighter service-level agreements that preclude an extended, multi-hour downtime for your workloads. This process aims to minimize downtime on individual workloads while providing a straightforward roll-back mechanism on a per-workload basis.
This mechanism involves configuring a new greenfield CDP Private Cloud Base cluster on a second set of hardware, consisting of a few dense storage nodes and several compute nodes. The side-car migration breaks down into three major phases.
- First, build and configure the new CDP Private Cloud Base cluster.
- Second, configure a replication process to provide periodic and consistent snapshots of data, metadata, and accompanying governance policies.
- Third, deploy the workloads onto the new cluster, test them, and flip them into a production state after validation.
After you move the workloads, disable them on the legacy cluster. You will temporarily have production workloads running across multiple clusters during the migration period.