Advice on taking backup?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 315
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
How do you guys and girls take backup of your level db data?
Do you (A) just copy out the files level create on disc or do you (b) implement a export feature which dumps all data in the database to file for later import?
If A: How does this work with having the db open by the running node program? Do you close down, backup and then open the database again or do you just copy out files wile running?
If B: Do you export all data every time or do you do diffs? If the database is large, how much would a full export slow down the other operations?
Or do you simply do more advanced stuff where you write to multiple databases on different machines (in different data centers) and look at that as backup?
Maybe we are missing some backup modules for level. At least there should be some advice on how to backup / avoid data loss in the documentation I think.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the LevelDB-related resources and existing documentation in this repository, then define backup guidance that addresses open databases, full exports, incremental differences, and replication; done means the recommended approach and its operational limits are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100