[SERVER-23864] How to recover data from files created by moveParanoia Created: 22/Apr/16  Updated: 22/Apr/16  Resolved: 22/Apr/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Suguru Namura Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

SERVER-23425

We have taken very seriously this issue.
I read the ticket SERVER-23425 and found this.

> Users who haven’t disabled the moveParanoia option should be able to recover this data manually.

But I can't found documented procedures and instructions.
We use Mongodb v3.0.10 and do not disabled the movePranoia option.
How can we recovery data?

Best.



 Comments   
Comment by Ramon Fernandez Marina [ 22/Apr/16 ]

service@awa.fm, documents moved by the balancer will be copied to files inside a directory called moveChunk. Once you locate these moveChunk directories in the data bearing nodes of your cluster, you will find .bson files if the corresponding node was a donor in a chunk migration.

You can use bsondump to inspect the contents of these files and compare the documents with the data in your cluster. There are no automated tools to perform this comparison process, since the specific requirements on what to identify as a missing/incorrect document will heavily depend on your application and data distribution – but it's not hard to write a small tool to meet your specific needs.

If your cluster meets the requirements to be impacted by SERVER-23425, I'd recommend you upgrade to 3.0.11 or 3.2.5 right away if you haven't done so already. Even if you cluster hasn't been affected, it's best to be on the safe side.

Finally, please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Generated at Thu Feb 08 04:04:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.