[SERVER-40255] Server Crashed and lost database Created: 21/Mar/19  Updated: 09/Apr/19  Resolved: 09/Apr/19

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

Type: Question Priority: Critical - P2
Reporter: Raja Sekhar Sana Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: wtc, wtcru
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File SERVER-40255_repair.tgz     PNG File Screen1.PNG     File WiredTiger.turtle     File WiredTiger.wt    
Issue Links:
Related
related to SERVER-40256 Accdently Server Crashed and We lost ... Closed
Participants:

 Description   

Hi Team,

 

My server unexpectedly crashed due to this my mongodb database with version 3.4 lost, when i am trying to run not running using dbpath, please solve my issue, really it was about 18 months data, please help me.

 

I am attaching .wt and turtle file. if you require will send complete data folder.



 Comments   
Comment by Raja Sekhar Sana [ 01/Apr/19 ]

Hi Eric,

Really it is a very bad to me to lost valuable data, is there any options to recover. Please guide us to get out lost data.

 

thanks & regards

Raja Sekhar

Comment by Eric Sedor [ 25/Mar/19 ]

Unfortunately we aren't able to repair this corruption. To avoid a problem like in the future, please see our recommendations above, especially with respect to running in a replica set and implementing a backup and backup recovery strategy.

We can collect information to guide our development efforts in the future. If you are able, can you please provide:

  1. The complete logs for the affected node, including before, leading up to, and after the first sign of corruption.
  2. A complete description of the underlying storage mechanism in use. Please address questions such as whether storage is locally attached or network-attached, whether disks are SSDs or HDDs, whether disks are Are the disks SSDs or HDDs, whether RAID is in use and if so how it is configured, and what file system and/or volume management system is in use.
  3. A description of your backup method, if any.
  4. A history of the deployment, including:
    1. a timeline of version changes
    2. a timeline of hardware upgrade/downgrade cycles or configuration changes
    3. a timeline of disaster recovery or backup restoration activities
    4. a timeline of any manipulations of the underlying database files, including copies or moves, and information about whether mongod was running during each manipulation.
  5. Finally, can you provide assurances that you have not manipulated (copied or moved) the underlying database files while mongod was running, and that your disks have been recently checked for integrity?
Comment by Raja Sekhar Sana [ 25/Mar/19 ]

Hi Eric,

 

Is there any progress / update.

 

regards

Raja Sekhar

Comment by Raja Sekhar Sana [ 24/Mar/19 ]

HI Eric,

No, it is not a repair attepted dbpath.

 

regards

Raja Sekhar

Comment by Eric Sedor [ 22/Mar/19 ]

Have you attemped a --repair operation on the dbpath provided at that google drive link? If so, are you able to provide the original dbpath from before that?

Comment by Raja Sekhar Sana [ 22/Mar/19 ]

Hi Team,

 

I have database named politik and 21 collections are there in database, very important to recover for us, i am sending drive link complete data folder.

https://drive.google.com/open?id=17O6J5dZdfJJOvnUL_6Ho09RlFadW0nBf

thanks & regards

S Raja Sekhar

Comment by Raja Sekhar Sana [ 22/Mar/19 ]

Hi,

 

By downloading files send by you, and replaced in dbpath, still issue remains. Please check screenshot. [^data.7z]

Comment by Eric Sedor [ 21/Mar/19 ]

I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath.

It is our strong recommendation to:

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