DIVAreplicate and DIVAnet

Contact Us:

04-37831601

Catalog : Broadcasting > Front Porch Digital

Views : 3634

DIVAreplicate and DIVAnet are Front Porch Digital’s advanced disaster recovery, business continuance and content distribution solutions

for multisite DIVArchive-based content storage management (CSM). Many broadcast networks or media companies now operate multiple content production and distribution sites around the globe. Moving content seamlessly between these sites increases efficiency, lowers operational costs and enables disaster recovery strategies that support true business continuance. DIVAreplicate allows the connection of a main DIVArchive system to a Disaster Recovery (DR) DIVArchive system while DIVAnet supports any number of fully independent DIVArchive CSM systems connected together across any type of wide area network (WAN) to form a globally distributed content storage repository.

Link download for PDF file

http://www.mediafire.com/download/jsdvzok53uo72fl/DIVAnet_Brochure_Letter.pdf

Enterprise-Wide Content Federation

In addition to the clear advantage of WAN-based content mirroring and distribution across two Main and DR DIVArchive systems (DIVAreplicate) or any number of independent DIVArchive CSM sites (DIVAnet), an overall management layer – called Access Gateway – gives any control system a filtered or federated view of all content contained in the underlying DIVArchive systems. This federated view removes the complexity of control systems, such as automation or Media Asset Management (MAM) systems, having to be concerned with the specific location of desired content and automatically routes commands and requests to the appropriate system. Intelligent command routing, load balancing, global content distribution plans and an advanced user interface are all part of this enterprise-wide federation solution.

Disaster Recovery

DIVAreplicate takes content normally ingested and stored at the main site and automatically replicates it to a remotely connected DIVArchive DR site. This content replication, in whole or in part, allows a second site to take over broadcast distribution in the event of a failure, natural disaster or other catastrophe. It’s important to note that each DIVArchive site still operates independently with no dependency on the other site. Flexible business rules controlling replication can be configured specifically to meet your exact requirements. For example, the system could be configured to replicate only high resolution programs and then only during the overnight hours using only a portion of available WAN bandwidth.

Designed With WAN in Mind

Moving content across a wide area network (WAN) is more complex than local transfers. DIVAreplicate and DIVAnet have special features to handle security, variable bandwidth and resilience to network outages. These include intelligent load balancing between DIVArchive sites, a central manager to implement global content distribution plans, and global object-delete to support smooth resumption of operation in the event of connectivity loss. Content replication commands issued are tracked through the entire end-to-end process including all intermediary WAN transition stages. If for any reason content transfers can’t be completed due to network problems, the content is held in a buffer and transferred as soon as connectivity is restored. Global object delete requests will likewise be held in a pending state if connectivity is lost between DIVArchive systems and then resolved once communication is re-established. All content restore operations maintain efficiency and conserve WAN bandwidth by prioritizing locally stored content over remote sites.

Innovative Storage Policy Management

DIVAreplicate and DIVAnet greatly enhance the current storage plan manager (SPM) functionality. You can create rules that control content

replication, deletion and transcoding based on an expanded set of parameters including content type, location and age. These SPM functions could be set up, for example, to use DIVArchive integrated transcoding to reduce content bit rate before replication to another site.

Guaranteed Content Replication

DIVAreplicate and DIVAnet management functions enable administrators to compare or reconcile the content collections at two independent sites. This allows resynchronizing sites that may have been disconnected due to WAN outages or scheduled maintenance, or to trigger the first set of transfers upon DIVAreplicate or DIVAnet installation. During the reconciliation phase, administrators are presented with a recommend set of actions to resolve any discrepancies between systems.

DIVAreplicate/DIVAnet API

Building upon the existing DIVArchive API, DIVAreplicate and DIVAnet add enhanced content storage control functions to networked DIVArchive systems. Control applications, such as automation and MAM systems, can communicate with local and remote DIVArchive systems through a single API connection at the DIVAreplicate/DIVAnet layer with little or no change to their existing integrations with the DIVArchive API. Advanced “site awareness” is available via this API but is optional in most cases as the AccessGateway automatic command routing can make these decisions rather than placing the burden on the control systems.

Multisite Monitoring

Authorized users can monitor all activities of any underlying DIVArchive system by simply connecting our standard user interface to the ppropriate DIVArchive manager system or can use the same user interface to monitor global activities by simply connecting to the Access Gateway server. Transactions that span multiple DIVArchive systems are combined in the user interface for simplicity, especially in very busy systems. Security provisions can limit which content stored at any site can be viewed and controlled by any user or external application — an essential feature when different businesses share common disaster recovery sites.

Seamless Migration

You can add DIVAreplicate or DIVAnet to any existing DIVArchive system without disrupting current operations. External applications using the DIVArchive API will continue to operate with current functionality until those systems add the new DIVAreplicate/ DIVAnet functions.