Media storage in Avaya Aura MS Content Store

Last Updated : May 16, 2019 |

The Content Store component of Avaya Aura® Media Server (MS) stores media and other files for hosted applications. Content Store provides a reliable, highly available, and persistent storage capability for Avaya Aura® MS. Any application with storage needs that align with the functionality of Content Store can use Content Store. However, not all applications must use the Content Store.

Content Store has an organized storage space consisting of Namespaces that include Content Groups which contain the actual content. Namespaces are the top level containers, under which Content Group containers exist. Namespaces and Content Groups can be considered analogous to folders. Actual content is stored by Content ID within each Content Group. A Content ID is analogous to a filename.

The following example shows the structure of Content Store:

Namespace_I
      ContentGroup_A
         Content ID1
         Content ID2
      ContentGroup_B
         Content ID1
         Content ID2
   Namespace_II
      ContentGroup_A
         Content ID1
         Content ID2

To provide high capacity and high availability, Content Store is scaled automatically with the cluster. Content Stores are automatically enabled on each media server in a cluster. The application content in the Content Stores of a cluster is synchronized automatically.

There is a master Content Store configured on both the Primary and Secondary servers of a load sharing cluster or on the Primary and Backup servers of a High Availability cluster. The dual master Content Store configuration provides full hardware and functionally redundancy. Standard cluster nodes provide Content Stores which contain synchronized content for local access.

Content Stores communicate with each other when handling requests. A connection to any one Content Store in a cluster is sufficient for any client application. Data integrity and synchronization in a cluster are handled automatically by the Content Store peers. However, it is more efficient to provision new media files directly to one of the master Content Stores. When a content modification request is received at Standard node Content Store, it is first forwarded to one of the master Content Stores in the cluster for processing.

For examples of content organization and additional information on Content Store functionality, see Using Content Store in Using Web Services on Avaya Aura® Media Server.