Database backup fails after "cryosparcm stop"

I’m about to upgrade from 2.15 to 3.0.0, and trying to run a database backup. If I stop cryoSPARC first, the backup does not work. If I leave cryoSPARC running, then the backup runs normally.

That is:

cryosparcm stop
cryosparcm backup --dir=/projects/CRYOEM/cryosparc_db_backups

Gives these messages:

Backing up to /projects/CRYOEM/cryosparc_db_backups/cryosparc_backup_2020_12_14_14h52.archive

CryoSPARC is not already running.

Starting the database in case it's not already running.
unix:///tmp/cryosparc-supervisor-02d268f8fe89c51a6b48cc5d2b4936b1.sock no such file

Executing mongodump.

2020-12-14T14:52:45.322-0500	Failed: error connecting to db server: no reachable servers

Matthew Cahn

Hi @mcahn,

This is the intended behaviour, the database needs to be running in order for the mongodump utility to be able to connect to it and perform a backup.
Note: Only the database needs to be running, so you can run cryosparcm stop to turn off all cryoSPARC services, then run the command cryosparcm start database to only start the database.

Hi @stephan,

That may be the intended behavior, but the backup process emits this message:

Starting the database in case it’s not already running.

Perhaps just the message is wrong.

Hi @mcahn,

You’re correct- thanks for pointing that out. The backup command should be able to work even if cryoSPARC has been stopped/already started. A fix will be released in the next version of cryoSPARC.

That’s great, thanks!

– Matthew