If you're working with the scale of data that requires a solution like MongoDB, you probably have a lot invested in your data. It goes without saying, then, that backups should be an integral part of any NoSQL offering, and it's important to know how best to approach them. To that end, the MongoDB Management Service (MMS) blog has published a comparison of three MongoDB backup strategies:
- mongodump
- Copying the underlying files
- MongoDB Management Service
As one might expect, given the source, the comparison leans in favor of the third option, but the overview of the three strategies remains a concise resource for understanding what options are availalbe. mongodump, for example, is a tool bundled with MongoDB that allows the creation of straightforward, filterable backups, while file copying (with Linux VM, for example) creates a somewhat inflexible filesystem snapshot. MMS, on the other hand, provides continuous backups as a service.
For a look at the three primary options for MongoDB backups, check out the full post.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}