- The document introduces MongoDB Management Service (MMS), a software built by MongoDB to make operations easier through monitoring and backup capabilities. - It provides a tour of MMS' interface and outlines the steps to get started, including signing up, adding hosts, and configuring monitoring and alerts. - Key features covered include monitoring metrics and health, setting different user roles, and taking automated, consistent backups of replica sets and sharded clusters with minimal overhead.

1. MongoDB Management
Service: Getting Started
Sam Weaver, Senior Solution Architect
#MongoDBWebinars
#MongoDBManagementServic
e

2. Welcome
3 part webinar series over the next 3 weeks
• Week 1: Introduction to MMS
• Week 2: Backup your data with MMS
– How the backup solution works
– Backing up a replica set
– Backing up a sharded cluster
– Restoring your data
• Week 3: Monitoring and alerting with MMS
– Charts
– Alerts
– Interpreting the data

3. Agenda for today
• High level tour of MMS
• Getting started with the agents
• Quick look into monitoring and backup – more on
these in the next session

4. What is MMS?
• Software built by MongoDB FOR MongoDB
• Makes your operations easier
• Can be run on-premise or in the cloud

5. MMS Then…

6. MMS Now….

7. Getting Started

8. Firstly.. Sign up..

10. Welcome screen..

11. Begin Setup..

12. Select an OS

14. Verify the agent..

15. Add and verify hosts

16. And if all goes well…

17. Great! Now what?

18. Notice..

19. Clicking on the host gives you
metrics

20. Why Monitoring?
Cant fix what you don’t know about
Capacity planning
Pre-empting problems
Proactive support
2-way mirror with commercial support

21. Bottom Line?
• MongoDB ops will live in this tool
• See what’s going on with your entire cluster
• In more detail with less effort than other 3rd party
tools

22. Your activity feed

23. Set alerts

24. Why Alerting?
Alerts on a huge range of metrics
– Host metrics
– Replica set
– Agent
– Backup
Send alerts via SMS, Email, PagerDuty and
HipChat

25. Bottom Line?
• Sleep easy knowing we will tell you what’s going on
as it happens
• Integrate with your existing alerting (pager duty, hip
chat)

26. Users

27. Add users

28. User Roles
• Different members of your team can do different
things
– Owner
– Automation admin
– Backup admin
– Monitoring admin
– UserAdmin
– Read only

29. Bottom Line?
• Multiple people can admin different parts of the
system.
• Work as one team, with set responsibilities for each

30. Backup

31. • Risks
– Storage failure
– Power outage
– Programmer error
– Hardware failure
– Data centre failure
– Cyber attack
– Weather related incidents
• Storage level options
• MongoDB Backup Service
Availability and Durability

32. • Relative to any particular risk
– How much data can you afford to lose? (RPO)
– How long can you afford to be offline? (RTO)
– What price are you willing to pay to remove the risk?
• Solutions
– Replication
– Application engineering?
– Backup
Addressing Risks

33. Replication
• Built into MongoDB, only ops and infrastructure
cost
• Very little to zero data loss in failure
• Down for a very short interval
• BUT… programmer errors will replicate almost
instantly

34. Traditional Backup
• Slower to restore
• Can suffer from being out of date
• Fairly cheap
• Isolated
• Covers most risks

35. • Mongodump/mongorestore
• Storage level options
• MongoDB Backup Service
Backup Approaches

36. Mongodump File system MMS Backup
Initial complexity Medium High Low
Confidence in
Backups
Medium Medium High
Point in time
recovery of replica
set
Sort of  No Yes
System Overhead High Can be low Low
Scalable No With work Yes
Consistent
Snapshot of
Sharded System
Difficult Difficult Yes
Recovery Approaches

38. Installing the agent..

39. Download and extract…

40. Verify agent and host

41. Select what you want to backup

42. Exclude certain name spaces

43. If its successful..

44. Snapshots…

45. Backing up a sharded cluster

46. Sharded Clusters
• Now only a few clicks:
– Balancer paused every 6 hours
– Ano-op token is inserted across all shards, mongoses
and config servers
– Oplog applied to replica sets until point in which token was
inserted
• Provides a consistent state of database across
shards

47. Bottom line: MMS Backup
• Simplest means of backing up your database
• Peace of mind, it just works
• Point-in-time for replica sets
• Check points for clusters
• Create QA and test environments quickly from
snapshots

48. Automation

49. Automation
Will be released soon
Deploy replica sets, & shards at the click of a button
Double the size of your estate easily
Upgrade versions quickly and safely
Manual process of rolling upgrades 12-15 steps

50. What next?
• Sign up to MMS at http://mms.mongodb.com
• Documentation can be found at
https://mms.mongodb.com/help/
• Listen in to the next webinar for a deeper
understanding of backing up your data

51. Next session..
• Next week! Wednesday 30th July 2014
• Backing up your MongoDB data with MMS

52. Questions?

53. Thanks!
Senior Solution Architect, MongoDB
Sam Weaver
#MongoDBWebinars
#MongoDBManagementServic
e