MMS features (1)

The MongoDB Management Service (MMS) is an infrastructure service used to monitor and back up MongoDB. The monitoring service is free of charge, and the backup service is charged. MMS monitoring MMS provides real-time reports, visualization, alarms, and hardware metrics, and displays data in an intuitive Web dashboard. You only need to install a lightweight Monitoring Agent to collect mongodb

The MongoDB Management Service (MMS) is an infrastructure service used to monitor and back up MongoDB. The monitoring service is free of charge, and the backup service is charged. MMS monitoring MMS provides real-time reports, visualization, alarms, and hardware metrics, and displays data in an intuitive Web dashboard. You only need to install a lightweight Monitoring Agent to collect mongodb

The MongoDB Management Service (MMS) is an infrastructure service used to monitor and back up MongoDB. The monitoring service is free of charge, and the backup service is charged. MMS monitoring MMS provides real-time reports, visualization, alarms, and hardware metrics, and displays data in an intuitive Web dashboard. You only need to install a lightweight Monitoring Agent to collect mongodb running information and send it back to MMS. The MMS user interface allows you to view visualized data and set alarms. The MMS backup function is designed for mongodb and can be scheduled to restore snapshots and time points. Once the service starts and runs, MMS provides a Web interface to support backup and recovery, and MMS backup also supports horizontal scaling. A lightweight backup proxy needs to be installed. The proxy performs initialization synchronization and captures the OPLOG of the primary node of the replica set. For sharded clusters, the backup proxy intercepts each primary and each config server. Then, the initial synchronization and oplog data are transmitted back to MMS over https. The MMS Service recreates each replica set and applies the oplog log. Then, the MMS maintains an independent mongodb database on the hard disk, also known as the head, which backs up each replica set. Each head is consistent with the original primary through the final oplog provided by the proxy. Both the initialized data and oplog use standard MongoDB queries. The MMS backup service uses backup to recreate each replica set and apply the oplog logs sent by the proxy. For replica sets and shards in the production environment, you do not know how to copy the backup data, because the data is completed using standard mongodb queries. The service needs to reserve all head snapshots and retain snapshots based on user-defined policies. MMS backup captures the snapshot of the replica set based on the bserved interval of OPLOG time change. The sharded cluster snapshot temporarily stops the balancer through mongos, so that you can insert a tag on all the shards and configuration servers. A snapshot is required when the MMS tag appears on the backup data. Compression and block-level deduplication reduce the data size of snapshots. Snapshots only store the differential data between snapshots. Snapshots use a small part of the disk space of the complete snapshot. Recovery recovery applies to the restoration of specific snapshots and time points in the replica set. The cluster can only be restored from the consistency of the snapshot time. Snapshot recovery is directly read from the backup Blockstore database, and files are transmitted through the HTTPS download link (pull) or the MMS service through SSH push. Time Point recovery first creates a local blockstore snapshot for restoration. Then, the oplog log is applied until the specified time point. The service then provides time point backup through the same HTTPS or SSH mechanism. Oplog logs are configurable for each backup, and the available time window affects recovery at the time point.

Original article address: MMS function introduction (1). Thank you for sharing it with me.