The system includes powerful tools for automated data management. Data management consists of 3 areas:
- Data retention: data retention policies are responsible for managing the lifecycle of the data in the system. Retention policies allow moving data from one storage location to another, managing retention period, or deleting/disposing of recordings.
- Data processing: data processing policies can provide additional information by analyzing certain aspects of the data (e.g. transcribing speech to text), or convert recordings from one format to another.
- Data import: data import policies drive the data import process which allows ingesting different data into the system.
Data management policies
Administrators are able to define archiving, deletion, and other processing rules based on various filter criteria.
Policy execution is carried out by the various services on the Media Repository and/or Recording Servers.
For more information on Data Management policies, see the corresponding article.
Data retention period configuration
Policies that are managing the lifecycle of recorded media are referred to as Data Retention Policies. The various methods of the configuration of data retention periods are described in the Data retention article.
Storage and export targets
You can define multiple different folders where media is stored by the system or the media has to be exported to. These are called Storage and export targets.
Storage and export targets can point to Verba Media Repositories, SAN volumes, NAS volumes (with UNC path), NetApp SnapLock, EMC Isilon SmartLock, AWS S3. Azure Storage and many more.
Data management policies that are set up with an action to move or copy media files need a storage target defined to specify the location to move/copy to.
Here are a couple of examples for the use of storage targets with the appropriate data management policies:
- to separate media of different users/groups in your organization
- add additional disks to the system
- offload system disks to e.g. SAN disks automatically
Resilient storage and archiving
The system supports the resiliency and high availability options of the underlying storage platforms. The system also offers a workaround if storage level resiliency is not available. For more information, see Resilient storage and archiving.
Large scale deployments
It is critical to understand how the system should be configured in the case of large-scale deployments where the system needs to potentially handle 100s of millions or billions of calls. For more information, see Best practices for large databases.
Data can be imported into the system from several sources. These sources together called Import sources.
Import sources can contain recordings, CDR data, and other archives.
There are two ways to upload the recorded media files from the Recording Servers to the final storage infrastructure.
- Configure uploading on the Recording Servers (server-level setting) individually.
To do this, go to Administration > Verba Servers > Select your recording server > Change configuration settings. In the configuration tree expand Storage Management > Upload.
Enable uploading and specify the storage server. This method only works if you use your Verba Media Repository or standard network storage as your media storage.
- Configure uploading via Data Management Policies using the Upload policy action. This is a system-wide configuration applying to all recording servers (where enabled) which allows you to create filters and upload to multiple storages based on conversation metadata.
This method also supports uploading to NetApp SnapLock, EMC Isilon SmartLock, EMC Centera, Hitachi Content Platform, and others. For the latest list of supported platforms, refer to the Storage and export targets article.