
RC-E User Manual
Management Client (RC-E Manager)
cameras or a group of cameras. This is done from the individual devices or from the device group, see Attaching
Individual Devices or a Group of Devices to a Storage Area (on page 58).
Effective Archiving
When archiving is enabled for a camera or a group of cameras, the contents of the camera(s)' database will
automatically be moved to an archive at regular intervals.
Depending on your requirements, you are able to configure one or more archives for each of your databases.
Archives can be located either on the recording server computer itself, or at another location which can be reached by
RC-E , for example on a network drive.
By setting up your archiving in an effective way, you can prune and groom your database storage area usage
significantly if needed. Often, it is desired to make archived recordings take up as little space as possible—especially
on a long-term basis, where it is perhaps even possible to slacken image and sound quality a bit. Effective pruning
and grooming can help ensure this and can be handled from the
Storage
tab (see "Storage Tab (Recording Server
Properties)" on page 65) of a recording server by adjusting several interdependent settings such as:
Recording database retention
Recording database size
Archive
retention
Archive
size
Archive
schedule
Encryption
Frames Per Second (FPS).
The size fields define the size of the camera's database, exemplified by the cylinder, and its archive(s) respectively:
By means of retention time and size setting for the recording database, exemplified by the white area in the cylinder,
you define how old recordings must be before they are archived. In our illustrated example, recordings are archived
when they have "sifted" down into the green area of the database cylinder, or in other words: when they are old
enough to be archived.
The retention time and size setting for archives define how long the recordings remain in the archive; recordings
remain in the archive for the time specified, or until the archive has reached the specified size limit. When these
settings are met, RC-E begins to overwrite old recordings in the archive.
The archiving schedule defines how often and at what times archiving takes place.
Encryption and FPS determine the size of the data in the databases.
To have recordings archived, all these parameters must be set up in accordance with each other. This means that the
retention period of a next coming archive must always be longer than the retention period of a current archive or
recording database. This is due to the fact that the number of retention days stated for an archive includes all
retention stated earlier in the process. Furthermore, archiving must always take place more frequently than the
retention period is set to, otherwise you risk losing data. If you have a retention time of 24 hours, any data older than
24 hours will be deleted. Therefore, to get your data safely moved to the next archive, it is important to run archiving
more often than every 24 hours.
Example:
These storage areas (image to the left) has a retention time of 4 days and the following archive
(image to the right) a retention time of 10 days. Furthermore, archiving is set to occur every day at 10:30,
ensuring a much more frequent archiving than retention time is set to.
Tip:
You can also control archiving by use of rules and events. See
About Rules and Events
(see "
About Events
" on
page 97) and
Events Overview
(on page 128).
On-Net Surveillance Systems, Inc.
57