Upload policy
This article provides a description of the upload data management policy. A data retention policy configured with the upload action is used for specifying the final storage location of the recorded conversations. Recording Servers store the recorded conversations on their local disk temporarily while recording. After the recording is done, the files need to be moved to the designated storage location(s).Â
Each policy you define can contain a different storage location (previously added as a storage target) and a set of filters to determine which conversations should be uploaded to that location. These filters are based on the metadata stored in the database for each conversation. This is a good way to have separate storage locations for conversations of different users, groups, etc.
The system supports 2 types of upload policies:
- Direct upload policies:Â direct upload policies are designed for uploading large amounts of data with minimal impact on the database. It uses the user-extension configuration (instead of the database) to determine which policy has to be applied for the conversation recorded on the server. It is the recommended option, especially if it is a large installation.
- Upload policies: normal upload policies are designed to upload data with complex and flexible policy filtering settings. It uses the database to determine which policy has to be applied for the conversation recorded on the server. It is not recommended for large volumes due to the increased database load.
The following table summarizes the two upload policy options:
 | Direct Upload Policy | Upload Policy |
---|---|---|
Place of execution | Recording Server | Recording Server |
Suitable for Large Volumes | Yes, recommended | Yes |
Data Types and Source Platforms | Any | Any |
Database Query / File Based | File | File and Database Query |
Filters | Conversation Type Source Platform 2N Source | Any |
User Assignment | Yes (policy filter configuration) | Yes (user/extension configuration) |
Audit Log | Yes | Yes |
Configurable Schedule | No | No |
Enabling policy based upload
Since upload policies are executed by the individual Recording Servers instead of the Media Repository (unlike all other policy types), you will need to enable policy based uploading on the server level in the configuration of each Recording Server (or using the configuration template).
Step 1 - Open the Verba Web interface, go to Configuration / Servers, then select your Recording Server.
Step 2 - Click on the Change Configuration Settings tab and in the configuration tree, go to the Storage Management / Upload node.
Step 3 - Set Policy Based Uploading Enabled to Yes.
Step 4 - Save the configuration then repeat these steps for each recording server in your system. Finally, execute the changes.
Configuring direct upload policy
To create an upload policy, follow the steps below:
 Step 1 - Create a Storage target for your policy
Step 2Â - Follow the generic policy creation steps described on the following page:Â Data management policies
Step 3 - Select Upload as the action
Step 4 - Enable the Direct Upload option
Step 5 - Select the Destination Storage Target you created from the list
Step 6 - Optionally enable related actions such as Voice Quality Check, Encryption and Signing.
Step 7 - Configure Filtering Criteria to specify which conversations should be exported by this policy
Configuring upload policy
To create an upload policy, follow the steps below:
 Step 1 - Create a Storage target for your policy
Step 2Â - Follow the generic policy creation steps described on the following page:Â Data management policies
Step 3 - Select Upload as the action
Step 4 - Select the Destination Storage Target you created from the list
Step 5 -Â Optionally enable related actions such as Voice Quality Check, Encryption and Signing.
Step 6 - Configure Filtering Criteria to specify which conversations should be exported by this policy