Hi @bp_sin,
If you follow my suggested approach above, the first step is making sure you have a viable file copy backup:
- Start a
mongodin a test environment using the dbPath backup from July 13th. Verify that this is a viable backup and the data that you are looking for is available.
If these files are a viable backup copy, mongod --dbpath /path/to/your/backup should start without any errors relating to data files and you will be able to query to confirm if the data you are looking for is present.
If the WT files you have are not a consistent backup, your options are unfortunately limited. You can try repairing or salvaging data as a last resort but that is often unsuccessful (see: Recover corrupted files (MongoDB 3.0.12) .wt - #4 by Stennie_X).
You should have separate paths for data files belonging to different backups or environments. Mixing files from different deployments may result in an unusable deployment.
I’d still recommend engaging a consultant (or your DBA team, if there is someone with more MongoDB admin experience on the team) as incorrect manipulation of data files or merging of data could lead to further challenges.
Regards,
Stennie