- Install On Prem MMS >
- On Prem MMS Components
On Prem MMS Components¶
See On Prem MMS Example Deployments for diagrams of potential deployment architectures and On Prem MMS Reference for system reference.
MMS Application Package¶
The front-end package contains the UI the end user interacts with, as well as HTTPS services used by the Monitoring Agent and Backup Agent to transmit data to and from MMS. All three components start automatically when the front-end MMS package starts. These components are stateless. Multiple instances of the front-end package can run as long as each instance has the same configuration. Users and agents can interact with any instance.
For MMS Monitoring, you only need to install the application package. The application package consists of the following components:
- MMS Application and Monitoring Server
- MMS Backup Ingestion Server
- MMS Backup Alerts Service
MMS HTTP Service¶
The HTTP server runs on port 8080 by default. This component
contains the web interface for managing MMS users, monitoring of
MongoDB servers, and managing those server’s backups. Users can sign
up, create new accounts and groups, as well as join an existing
group. The MMS Web Server also contains endpoints used by the MMS
Agent to report back information on monitored MongoDB instances.
Backup HTTP Service¶
The HTTP server runs on port 8081 by default. The Backup HTTP Service
contains a set of web services used by the Backup Agent. The agent
retrieves its configuration from this service. The agent also sends
back initial sync and oplog data through this interface. There is no
user interaction with this service. The Backup HTTP service runs on
port 8081 by default.
The Backup HTTP Service exposes an endpoint that reports on the state of the service and the underlying database to support monitoring of the Backup service. This status also checks the connections from the service to the MMS Application Database and the MMS Backup Blockstore Database. See Backup HTTP Service Endpoint.
Backup Alert Service¶
The Backup Alert Service watches the state of all agents, local copies of backed up databases, and snapshots. It sends email alerts as problems occur. The Backup Alert Service exposes a health-check endpoint. See Backup Alert Service Endpoint.
Backup Daemon Package¶
Backup Daemon¶
The Backup Daemon is the only component in the Backup Daemon Package. The Backup Daemon manages all local copies of backed up database (i.e. HEADs) as well as backup snapshots. The daemon does scheduled work based on data coming in to the Backup HTTP Service from the Backup Agents. No client applications talk directly to the daemon. Its state and job queues come from the MMS Application Database.
The daemon creates a local copy of the backed up database on in its
local storage in the rootDirectory path. If you run
multiple Backup Daemons, when you add a new backup the system selects
a daemon for that instance and the local copy of that instance resides
with that Daemon.
The daemon will take scheduled snapshots and store the snapshots in the Snapshot Storage (also known as the Blockstore). It will also act on restore requests by retrieving data from the Blockstore and delivering it to the requested destination.
The server running the Backup Daemon acts as a hidden secondary for every replica set assigned to it.
Multiple Backup Daemons can increase your storage by scaling horizontally and can provide manual failover.
The Backup Daemon exposes a health-check endpoint. See Backup Daemon Endpoint.
Data Storage¶
MMS uses dedicated MongoDB databases to store the MMS Application’s monitoring data and the Backup Service’s snapshots. The “backing databases,” run on separate dedicated replica sets, which are the backing MongoDB instances.
You can only use backing MongoDB instances for than storing MMS data. MMS requires that you use separate replica sets for each backing database and that these instances only host MMS data.
The backing databases are not part of the MMS package installation. Set them up separately and record their locations in the MMS configuration files.
MMS Application Database¶
This database contains application metadata that is used by the MMS monitoring application. The database stores:
- Monitoring data collected from Monitoring Agents.
- Meta data for MMS users, groups, hosts, monitoring data, and backup state.
For topology and specifications, see MMS Application Database.
MMS Backup Blockstore Database¶
This database contains all snapshots of databases backed up and oplogs retained for point in time restores. The blockstore database will require disk space proportional to the backed up databases.
Configure the Blockstore as a replica set to provide durability and automatic failover to the backup and restore components. See Preparing Backing MongoDB Instances for more information.
You cannot backup the blockstore database with MMS Backup.
Additional Information¶
To learn more about On Prem MMS Backup requirements and On Prem MMS Backup, see Backup FAQs and the Backup Agent.