1. Introduction

eMAM is an all-in-one, web-based Digital Asset Management (DAM) software system designed to organize, share, and collaborate digitized information such as audios, videos, images, and documents. EMAM has taken a ground-breaking approach to create a flexible, feature-rich, and modular digital asset management platform to meet asset management requirements of individuals, as well as major enterprises. 

EMAM can offer basic hardware specs for the different packages and platforms, but it is ultimately up to the Reseller/ SI or cloud vendor to finetune the hardware specs with their offerings and the customer’s requirements. This document is meant as a starting point guide. 

Here’s a comparison chart on different eMAM products:

FIGURE 1- EMAM PRODUCTS COMPARISON CHART

2. eMAM Vault system

eMAM Vault is a powerful system to manage media processing, storage and archive in any number of cloud or local/on premise environments. The eMAM web interface can manage the storage, processing, and archive of media. Users can quickly search human or AI tagged media, browse, and preview proxy copies of media from any connected devices. Media can be downloaded or delivered to any location. A range of transcoding systems can make different formats as needed. Media can be automatically or manually moved to permanent, low cost local or archive, but all media remains searchable. Needed media can be restored, with some configurations supporting partial file restore.

eMAM Vault can run on one or two servers or VMs to support 10 active defined users. It provides excellent value for basic system, which can be expanded to include additional (or unlimited) users, server licenses for additional locations, artificial intelligence/machine learning tagging, additional workflow features, and scaling/disaster recovery options. 

Main functionalities of eMAM Vault are:

5. Monitor the watch folders for incoming files
6. Automatically transcode the incoming source files and prepare web-based proxy copies and other platform files.
7. Index and move the source files and proxy files to connected storages.
8. Deliver the content from managed storages to external locations.
9. Archive the files to NAS storage or the LTO library managed by our partner 3rd party Archive vendors. 

https://www.emamsolutions.com/tech-partners/

6. Restore (including partial) the files to connected disk storage.

Click Here to know more about eMAM Vault. 

2.1 eMAM Database/Web/Application Nodes

In eMAM Vault system configuration, eMAM database, web and application nodes are installed in one server. We recommend keeping the database and log files in a RAID10 array with daily backup configuration. For the high transcoding requirements, we recommend running the server based transcoding engine and eMAM application server components from a separate server.

• The eMAM Web Node consists of software components; eMAM Gateway and eMAM Director and are pointed to the eMAM Database running in the same server. eMAM Director application will be deployed in the same server and these components will be pointed to eMAM Gateways running in the same server.
  
• The eMAM Application Node consists of software components; eMAM Delivery Service, eMAM Cloud Connector, eMAM Ingest Service and eMAM Archive Service and are deployed in the same server or a separate server depends on the ingest, archive and delivery volume. All these application components are deployed as backed windows services and these components will be pointed to eMAM Gateways.
• The eMAM Database Node consists of a set of Stored Procedures, Functions, Tables and other configurations. The eMAM Database Node can be hosted in Microsoft SQL Server. eMAM uses less expensive NAS storage or LTO tape library as archive storage. Content can be kept in both online disk storage and archive storage. Disk retention rules settings are available in eMAM to automatically move the content from disk storage to archive. Content from the archive can be restored to online disk storage or it can be delivered outside eMAM in any desired file format. eMAM supports partial restore for supported broadcast file formats.  EMAM recommends LTO library to preserve and protect the content in archive for long term. eMAM requires third party software to manage Robotic LTO libraries.
  

3. Server Specifications

The eMAM Vault software package consists of one eMAM App Node, one eMAM Web Node and one eMAM Database Node . In eMAM Vault configuration, eMAM software components can be deployed in one server.

Basic server hardware requirements for eMAM Vault are as follows:

4. Network Diagram

Below are high level network diagrams for eMAM Vault system installed on-prem or on cloud or in a hybrid environment.

4.1 On Prem Diagram

FIGURE 2- ON PREM DIAGRAM

4.2 Cloud Network Diagram

FIGURE 3- CLOUD NETWORK DIAGRAM

4.3 Hybrid Network Diagram

FIGURE 4- HYBRID NETWORK DIAGRAM

FIGURE 5- FIREWALL PORTS

6. Need Help

      Please contact your Sales Representative for details. sales@emamsolutions.com, +1.888.808.3856

7. Appendices

7.1 Archive Appliance / Archive Server

This server is required to manage a robotic LTO library. eMAM Archive module will interface with the archive server/appliance to perform archive, restore and partial restore functions from LTO tapes. 

https://www.emamsolutions.com/tech-partners/

7.2 Transcode Appliance / Transcode Server

eMAM requires a transcoder to create .h264 MP4 proxy files for eMAM. eMAM Ingest and delivery modules will interface with the transcode server/appliance to perform transcodes. Transcoding is done by a 3rd party partner. In eMAM Vault, in most cases you may use the same server that is running eMAM.

https://www.emamsolutions.com/tech-partners/

7.3 Online disk storage

eMAM stores the original and proxy files in an online disk storage for immediate access. Storage size is determined based on the daily ingest volume and the amount of content needs to be kept in the online disk storage. eMAM has built in options to move the content from online storage to archive storage based on storage threshold, archive threshold (days) and other archive rules. eMAM uses NAS, DAS or SAN storage as online disk storage depends on the customer requirements. Additional third-party software may require connecting to the multi-write SAN volumes. ** Please note – eMAM uses windows service users that must have read/write/delete access to the Storage. This in most cases requires the same user is also a valid user on the storage.

7.4 Cloud Storage (Optional)

eMAM can store the content in Object Storage buckets. The eMAM Cloud connector can upload the original content and proxy files into separate cloud storage buckets. Content that exist in AWS S3 buckets can be presented through Amazon CloudFront (CDN) URL within eMAM. For example, if somebody tries to preview a video from Los Angeles, the video will be loaded from a datacenter in Los Angeles. If somebody tries to preview the same video from London, the video will be loaded from a datacenter near to London. Cloud storage can be considered as an archive storage too.

Purchase the cloud services from a cloud vendor and provide the account configuration details to eMAM implementation team. (Sample cloud vendors below)

1. https://aws.amazon.com/s3/
2. https://aws.amazon.com/cloudfront/ 
3. https://azure.microsoft.com/en-us/services/storage/ 
4. https://cloud.google.com/storage/ 
5. https://wasabi.com