Mongo-header

Backup and Recovery for MongoDB

The Results

Datos IO RecoverX provided this media and entertainment customer with the ability to perform daily backups for compliance requirements, recover in the event of operational failures, all without burdening operational efficiency.

The Customer

media-ent

Our customer is a North American-based leading entertainment discovery platform company that provides personalized entertainment. This organization has ~1,800+ employees worldwide. Their end customers include Spotify, Shazaam, iTunes and Google.

The customer deploys an entertainment guide application on a MongoDB database because of its flexibility of schema, ease of use, and scalability given the high-volume nature of their applications. Specifically, they use multiple MongoDB clusters, both sharded and unsharded configuration. They store entertainment content metadata for audio/video programming, as well as sensitive customer data such as name and address.

The Problem

This customer required a durable backup and recovery solution that is purpose-built for MongoDB, and one that would meet internal IT standards. They initially considered native backup and recovery capabilities of MongoDB, but the complexity of deployment, extremely high TCO, and lack of sharded cluster support made it unsuitable.

This customer uses MongoDB Enterprise with Cloud Manager for operational management of their MongoDB cluster. However, they found that on-premise backup solution from MongoDB is very resource-intensive and requires setting up multiple, dedicated servers (~6-8), large amount of storage (6-8x) and additional MongoDB licenses. Overall, the competitive solution price was ~4x higher than Datos IO RecoverX. In addition, they wanted a single backup and recovery solution that can support multiple databases as they look to adopt additional non-relational databases in the future.

quote

The Solution

RecoverX provided our customer with the ability to do: 1) Daily backups, and 2) Recover in the event of operational failures. Specifically, the capability to schedule and perform flexible versioning and recovery (collection-level) operations along with an intuitive user interface is why they chose Datos IO. Additionally, our customer wanted to keep backups local on-premise storage, so needed Datos IO RecoverX to support classical Network Attached secondary storage. Finally, Datos IO RecoverX software-only solution allowed them to deploy on existing hardware and scale across their application environments.

Environment Details

chart

Deployment Diagram

deployment-diagram

Learn How Datos IO Can Help Your Organization

File Origin: page.php -- Child (Default Template)