Archival Service
The Archival Service in VRS is responsible for managing long-term storage of recording files that accumulate over time and consume significant disk space. It supports two operational modes to offer flexibility in storage management.
Archive Only
Copy & Archive
Archive Only
Archive Only moves recording files from the Recorder to the SFTP server once they exceed the configured retention period (X days).
A retention period can be configured in the Archive Days config. A retention period of 3 days means recordings are retained on the Recorder for 72 hours.
Any recordings older than the configured retention period are automatically archived to the SFTP server.
Archived recordings are highlighted with a grey background on the interface.
Users can continue to search, access, and play archived recordings directly from the interface.
Example
If archival is configured with a retention period of 1 day and the archival container starts running on 4 June at 5:00 PM, then the 24-hour retention period completes on 5 June at 5:00 PM. At that time, the system archives all recordings created before 4 June at 5:00 PM, as those recordings are older than the configured retention period of 24 hours.
Copy and Archive
Copy and archive first copies the recordings from the Recorder to the remote archival server and then remove them from the Recorder after the configured purge period has elapsed. The following two configurations are available in this mode:
Copy Time
Purge Days
How It Works
At the configured copy time, the system copies all eligible recordings from the Recorder to the remote archival server.
On subsequent runs, only recordings created since the previous copy operation are transferred, preventing duplicate copies.
Once the configured purge period is reached, recordings that have already been successfully copied to the archival server are removed from the Recorder.
Example
The copy time is set to 6:00 pm on 01 June, and purge days are set to 1 day.
The copy job executes for the first time.
All recordings available on the Recorder up to 01 June 06:00 PM are copied to the archival server.
The original recordings remain available on the Recorder.
02 June – 06:00 PM
The copy job executes again.
Recordings created between 01 June 06:00 PM and 02 June 06:00 PM are copied to the archival server.
Recordings that were copied during the previous run (on 01 June 06:00 PM) have now reached the configured purge period of 1 day (24 hours).
These recordings are therefore removed from the Recorder while remaining available on the archival server.
03 June – 06:00 PM
The copy job copies recordings created between 02 June 06:00 PM and 03 June 06:00 PM.
Recordings copied on 02 June 06:00 PM are now 24 hours old and are purged from the Recorder.
This cycle continues daily, ensuring that recordings are first copied to the archival server and then automatically removed from the Recorder after the configured retention period.
Stream Deletion
Streams are created once the files are recorded on the server. These streams are incomplete chunks of complete recording files, which are temporarily stored at a place to be mixed to become one meaningful conversation. Once these streams are mixed and stored in the session directory, there is no further use for them, and they occupy space. Hence, it is important to get rid of these files. Stream deletion plays its part in the removal of unnecessary stream files that have no further purpose to serve. These stream deletion services can also be set manually. We can set the number of days before all the files will be deleted.
Limitations:
Archival service configuration from the VRS interface is only supported for Cisco deployments.
Calls cannot be manually deleted.
Archived recordings cannot be retrieved.
Manual archiving of calls is not supported.
Only one archival mode can be active at a time; both cannot run simultaneously.
Recordings of Outbound EFCX Calls can’t be archived.
Always ensure that the housekeeping retention period is shorter than the Archival Interval. (If the archival service retention period is set shorter than the housekeeping job interval, conflicts may occur between the archival service and Rsync.)