Timeline for Standalone Mongodb suddenly failed and I'm unable to recover. Backups are also corrupt
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2021 at 14:15 | answer | added | smurfing | timeline score: 1 | |
| Apr 28, 2021 at 9:46 | comment | added | smurfing | @JJussi Tank you for the link, we had it on our short list. We have managed to reconstruct the database using the methods outlined by dillonhua in your link, and alexbevi.com/blog/2016/02/10/…. We still lost a weeks worth of work. Its a hurdle to compile the wt-tool, but the biggest challenge was to match 23 collection names with the name of their disk file. | |
| Apr 22, 2021 at 10:55 | comment | added | JJussi | Yes, you are right. You need to have a running mongod instance to use mongodump. Have you test to salvage data with wiretiger tools? fatalerrors.org/a/wiredtiger-tool-restores-mongodb-data.html | |
| Apr 21, 2021 at 14:43 | comment | added | smurfing | @JJussi As far as I can tell, mongodump requires a running mongod instance. In this case mongod exits with an error on startup. Are you suggesting mongodump for backups over fs snapshots on a working instance? | |
| Apr 20, 2021 at 20:47 | review | First posts | |||
| Apr 20, 2021 at 22:46 | |||||
| Apr 20, 2021 at 20:14 | comment | added | JJussi | You can easily test with mongodump. Use mongodump to dump data and then you can use bsondump -command to view that .bson data as json. You can f.ex. "cat collection.json | bsondump | wc -l" and result is how many documents that collection have. To check that you have what you want. | |
| Apr 20, 2021 at 19:16 | history | asked | smurfing | CC BY-SA 4.0 |