> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/tandem/configuration.md).

# Configuration

Where each part of Tandem is configured, and in what order.

## Configuration

Tandem is configured in two places: on each recording server and in the Management Client.

Configure the services on the recorders first. The Management Client wizard pairs recorders that are already running and reachable, so the services must be in place before you can create a cluster.

### On each recorder

Two services run on every recording server in a cluster, each with its own tray icon and settings.

* **Clustering Service** — the account and connection it uses for the Management Server and its API security.
* **Backfill Service** — its Windows logon account, Management Server connection, API security, and shared folder credentials.

Configure both services on **every cluster member**. The settings are per recording server, and a member left unconfigured cannot take part in the cluster.

### On the Management Client

With the services in place, the rest is done from the Tandem plugin in Management Client.

* **Pairing Recorders to a Cluster** — the wizard that joins two recording servers into one clustered recorder.
* **Backfill Configuration** — enabling backfill per recorder, choosing its staging drive, and setting bandwidth throttling.

### Order of work

1. Install Tandem — see Installation.
2. Configure the Clustering and Backfill services on both recorders.
3. Pair the two recorders into a cluster.
4. Set the backfill options for each recorder.

Steps 2 and 4 are both per recorder, and both are easy to do on one member and forget on the other. Check each cluster from both sides before you rely on it.
