That’s the issue I am suggesting be worked around or provide some hints/tips for. The backup was done as one user and the restore by another. I would think there would be ways to handle that more gracefully with some user detection.
All cryosparcm commands should be run by the designated, non-privileged Linux user.
Did other Linux users’ attempts to run the cryosparcm backup and cryosparcm restore not result, as expected, in an error?
What is the output of the command
cryosparcm status | grep USER?
Yes initially CryoSPARC was installed by root for testing purposes, which we know is not recommended. However there were jobs being run and we wanted to keep a history so we migrated the database to the new instance created by a non-root user. So I’m just suggesting to have some detection and warnings/alerts when backup/restore is done by a different user.