MongoDB Management Service (MMS)

Rick HoulihanSolutions Architect

2

Agenda

Introduction

MMS Monitoring Overview

Setup Demo

MMS Backup Overview

Summary

3

MMS IntroductionWhat is it?

MongoDB Management Service (MMS) is an enterprise grade platform built to manage any size MongoDB deployment.

• Real Time Monitoring

• Alert/Notification API

• Point in Time Backup

• Automation (Coming Soon!)

4

MMS MonitoringHow it works

5

MMS MonitoringDashboards and Metrics

• Multi-level Operational Dashboards• Customizable Charts

• Metrics by Host or Group

• Flexible Log Collection• Per Host or Global

• Detailed Metric Breakdowns• Server Event Annotations

6

MMS Monitoring Running with Confidence

• Configurable Alerts• Critical Database KPI’s• Host Configuration and

Status• Host Level Metrics

• Flexible Notifications• Tiered Alert Scheduling• SMS, Email• Third Party Integrations

• PagerDuty, HipChat, SNMP

7

MMS – Get Started Fast

• Create an MMS Group• http://mms.mongodb.com (cloud)• http://yourhost:8080 (on prem)

• Install the Agent(s) • Monitoring is required• Backup is optional

• Start Managing MongoDB!

8

MMS BackupHow it works

9

MMS GroupMMS GroupMMS Group

MMS Group

MMS Agent

MMS Backup – Agent Overview

Replica Set

Replica Set

Replica Set

mongodmongodmongod

MMS Service• Flexible Deployment Options

• Statically compiled Go binary• One agent per MMS group• Stateless

• Workflow Monitor and Control Point• Sends initial sync and oplog data• Synchronizes shards and config

servers

• Shared or Dedicated Host• Can be network and CPU intensive

10

Works Like A Secondary

• Fully Automated Process• Oplog replayed on backup host• Concurrent backup of multiple clusters• Support for multiple mongod versions

• Standard Replication Mechanisms• Proven and reliable at scale• No replica set configuration required

Configuration

Initial Sync

Oplog Tail

Oplog Replay

Snapshot

• Minimal Production Impact• Incremental oplog traffic after initial

sync

11

System Architecture

Reconstructed Replica Sets

Backup Agent

Replica Set 1

Customer

BackupIngestion

MongoDB Inc.

BackupDaemon

Data DB

Block Store

Replica Set 1

1. Configuration2. Initial Sync

3. Stream Oplog

4. Store Data

7. Persist Snapshot

5. Retrieve Data

6. Apply Ops

12

MMS Backup - Daemon

• Asynchronous Backup Process• Data is processed from raw oplog cache• Oplog replay executed on source mongod version• Snapshot is de-duped at file and block level to

minimize footprint on disk

• Concurrent Replica Set Backup• Manages simultaneous backup of multiple replica

sets• Maintains version consistency with source

• User Configurable Snapshots• Adjustable snapshot scheduling and persistence

requirements

13

MMS – Single Server Deployment

14

MMS - Large Deployment with HA

15

MMS - Hosted Service Deployment

Meta Data DB

Oplog DB

Sync DB

BlockstoreDB(6x)

Daemon Host (15x across 2 DCs)

16 CPU cores, 386 GB RAM, 36 disks

Ingest 4x2 per DC

Restore 2x1 per DC

Partition 0 (17-20TB 7.2k RAID 10) – One of the DBs

Partition 1 (17-20TB 7.2k RAID 10) – One of the DBs

Partition 2 (2-3.5TB SSD or 15k RAID 0) – Daemon heads

Partition 3 (2-3.5TB SSD or 15k RAID 0) – Daemon heads

Daemon Process 1(Java)

Daemon Process 2(Java)

16

• Fully Integrated Management Service for MongoDB

– Leverages operational best practices for Monitoring and Backup

– Provides Point in Time Snapshot and Recovery

– Supported by MongoDB

• Flexible Deployment Options

– Available hosted or on prem

– Flexible Alerts and Notifications

– Tunable snapshots and persistence scheduling

• Distributed and Scalable

– Multi tiered architecture

– Horizontally scalable to meet business requirements

MMS - Summary

17

MMS - Learn More and Sign Up

http://mms.mongodb.com

18

MongoDB WorldNew York City, June 23-25

http://world.mongodb.comSave $200 with discount code MODERNAPPS

#MongoDBWorld

See how Bosch, UK Government Digital Service, Carfax, Stripe and others are engineering the next generation of data with MongoDB