Core Configuration
The Core Configuration step defines the foundational replication parameters for the selected tool. These settings control how data is replicated, how offsets are managed, and how the replication infrastructure behaves.
MirrorMaker 2 configuration is organized into four sections.
| Field | Required | Description |
|---|---|---|
| Max Tasks | No | Maximum number of tasks for the MirrorMaker 2 connector. More tasks increase parallelism. |
| Replication Factor | Yes | The replication factor for internal topics created by MirrorMaker 2 on the destination cluster. |
| Policy Separator | No | The character used to separate source cluster alias from topic names in the replication policy. |
| Policy Class | No | The fully qualified class name of the replication policy. Controls how topic names are mapped between source and destination. |

| Field | Required | Description |
|---|---|---|
| Group ID | Yes | The consumer group ID used by MirrorMaker 2’s internal consumers. |
| Auto Offset Reset | No | Where to start consuming when no committed offset exists. Default: Earliest. |
| Poll Timeout ms | Yes | Maximum time in milliseconds that the consumer waits for new records during each poll cycle. |
| Request Timeout ms | No | Maximum time in milliseconds for consumer requests to the source cluster. |

| Field | Required | Description |
|---|---|---|
| Override Bootstrap Servers | No | Custom bootstrap servers for the producer. When set, the producer connects to these servers instead of the destination cluster’s default. |
| Override Security Protocol | No | Custom security protocol for the producer connection. |
| Retry Backoff ms | No | Time in milliseconds between producer retry attempts. |

| Field | Required | Description |
|---|---|---|
| Offsets Topic | No | The name of the internal topic used to store translated consumer group offsets. |
| Max Offset Lag | No | The maximum offset lag allowed before MirrorMaker 2 flags a warning. |
| Heartbeat Topics | No | Configuration for heartbeat topics used to monitor MirrorMaker 2 liveness and replication health. |

| Field | Required | Default | Description |
|---|---|---|---|
| Link Name | Yes | A unique name for the cluster link. | |
| Link Mode | No | Destination Initiated | The direction of the link. Matches the linking mode configured during infrastructure setup. |
| Include Data Rollback Support | No | Off | When enabled, the suite configures the link to support rolling back migrated data to the source cluster. |
Topic Settings:
| Field | Description |
|---|---|
| Auto-create Mirror Topics | When enabled, mirror topics are automatically created on the destination when new topics appear on the source. |
| Topic Config Sync Interval ms | How frequently topic configurations are synchronized from the source to the destination. |
Consumer Offset Sync:
| Field | Description |
|---|---|
| Enable Consumer Offset Sync | Toggle to enable consumer offset synchronization through the cluster link. |
| Sync Interval ms | How frequently consumer offsets are synchronized. |
ACL Sync:
Toggle to enable ACL synchronization through the cluster link. When enabled, ACL changes on the source are replicated to the destination.

| Field | Required | Description |
|---|---|---|
| License Key | No | Confluent Enterprise license key. Without a key, Replicator runs in trial mode for 30 days. |
| Tasks Max | Yes | Maximum number of replication tasks. Higher values increase parallelism. |
| Topic Poll Interval ms | Yes | How frequently Replicator polls the source cluster for new topics. |
| Auto-create Topics | No | When enabled, topics are automatically created on the destination cluster. |
| Sync Topic Configs | No | When enabled, topic configurations are synchronized from source to destination. |
| Preserve Partitions | No | When enabled, the destination topic maintains the same partition count as the source. |
| Offset Commit Topic | No | The internal topic name used for storing replication offset commits. |
| Destination Replication Factor | No | The replication factor for topics created on the destination. Auto-defaults based on the destination broker count, capped at 3. |

| Field | Required | Description |
|---|---|---|
| Pipeline Name | Yes | A unique name for the Orbit replication pipeline. |
| Enable Consumer Group Sync | No | When enabled, consumer group offsets are replicated to the WarpStream cluster. |
| Copy Source Cluster Configuration | No | When enabled, topic-level configurations from the source cluster are applied to the destination. |
