@EdLowe I apologize for the delayed response. In case you have not yet moved ahead with recovery:
- You may want to identify and eliminate the cause of the corruption. In CryoSPARC v4.4, with database journaling enabled by default, corruption should be rare and might indicate a problem with the underlying storage. Ensure suitable filesystem settings (nfs example).
- Before proceeding with any of the procedures below, you should create a backup copy of the database directory, in case you may want to reuse its contents for any reason. Before copying, ensure CryoSPARC and its associated processes (including the
mongodprocess) are shutdown completely. - Restoration of an old database backup will likely lead to corruption of CryoSPARC project directories that have been changed after the backup has been created. Consider alternatives such as
- Alternative: rebuild the database from scratch
- Alternative with significant caveats: so-called
--repair(docs)