Initial Server Deployment

Overview

EchoSystem Server (ESS) deployment requirements are dependent on the factors covered in the previous section and are therefore unique to each institution. Most initial deployments will follow similar usage and sizing patterns. The recommendations and diagram in this section are provided as an example of a common initial deployment scenario. These recommendations are suited for deployments consisting of 1-10 capture appliances (or Classroom Devices) and 25 Personal Capture users generating up to 50 hours of capture per day, total. They also consider the likelihood of capture growth and server expansion.

Echo360 engineers can discuss specific deployment and server sizing needs.

Initial Recommendations

This example deployment scenario requires the following system configuration:

• One ESS computer meeting the recommended requirements with a configuration according to these suggestions:
  • Supported third-party database server on the ESS computer
  • ESS native web services on primary network interface
  • ESS native streaming services on primary network interface
  • ESS native file transfer services on secondary network interface

• One EchoSystem Media Processor computer meeting the recommended requirements based on daily capture hours and desired turnaround time as follows:
  • 25 daily capture hours with same day turnaround time
  • 50 daily capture hours with next day turnaround time

• Local ESS storage, Network Attached Storage (NAS) or a Storage Area Network (SAN). Initial storage capacity depends on data retention policies, discussed in Deployment Planning. Plan for storage capacity at 500 GB to 4 TB for the first two semesters or terms.

Diagram

The illustration below shows a common initial deployment scenario. It consists of the following:

• Capture devices
• An EchoSystem Server (ESS)
• One or more media processing servers
• An optional (but recommended) storage server

Click for larger image