mongolvmbackup | Snapshot & Backup MongoDB using LVM | Continuous Backup library
kandi X-RAY | mongolvmbackup Summary
kandi X-RAY | mongolvmbackup Summary
this tool is not maintained anymore. use at your own risk. other forks of this code might be more useful. a tool for backing up your mongodb datasets with almost no downtime. it accomplishes this mongodb’s fsync* commands and lvm snapshotting (so requires your db volume be created in lvm!). features: * roughly follows suggestions made in the [mongodb] [docs] * lock mongodb only briefly while the snapshot is being created. usually this takes only a couple of seconds; after that it’s business as usual. * a symlink to the latest backup is created to aid with restores and help other scripts find your data to send it offsite. * compress with gzip by default; other algorithms are supported * remove compressed backups older than n days * works with shards if you run a mongolvmbackup for each shard, but results [may not be consistent] warning: mongolvmbackup is to be used entirely at your own risk. that said it’s believed to be safe and we use it on production hosts.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mongolvmbackup
mongolvmbackup Key Features
mongolvmbackup Examples and Code Snippets
Community Discussions
Trending Discussions on Continuous Backup
QUESTION
ANSWER
Answered 2022-Feb-22 at 10:59I am not sure if you have seen this message in the portal when you created the account/also mentioned in the doc
"You will not be able to switch between the backup policies after the account has been created"
since you need to select either "Periodic" or "Continuous" at the creation of Cosmos Account, it becomes mandatory.
Update:
You will not see the above in portal anymore, you can Switch from "Periodic" to "Continous" on an existing account and that cannot be reverted. You can read more here.
QUESTION
What would be the consistency of the continuous backup of the write region if the database is using bounded staleness consistency? Will it be equivalent to strong consistent data assuming no failovers happened?
Thanks Guru
...ANSWER
Answered 2021-Nov-25 at 17:15Backups made from any secondary region will have data consistency defined by the guarantees provided by the consistency level chosen. In the case of strong consistency, all secondary region backups will have completely consistent data.
Bounded staleness will have data that may have stale or inconsistent data inside the defined staleness window (minimum 300 seconds or 100k writes). Outside of that staleness window the data will be consistent.
Data for the weaker consistency levels will have no guarantees for consistency from backups in secondary regions.
QUESTION
MongoDB has deprecated the continuous back up of data. It has recommended using CPS (Cloud provider snapshots). As far as I understood, snapshots isn't really going to be effective compared to continuous backup coz, if system breaks, then we can only be able to restore the data till the previous snapshot which isn't gonna make the database up-to-date or close to it atleast.
Am I missing something here in my understanding?
...ANSWER
Answered 2020-May-19 at 10:12Cloud provider snapshots can be combined with point in time restore to give the recovery point objective you require. With oplog based restores you can get granularity of one second.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install mongolvmbackup
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page