Symphony Server
3.
To specify a storage path, complete the following tasks in the
Video Storage
section:
a) Specify the path to which Symphony should save footage files.
b) To add another storage path, click
Add Another Path
and specify the path.
c) To save footage files to only one storage path, select
Failover
.
Symphony attempts to save footage files to the first path in the list. If that path is not
available, Symphony attempts to save footage files to the next path in the list.
d) To save footage files to all storage paths, select
Redundant
.
e) Select the path from which Symphony should read footage files in the
Force disk reads
from
.
4.
To specify a secondary (archive) storage path, complete the following tasks:
a) Select
Archive video to secondary storage path
.
b) Type the path to which Symphony should save footage files.
You must type a secondary (archive) storage path for each of the primary storage paths.
c) In the
Days to store before archiving
field, set how many days must occur before
Symphony saves the footage files to the secondary (archive) storage path.
This value must be less than the
Limit the number of days video is stored
value.
5.
To set a limit based on the amount of disk space left, set the disk space in the
MB
field or the
percentage of disk space in the
%
field.
6.
To set the maximum number of days for which Symphony can retain footage files, select
Limit
the number of days video is stored
and set the number of days.
7.
To retain metadata after Symphony deletes footage files, select
Keep metadata longer
and set
the number of days.
8.
To copy footage files generated during a failover back to the restored primary server from the
redundant server, select
SAN Failover mode: Copy files to owner server
.
Both the primary server and redundant server must have read and write permission for the
storage paths on each server.
9.
In the
Cameras
list, define any storage paths specific to cameras.
By default, Symphony saves footage files from all cameras to the storage paths.
10. Click
Save
.
Configure overload protection
You can configure a Symphony Server to move cameras to another server when the CPU load grows
too great.
1.
In the server configuration interface, click
Settings
>
Servers
.
2.
Select a server and click
Overload Protection
.
3.
Select whether to move cameras to a different server when the CPU load is too high.
4.
Select whether to use redundant servers.
5.
Set the CPU threshold (in percent).
6.
Set the polling frequency (in seconds).
7.
Set the maximum number of cameras to move to the new server.
8.
Click
Save
.
Server redundancy
Symphony supports server redundancy in server farms. If a Symphony Server stops responding, the
camera and device processing moves to another Symphony Server.
A primary servers actively performs camera and device processing. When failover occurs, the
primary server becomes a redundant server.
Senstar Symphony User Guide
47
