@@ -44,12 +44,12 @@ For a list of |onprem|'s default ports and health-check endpoints, see
44
44
Backup Daemon Service
45
45
---------------------
46
46
47
- You can configure any |onprem| instance to run the :term:`Backup
48
- Daemon` service to back up MongoDB databases.
49
-
50
- To learn how to start, check the status of, stop, and restart the Backup
51
- daemon on a server, see :ref:`Start and Stop the Backup Daemon
52
- <start-stop-backup-daemon>`.
47
+ You can configure any |onprem| instance to perform backup :term:`snapshot`
48
+ maintenance work, such as a :term:`grooms <groom>` and managing
49
+ file system snapshot files on the :term:`file system store <File System
50
+ Store>` by running the :term:`Backup Daemon`. To learn how to start,
51
+ check the status of, stop, and restart the Backup Daemon on a server,
52
+ see :ref:`Start and Stop the Backup Daemon <start-stop-backup-daemon>`.
53
53
54
54
How the Backup Daemon performs depends upon the
55
55
:manual:`MongoDB version compatibility</reference/command/setFeatureCompatibilityVersion>`
@@ -65,11 +65,11 @@ The Backup Daemon service provides the following services for databases:
65
65
- Performs some state updates to the backup job
66
66
- Perform a queryable restore
67
67
68
- The daemon does scheduled work based on data coming into the |onprem|
69
- from the {+mdbagent+}s. Client applications can't communicate with the
70
- daemon. Its state and job queues come from the
71
- :ref:`mms-application-database`. |mms| creates snapshots from the
72
- database being backed up.
68
+ Client applications can't communicate with the daemon. Its state and job
69
+ queues come from the :ref:`mms-application-database`. |mms| creates
70
+ snapshots from the database being backed up. For incremental backups
71
+ using file system stores, the daemon is responsible for creating
72
+ snapshots.
73
73
74
74
:ref:`Multiple Backup Daemons <multiple-backup-daemons>` can scale
75
75
horizontally to run more concurrent jobs when needed and can provide
0 commit comments