> 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/xport/use-cases/load-balancing-between-recorders.md).

# Load Balancing Between Recorders

Safe Volume Reallocation

## Background

A large enterprise initially deployed some Recording Servers to manage all their cameras using a shared SAN-based storage architecture. Each Recorder was connected to multiple iSCSI volumes that collectively stored all video archives.

The system performed well initially when the compute and camera loads were balanced. However, over time, several factors increased the computational demand: higher camera resolutions and frame rates, additional analytics modules requiring data from these recorders, and extended retention periods that increased media database activity. As a result, the existing Recorders faced **compute saturation**, even though the shared storage array still had adequate capacity.

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2FDrDemjMaI2NE1FtwGT6e%2FCompute_Saturation.png?alt=media&amp;token=7d34d189-2af8-4321-976b-2c46b503bf57" alt="" width="375"><figcaption><p>Deployment with Shared SAN, Compute Saturation</p></figcaption></figure>

## Problem

To resolve the compute bottleneck, the customer planned to add new Recording Servers to balance the camera workload more evenly. The goal was to distribute the total number of cameras evenly across all Recorders. However, since **each storage volume in XProtect is exclusively owned by one Recording Service**, it was not possible to directly reassign existing volumes from the original Recorders to the new ones. Manual reassignment would lead to catastrophic data loss because the new Recorder cannot safely take ownership of a volume that contains another Recorder's media database.

## Solution: XPort Volume Migration

The **XPort Volume Migration** workflow enabled safe redistribution of existing volumes across all Recording Servers without reformatting or reindexing:

* XPort identified the storage volumes currently owned by each Recorder.

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2FDByk2kLdDLAx6P4yYulp%2Fchoose_source_volume.png?alt=media&amp;token=6705f017-ded6-4449-a364-b79a9d258afa" alt="" width="563"><figcaption><p>List Volumes on a Recorder</p></figcaption></figure>

* For selected volumes, it automatically quiesced recording and enabled a clean detach from their original owners.

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2FgcB0wYk7Vp2igLC1Zg7I%2Fmigrate_devices.png?alt=media&amp;token=accbd0a2-8aac-4022-bb3c-86167083037b" alt="" width="563"><figcaption><p>Migrate Devices</p></figcaption></figure>

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2FOBbmgCuDfuQXKNn8kXjP%2Fvolume_unmount.png?alt=media&amp;token=a63476c3-4d9f-4cc9-96d1-fd10aba68432" alt="" width="563"><figcaption><p>Volume Unmount</p></figcaption></figure>

* The same volumes were reassigned to the destination Recorders, preserving their media databases.
* After media database rehydration, the new Recorders assumed control of both live recording and playback from those volumes, with complete database integrity.

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2FdVKxZYDwDbGuwP9x9miE%2FRehydrate.png?alt=media&amp;token=d3b73418-24cb-4029-9d24-f1c431971d33" alt="" width="563"><figcaption><p>Media Database Rehydration on the Migrated Volume</p></figcaption></figure>

* A PDF report captured the journey for future audit purposes.

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2Ftq1xTqrklDkOpMoskM8m%2Fpdf_report.png?alt=media&amp;token=de49eef4-5b18-4015-9288-4c4821628c63" alt="" width="563"><figcaption><p>Report</p></figcaption></figure>

## **Outcome**

<figure><img src="https://771655570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxj7X0c61rEOwTqSjg2jo%2Fuploads%2FzYxgqGrzxeIL34B9ZGpV%2FRebalanced_Deployment.png?alt=media&amp;token=d62b4b9a-3879-4919-be93-4c50545f9ccb" alt="" width="563"><figcaption><p>Rebalanced Deployment</p></figcaption></figure>

* **Balanced Compute Load:** Camera workloads were evenly distributed across all Recorders.
* **No New Storage Required:** The existing SAN or NAS infrastructure was reused without modification.
* **Zero Data Loss:** All previously stored media databases remained intact and readable by their new Recorder owners.

## **Summary**

> As systems grow, compute demand often increases faster than storage utilization.\
> XPort Volume Migration enables controlled, lossless reassignment of existing storage volumes between Recording Servers — allowing balanced performance without adding new storage.
