> 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/system-requirements.md).

# System Requirements

What Tandem needs from XProtect, from your servers, and from your storage

### XProtect Versions

Tandem has been tested, starting with **XProtect 2026 R1**.

{% hint style="info" %}
Running an earlier XProtect version? Contact Vega Systems before deploying.
{% endhint %}

### XProtect Variants

Tandem is ideal for deployments on XProtect variants where you can install the recording server on its own VM or server machine, separate from the Management Server.

| XProtect product | Suitable                     |
| ---------------- | ---------------------------- |
| Corporate        | Yes                          |
| Expert           | Yes                          |
| Professional+    | Yes                          |
| Express+         | Check with Vega Systems Inc. |
| Essential+       | Check with Vega Systems Inc. |

### Server hardware

Tandem adds no server sizing requirement of its own. Size each member exactly as Milestone XProtect specifies for a recording server carrying that camera load, using the Milestone XProtect System Requirements.

These points follow from how the pair works:

* **Size each recorder in the pair for the full camera load.** Both members record from every camera in the pair, at all times. Neither is a half-loaded standby.
* **Size storage for the full retention period on each member.** Two full copies of the video mean the pair consumes roughly twice the storage a single recorder would.
* **Drive letters for storage profiles must be identical** between members of a cluster pair.

### Backfill headroom

When a member comes back from an outage, Tandem copies the video it missed from its peer. It first writes that content to a buffer on the recovering member, then merges it into that member's own timeline. The recovering member therefore needs free storage headroom to hold the buffered content while the merge takes place.

All recorders need this headroom capacity. Two things follow:

* **Free space is not automatic.** The recovering member still holds all its own pre-outage recordings—nothing was deleted while it was off. Its storage does not free up during an outage; it simply stops growing.&#x20;
* **The buffer can live anywhere that the member can reach.** The live recording drive, the archive drive, or a separate drive attached to that recorder are all valid. What matters is that the recovering member can access the capacity, not where it sits.

Size the headroom for the longest outage you expect a member to survive, at the cameras' recorded bitrate. A member with no free capacity cannot be backfilled, and the gap in its timeline remains until space becomes available.

### Software components

Tandem is lightweight and runs alongside XProtect.

| Machine                | Component                | What it does                                                         |
| ---------------------- | ------------------------ | -------------------------------------------------------------------- |
| Each recording server  | Clustering Service       | Pairs the recorders and keeps configuration replicated between them. |
| Each recording server  | Backfill Service         | Copies missed media to a recovered member.                           |
| Management Client host | Tandem management plugin | Configures and monitors each pair from Management Client.            |

Both services run continuously on each member. Neither adds meaningfully to recorder load, so no compute allowance beyond the native XProtect specification is needed. The Management Client component is a plugin only — it carries no video and holds no state.

### Time synchronization

Both members of a pair must take their time from the same source as the rest of the VMS. This is **required**, not recommended.

Tandem reconciles recordings between the two members by timestamp. It has no other way to know which second of video on one member corresponds to which second on the other. If the two clocks disagree, everything that depends on that reconciliation degrades:

* **Backfill misaligns.** Video copied from the peer is merged into the recovering member's timeline at the wrong offset, leaving apparent gaps on one side of the join and duplicated seconds on the other.
* **Failover shows a seam.** When playback crosses from one member's recordings to the other's, it jumps forward or backward by the drift amount.
* **Exported evidence becomes difficult to defend.** Two copies of the same incident carry two different times.

#### What to configure

* Point both members to the same time source as the Management Server and the rest of the VMS—typically the domain hierarchy via Windows Time on domain-joined servers, or a common NTP server otherwise.
* Allow NTP (UDP 123) from both members to that source.&#x20;
* Do not give the two members different time sources, even if both are accurate. Two well-behaved sources still drift relative to each other.

{% hint style="danger" %}
**Virtual machines.** Do not run hypervisor guest time synchronization and NTP at the same time. The two correct each other in opposite directions and produce exactly the drift Tandem cannot tolerate. Choose one: either disable guest time sync on both VMs and let each member use NTP, or disable NTP in the guests and ensure the hypervisor hosts themselves are synchronized to the VMS' time source.
{% endhint %}

### Media database encryption

XProtect can encrypt recorded media at rest. Tandem runs on an encrypted system, but [Media Recovery with Backfill](https://docs.vega365.com/tandem/recovering-from-recorder-failure/media-recovery-with-backfill.md) doesn't work when encryption is enabled—**media encrypted on one recording server cannot be decrypted on the other**, so backfill cannot copy recordings between cluster members.

Decide which you need before clustering.

|                                                  | Encryption off | Encryption on |
| ------------------------------------------------ | -------------- | ------------- |
| Two independent copies while both members are up | Yes            | Yes           |
| Failover with no gap in the recordings           | Yes            | Yes           |
| Recovery of content missed during an outage      | Yes            | **No**        |

Even with XProtect's encryption at rest, both record continuously, and failover is unchanged. The cost is the repair afterward: a recorder that was down keeps a permanent gap for the period it was off. The other member still holds that footage and still serves it to clients, so the video isn't lost to the system—only to that one recorder's timeline. See [Encrypt your recordings](https://doc.milestonesys.com/latest/en-US/standard_features/sf_mc/sf_mcnodes/sf_2serversandhardware/mc_encryptyourrecordings.htm) in the Milestone XProtect administrator guide.

* **Where encryption at rest is mandatory**, deploy Tandem without backfill and accept the permanent gaps on a recovered member.
* **Where it is not**, leave encryption off so both copies stay complete.

#### Edge Recording Exclusion&#xD;

Separate recorder pairs by assigning cameras that support edge recording and those that rely on Tandem Backfill. Assign edge-recording cameras to a Tandem Cluster with Backfill disabled; assign other cameras to their own dedicated redundant clusters with Backfill enabled. The two groups must not share a recorder.\
Backfill is unnecessary for edge-recording cameras. When a recorder in the pair comes back online after an outage, it independently retrieves the missing content directly from each camera's onboard storage. No peer-to-peer transfer between recorders is required.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2FTp3NzV3jwOgdQNCm6xJU%2Ftandem_edge_vs_backfill_cameras.png?alt=media&amp;token=7659d36a-7690-479e-abb0-094844c2582b" alt="" width="563"><figcaption><p>Keep Edge recording + Edge Backfill cameras on a dedicated Tandem Cluster</p></figcaption></figure>
