Migrating a db owned by a different user

Install, Configure and Update
1

Hi All,

I am trying to install cryosparc with a db that we used previously which is owned by a different user. I am unable to rsync it to a new location (permission denied) and when the old user rsyncs it, the new installation of cryosparc seems to be unable to read it. Csparc starts fine but there are no users in the list and seems like the projects are also unavailable? Is there a way to work around this?

Many thanks,
Daniel

2

You could ask the other user to (on the old CryoSPARC instance’s computer):

  1. cryosparcm stop
cd /path/to/cryosparc_database
cd ..
tar zcfv db_copy.tar.gz cryosparc_database
  2. copy db_copy.tar.gz to the destination host (if necessary)
  3. make db_copy.tar.gz readable to the new CryoSPARC instance’s Linux account

Then, on the destination host, under the new CryoSPARC instance’s Linux account

  1. cryosparcm stop
  2. at a path of your choice, unpack db_copy.tar.gz
  3. edit
    /path/to/cryosparc_master/config.sh
    to point CRYOSPARC_DB_PATH to the (full path) of just unpacked cryosparc_database
  4. cryosparcm start

This procedure assumes that the old CryoSPARC instance will be retired, and its license id reused on the new instance. Please let us know otherwise.
EDITED: correct CRYOSPARC_DB_PATH variable name

3

I have a slightly different case. A user will be leaving the lab, and we would like to move this user’s CryoSPARC instance’s database, along with projects, workspaces, etc., to the lab’s instance. The lab’s instance has its license, and the user leaving has another license. Ideally, we do not want to make any changes to the lab’s instance.

Will detaching all projects and adding to the lab’s instance be the best route?

Thanks!

4

Probably the least troublesome generally, if not the quickest…

5

@himi This is a plausible approach.
During attachment of the project to the lab’s instance, please observe the command_core log for potential import errors, for example using the command

cryosparcm log command_core

If you observe any errors when attaching/importing a project, do not “use” the project. Creation of a new job, for example, inside a project whose attachment failed could lead to the corruption of the project directory. If you encounter any errors when attaching a project, please ask for help on the forum.