Hi @user123, @pgoetz,
Please note cryoSPARC v3.2.0 uses MongoDB v3.4.10.
This is ideal if you’d like to keep a backup of the results that cryoSPARC has created (e.g., micrographs, particles, 3D volumes), but if you only want to keep a backup of the database (users, lanes, projects, workspace and job metadata, plots, event logs, etc.,), the
cryosparcm backup function is enough.
If the drive containing the cryoSPARC database folder is lost, but you have an
rsync'd backup of it, you can restore your instance by specifying the path to the backup database directory in
CRYOSPARC_DB_PATH, then restarting cryoSPARC.
cryosparcm backup function is a wrapper to
mongodump. You can read about it here. Relevant excerpts:
mongorestore operate against a running
mongod process, and can manipulate the underlying data files directly.
When connected to a MongoDB instance,
mongodump can adversely affect
mongod performance. If your data is larger than system memory, the queries will push the working set out of memory, causing page faults.
Also, a note about making backups of the database using
Since copying multiple files is not an atomic operation, you must stop all writes to the
mongod before copying the files. Otherwise, you will copy the files in an invalid state.
You can “stop all writes” by turning off cryoSPARC before you make a copy: