Restoring lost CryoSPARC data

[wtempel]

The database currently connected to your CryoSPARC instance may be corrupt or incomplete.
You may want to confirm that storage devices or filesystems have not been damaged by the power outage.
The following steps for rebuilding the database assume that that CryoSPARC has been stopped completely. If the cryosparc_master/ installation has been damaged as a result of the power outage, you may consider a fresh CryoSPARC installation.
The database path should point to robust storage of sufficient size. Based on the number and kinds of jobs stored, a CryoSPARC database (separate from CryoSPARC project directories) may require hundreds of gigabytes or even several terabytes of storage. Ideally, the storage is frequently snapshotted and the snapshots are replicated on a backup server.

@wtempel

1. updating the CRYOSPARC_DB_PATH= definition inside /XXX/cryosparc_master/config.sh with a new, suitable path.
2. then running
   cryosparcm start
   which should start CryoSPARC with a blank database.
3. re-creating CryoSPARC users in the database with
   cryosparcm createuser
   commands (guide)
4. registering CryoSPARC workers in the database with
   cryosparcw connect commands (on the worker(s), guide) or
   cryosparcm cluster connect command(s) (guide), as applicable.
5. attaching project directories. You may have to delete the cs.lock file from any given project directory before attachment because the instance id stored in the new, blank database differs from the old instance id stored in the old database. This is an exception from the rule that cs.lock files should generally not be deleted.