Server Labeling

Label the recorders as Primary or Secondary.

Introduction

Before RMF can do anything, it needs to identify which recorders are the primaries (the “live” capture points) and which are the secondaries (the backups). During the Server Labeling step, you tag each recorder as either Primary or Secondary. RMF then builds its device list exclusively from these labeled servers; anything left untagged is treated as out of scope, and its cameras never appear in the UI or participate in synchronization or failover. In short, no label, no redundancy—so be sure every recorder that should participate is labeled before you move on to pairing.

Prerequisite

Complete Architecture Selection

Label the Servers

Follow these steps to label the servers.

Note: RMF needs a minimum of two recording servers for labeling.

  1. Select Label Servers.

Label Servers

a. For an Independent architecture, the following screen appears:

Login Screen—Independent

Note: You must log in with administrator privileges.

Click Connect at the bottom right corner of the screen to continue.

Connect Option—Independent

b. For Federated/Single Site, the following screen appears:

Login Screen—Federated/Single Site

Note: If your XProtect architecture is Federated, you must log in to the Parent Management Server.

Click Connect at the bottom right of the screen to continue.

Connect Option—Federated/Single Site
Unlabeled Servers
  1. For more details, click the Help icon in the bottom left corner.

Help Icon
Help Description
  1. Label at least one server as Primary and another server as Secondary.

Note: You must select and drag and drop the recording servers to classify them as Primary and Secondary.

Primary Recording Server
Secondary Recording Server
  1. Click the tick mark at the bottom of the screen to save the changes.

Save Icon

5. Click Save in the Milestone toolbar to save the changes.

Save Icon—Milestone Toolbar

Last updated