> 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/on-the-management-client/clustering-recorders/pairing-recorders-to-a-cluster.md).

# Pairing Recorders to a Cluster

Pair two recording servers into a single clustered recorder.

### Clustering

Clustering joins two recording servers into one recorder in XProtect. The secondary takes on the primary's recorder identity, receives its configuration, and begins recording the same cameras as a hot standby.

### Where to Start

The Tandem plugin appears in Management Client under **MIP Plug-ins → Tandem**, with two nodes: **Clustering** and **BackFill**. Go to the **Clustering** node.

Then, go to the **Configuration** tab on the right.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FA1iO0z0KdOk0OXZjcNbc%2Fclustering_prereqs.png?alt=media&amp;token=efb5bb4c-4423-4a8f-88f9-e0ac6a28f7ee" alt=""><figcaption></figcaption></figure>

### Step 1 - Before you start the clustering process

The Configuration wizard opens on a **Prerequisites** checklist. Tandem doesn't verify these for you—confirm each item on both servers before continuing.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FA1iO0z0KdOk0OXZjcNbc%2Fclustering_prereqs.png?alt=media&amp;token=efb5bb4c-4423-4a8f-88f9-e0ac6a28f7ee" alt=""><figcaption><p>Step 1 of 4 — Prerequisites</p></figcaption></figure>

| # | Requirement                                                                                                                            | Where to check                                                                                       |
| - | -------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| 1 | XProtect must have atleast two un-clustered recorders. The primary with or without any devices, and the secondary, without any devices | Both recorders must have been added to XProtect. Both visible under **Servers → Recording Servers.** |
| 2 | Identical drive letters on both servers                                                                                                | Live and archive storage must use the same drive letters on the primary and the secondary.           |
| 3 | Tandem services running on both servers                                                                                                | Tandem clustering and backfill services must be running on both these recorders                      |
| 4 | Secondary recorder is empty                                                                                                            | Remove all hardware from the secondary before clustering                                             |
| 5 | Valid Tandem license applied with at least one recorder pair license unused.                                                           | **Management Client → Basics → License Information**                                                 |
| 6 | Ports open between the two servers                                                                                                     | See [Network Requirements](https://docs.vega365.com/tandem/network-requirements.md)                  |

The example below uses two recording servers: **PRIMARYREC1**, which has four cameras, and **V33**, which has none. This is the expected starting state—all cameras on the intended primary, and none on the intended secondary.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FpBVZGSXoXXbykJ4402z3%2Frs_before_clustering.png?alt=media&amp;token=c1e2872a-d1b7-4384-bc23-720eb6a303df" alt="" width="484"><figcaption></figcaption></figure>

### Step 2 — Select the primary recorder

Choose the recording server that will be the primary in this cluster. Only unclustered recording servers are listed; the count of unclustered recorders appears beside the search box.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2F8BAhdTnr2hP0t7Z990l0%2FSelect_Primary.png?alt=media&amp;token=22411eb2-5b10-401c-ace3-23b88ae4d8cd" alt=""><figcaption></figcaption></figure>

**Choose the recorder that already has your cameras.** The primary keeps its cameras and configuration, and you copy its settings to the secondary you select next.&#x20;

Each row shows the recording server name, address, camera count, and status. The camera count is the quickest way to confirm you are selecting the right machine.

Your selection is confirmed at the bottom of the page. Select **Next: Select secondary**.

### Step 3 — Select the secondary recorder

Choose the recording server that will be the secondary for the selected primary. It must have no cameras — recorders that don't qualify are greyed out, and the page shows how many listed recorders are eligible.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FXE6c6ctN7YayjOsHpB7n%2Fselect_sec.png?alt=media&amp;token=25731394-0cc0-425f-ae4a-da69a255c4e4" alt=""><figcaption></figcaption></figure>

The primary you chose in the previous step is shown at the top of the page for reference.

{% hint style="info" %}
**The secondary takes on the primary's recorder identity.** When you cluster, the secondary's current identity is replaced.&#x20;
{% endhint %}

Select **Next: Confirm pair**.

### Step 4 — Review and cluster

The final step shows both recorders side by side, with the role each will hold after pairing.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FpO8oTi49kKsWY6sd3VpU%2Fpair.png?alt=media&amp;token=be80f8eb-f275-4e7e-97b2-b8b5380721c5" alt=""><figcaption></figcaption></figure>

|               | Primary                                                                      | Secondary                                                                     |
| ------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| After pairing | **Attached**                                                                 | **Headless**                                                                  |
| Behavior      | Keeps its cameras and configuration, and continues serving live and playback | Takes on the primary's identity and records the same cameras as a hot standby |

What happens when you pair:

1. The secondary takes on the primary's recorder identity.
2. The primary's configuration is copied to the secondary and kept in sync from then on.
3. Both recorders stream and record every camera. The primary stays attached to the Management Server.

Confirm that you understand the secondary's identity will be replaced, then select **Pair recorders**. The button stays unavailable until you tick the confirmation.

#### Clustering progress

Clustering runs in two phases, shown with a progress bar and a countdown to the next phase.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FMJy9RuPwvH9QuLIDYtfK%2Fclustering_in_progress.png?alt=media&amp;token=e6dbbca7-160d-43a3-ba91-c6c9de6e358b" alt=""><figcaption></figcaption></figure>

| Phase           | What it does                                                    |
| --------------- | --------------------------------------------------------------- |
| Clustering      | Joins the two recorders into a single recorder in XProtect      |
| Arm and monitor | Pushes configuration to the secondary recorder and synchronizes |

A deliberate pause occurs between phases while the secondary recorder settles. This is expected — leave the wizard open and let it finish.

When both phases are complete, the page reports **Pair is live**. Select **Pair another** to cluster a further set of recorders, or leave the wizard.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FcYLBp7f0mfK02VAutaaj%2Fclustering_complete.png?alt=media&amp;token=509da8a1-fa79-4528-9e8e-3495a2ce4f35" alt=""><figcaption></figcaption></figure>

### Monitoring a cluster

The **Dashboard** tab shows every cluster in the system.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FrBecsImenjzoClLbTnUG%2Fdashboard.png?alt=media&amp;token=29096b6f-f99d-4ab4-8459-c31937a6657c" alt=""><figcaption></figcaption></figure>

Four counters summarize the system:

| Counter        | Meaning                                              |
| -------------- | ---------------------------------------------------- |
| Total clusters | Clusters configured in this system                   |
| In sync        | Clusters where configuration is replicating normally |
| Failed over    | Clusters where the secondary has taken over          |
| Degraded       | Clusters needing attention                           |

Below the counters, each cluster is listed by its recorder name and recorder ID, with a status badge and a **Remove** button. Use the search box to find a cluster by recorder name or hostname.

Each cluster expands to show both members side by side:

* **State**
  * Active - this recorder is serving clients
  * Standby - this recorder is standing by to step in. It is recording from cameras.
* **Tandem Clustering Agent** — whether the agent is reachable on that member.
* **Config last synced** — when that member last received configuration.

The two timestamps will not always match exactly. A difference of minutes is normal; a secondary whose timestamp stops advancing is the signal to investigate.
