mongo-oplog-backup | Experimental incremental backup system for MongoDB | Continuous Backup library

by journeyapps Ruby Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | mongo-oplog-backup Summary

mongo-oplog-backup is a Ruby library typically used in Backup Recovery, Continuous Backup applications. mongo-oplog-backup has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This project aims to enable incremental backups with point-in-time restore functionality, utilizing MongoDB's oplog and standard tools wherever possible. A backup script can be run from a cron job, and each incremental run produces a single file that can be stored on your preferred medium, for example Amazon S3 or an FTP site. This project only provides the tools to produce the backup files, and it's up to you to transfer it to a backup medium. Internally the mongodump command is used for the backup operations. Initially a full dump is performed, after which incremetal backups are performed by backing up new sections of the oplog. Only the standard BSON format from mongodump is used. To restore a backup, the incremental oplogs are merged into a single file and combined with the initial full dump, which can then be restored with a standard mongorestore --oplogReplay command. A point-in-time restore with the --oplogLimit option of mongorestore. Additional support for this may be added to the oplog merging command in the future to simplify the process. Incremental oplogs always overlap by exactly one entry, so that integrity can easily be verified (e.g. that there are no gaps between incremental oplogs).

Support

Quality

Security

License

Reuse

Support

mongo-oplog-backup has a low active ecosystem.

It has 62 star(s) with 17 fork(s). There are 25 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 9 have been closed. On average issues are closed in 643 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of mongo-oplog-backup is current.

Quality

mongo-oplog-backup has 0 bugs and 0 code smells.

Security

mongo-oplog-backup has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mongo-oplog-backup code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

mongo-oplog-backup is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

mongo-oplog-backup releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed mongo-oplog-backup and discovered the below as its top functions. This is intended to give you an instant insight into mongo-oplog-backup implemented functionality, and help decide if they suit your requirements.

Backs up the state of the given state .
Restore log files .
Performs a backup operation .
Run the command .
Initialize a backup .
Load YAML file
Start the backup .
Checks if the backup timestamp exists
Generate a command string .
Returns the latest version of the latest version .

Get all kandi verified functions for this library.

mongo-oplog-backup Key Features

No Key Features are available at this moment for mongo-oplog-backup.

mongo-oplog-backup Examples and Code Snippets

No Code Snippets are available at this moment for mongo-oplog-backup.

Community Discussions

Trending Discussions on Continuous Backup

How to disable azure cosmos db continious backup

Consistency of Continuous backup of Azure Cosmos DB

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

QUESTION

How to disable azure cosmos db continious backup

Asked 2022-Feb-22 at 10:59

I enabled the Azure cosmos DB continuous backup for one of my Cosmos DBs.
How can I disable it? It just says you have successfully enrolled in continuous backup.

...

ANSWER

Answered 2022-Feb-22 at 10:59

I 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.

Source https://stackoverflow.com/questions/69347197

QUESTION

Consistency of Continuous backup of Azure Cosmos DB

Asked 2021-Nov-25 at 17:15

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:15

Backups 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.

Source https://stackoverflow.com/questions/70099953

QUESTION

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

Asked 2020-May-19 at 10:12

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:12

Cloud 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.

Source https://stackoverflow.com/questions/61886736

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mongo-oplog-backup

Install released gem (recommended):.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: