Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
*Location*: http://mms.mongodb.com/help-hosted/master/core/functional-overview/
*User-Agent*: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0
*Referrer*: http://mms.mongodb.com/help-hosted/master/application/
*Screen Resolution*: 1920 x 1200
*repo*: REPONAME
*source*: core/functional-overview
*Location*: http://mms.mongodb.com/help-hosted/master/core/functional-overview/ *User-Agent*: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 *Referrer*: http://mms.mongodb.com/help-hosted/master/application/ *Screen Resolution*: 1920 x 1200 *repo*: REPONAME *source*: core/functional-overview
Description
"The MMS service recreates every replica set you backup and applies the oplog entries sent by the backup agents. MMS then maintains a standalone MongoDB database on disk, also called a head, for each backed up replica set. Each head is consistent with the original primary up to the last oplog supplied by the agent. The initial sync and tailing of the oplog are all done using standard MongoDB queries."
This not clear.
"The MMS service recreates every replica set you backup and applies the oplog entries sent by the backup agents."
Sounds like the MMS Service stands up mongod nodes to replicate the backed up environment. Basically, it duplicates my mongod environment.
"MMS then maintains a standalone MongoDB database on disk, also called a head, for each backed up replica set."
Is this something different from a duplicate set of mongod instances?
Does MMS really stand up a mongod node for each of my mongod nodes? Seems dubious.