Local Archive

Local Archive is recorder-centric, storing recorded content from a single Recorder only. Local Archive is only available on servers assigned the TDM, IP, or Screen Recorder server roles. Local Archive relies on Recorder processes to determine the content to be archived.

You can archive 100% of the recordings from a Recorder. Optionally, as with Central Archive, you can set up rules (campaigns) to archive selected local content that meets defined criteria and set a schedule for archiving. You choose Compliance (100%) or Selective Local archiving when you define the local archive drive.

Selective Local archiving only stores specific content from the local recorder. If screens are recorded on a separate recorder, they are not archived.

Interactions Product that assists contact centers increase operational effectiveness and improves the customer experience through full-time recording, powerful quality monitoring, compliance/liability management, rich reports, and an intuitive, dashboard-style interface. created using the contingency serial number are archived when using Local Archive. A contingency serial number is assigned to a Recorder when an assigned serial number has exhausted its supply of INUMs. To learn more about how a Recorder can use multiple serial numbers, see the related information section.

Although the content to be archived is local to the Recorder, the drive used for storage does not have to be. You can store the recorded content on an RDX drive attached to the recorder. You can also archive it to a fixed SAN, FTP, Hitachi HCP, Amazon S3, Azure Blob Storage, GCS (Google Cloud Storage) or EMC Centera drive.

Once Archive starts moving recorded content into a repository, you can monitor archive performance.