> 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/un-pairing.md).

# Un-Pairing

Reverse clustering from the Dashboard

## Removing a cluster

Remove a cluster from the **Dashboard** tab of the Tandem plugin.

{% hint style="warning" %}
**Removing a cluster ends redundancy for those cameras.** Configuration replication stops, and the cameras are no longer recorded as two copies from the moment you remove the cluster. Remove a cluster only when you intend to stop protecting those cameras, or as a deliberate step before repurposing the recorders.
{% endhint %}

### Step 1 — Select Remove

On the Dashboard, find the cluster you want to remove and select **Remove**.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2F2kFYrqDzDF4ErKIsT0YS%2Fclick%20on%20remove.png?alt=media&amp;token=3483ca53-aa9f-46cc-a88f-c40d4861c250" alt=""><figcaption></figcaption></figure>

Each cluster is listed by the recorder name and the recorder ID it holds, so check these before selecting **Remove** on a system running more than one cluster.

### Step 2 — Confirm

A confirmation dialog lists the primary and secondary recording servers and their hostnames, so you can verify you are removing the right cluster.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FYLVaptq2Tra45FWRAYIX%2Fclick_yes_to_remove.png?alt=media&amp;token=1902e6a2-d175-431e-a1d5-0e758402fcbf" alt=""><figcaption></figcaption></figure>

The primary is unaffected — it keeps its cameras, its configuration, and its recordings, and continues serving clients exactly as before. The secondary is released, as described below.

### What happens to the secondary

When the cluster is removed, the former secondary:

* **Loses its cameras.** All cameras are erased from the secondary, and it stops recording.
* **Reconnects to the Management Server.** It is no longer headless.
* **Becomes a standard recording server**, available for use in the system like any other.

Its media database is **not** erased. The recordings it made while clustered remain on its storage, and the administrator must erase them and repurpose the storage as needed.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FmcCQbXBl7bz0dDmnfEKd%2FUnpaired_state.png?alt=media&amp;token=95dfac06-7526-4faa-a77d-298d86a20590" alt=""><figcaption><p>Dashboard with no clustered recorder pairs</p></figcaption></figure>

{% hint style="warning" %}
**Retain anything you need before removing the cluster.** Once the cameras are erased from the secondary, it stops producing a second copy of the video. Export or archive any recordings you need to keep before removing the cluster, not after.
{% endhint %}

### Reusing the released recording server

Because the secondary's cameras are erased as part of the removal, the server meets the wizard's requirement that a secondary have no hardware on it. It can be clustered again — as a secondary in a new cluster, or used as an ordinary recording server.

Erase its media database first if you need the storage for a new purpose. A clustered secondary records the same cameras as its primary, so it uses the full retention for that camera set and will not free up space on its own.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2Fc3CnSs6NtqFXESsJfn3f%2Frecorder_returned_for_repurposing.png?alt=media&amp;token=6ca01a7b-7922-437a-a08e-af25d58dcf68" alt="" width="484"><figcaption><p>Estwhile Secondary "V33" returns to the Recording Server list as an "Unknown" recorder.</p></figcaption></figure>
