[SERVER-37011] Data lost Created: 05/Sep/18  Updated: 07/Apr/23  Resolved: 11/Sep/18

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

Type: Question Priority: Major - P3
Reporter: Tommy Walfred Assignee: Nick Brewer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt    
Issue Links:
Related
is related to SERVER-36693 I have broken MongoDB. Need to repair... Closed
Participants:

 Description   

Our MongoDB had been broken due to unexpected shutdown of server.

And I requested community to help repair it.

I had provided WiredTiger files, and received updated one from community.

And replaced old wiredtiger files with those one, and db was repaired.

But the disaster is that I've lost last month's data after repair.

I still have back up of broken db (before repair) including old wiredTiger files and new repaired wiredTiger files (the community provided for fix).

Is there any way to recover my lost data?



 Comments   
Comment by Tommy Walfred [ 11/Sep/18 ]

Huh, it's really bad. If we have the old data before it was corrupted, then why do we request repair?

 

Comment by Nick Brewer [ 11/Sep/18 ]

tommy.super@yandex.com The files you've uploaded are the same ones upon which an initial repair attempt (available here) was performed in SERVER-36693. If you were not able to recover all of your data using this repair, I'm afraid there's nothing else we can do; you would need to have another backup available, or another means of accessing the old data before it was corrupted. 

-Nick

Comment by Tommy Walfred [ 10/Sep/18 ]

Hi Nick,

How are you?

Comment by Tommy Walfred [ 06/Sep/18 ]

Hi Nick,

What else do you need from me for its success repair without any data loss?

Comment by Tommy Walfred [ 06/Sep/18 ]

Hi Nick,

I have a backup of DB before repair.

 

Comment by Nick Brewer [ 06/Sep/18 ]

tommy.super@yandex.com If the previous repair allowed MongoDB to boot, but a portion of the data was not recoverable, it is unlikely that the outcome would be different this time - in order to recover the full data you would need to have a backup of it available.

-Nick

Comment by Tommy Walfred [ 06/Sep/18 ]

Hi Nick,
Thanks for your kind reply.

Here is the issue link.

https://jira.mongodb.org/browse/SERVER-36693

 

And I have uploaded the origin wiredTiger.turtle and wiredTiger.wt files.

WiredTiger.turtleWiredTiger.wt

  • MongoDB version - 3.4.4
  • Operating system and version - Windows 8.1
  • Platform is native hardware.

Please let me know if you have anything needed besides these info.

Kindly,

Tom

Comment by Nick Brewer [ 05/Sep/18 ]

tommy.super@yandex.com It would be useful if you could link to the relevant community posting where the files were repaired. You can also upload the WiredTiger.turtle and WiredTiger.wt files (from the backup, before the previous repair) here and we can make a repair attempt.

Additionally, we'd need to confirm:

  • The mongoDB version
  • The operating system and version
  • The platform (virtual machine, container, native hardware, etc)

Thanks,
-Nick

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