Database migration from v4.5.3 to 4.5.7

Hi all,

I have running cryosparc on production, with version 4.5.3
cryosparc version : 4.5.3
cryosparc path : /apps/cryosparc
Database path : /cryosparcdatabase/v4.5.3
all this on AWS EBS

now i want to migrate the production database (copying) to other instance let’s say DEV

on DEV instance
cryosparc version : 4.7.1
cryosparc path : /efshome/apps/cryosparc
Database path : /efshome/apps/cryosparc/database/v4.7.1_251124
all this on AWS shared EFS

i want a plan for migration without effecting production database (we can have downtime)

Here the shared EFS is mounted on production and DEV

Can you share migration strategy based on this please

Thanks,
Gowtham

May I mention two constraints (additional constraints may apply in your environment/facility) that are applicable to your use case:

  1. Review this page for prerequisites of a valid database copy.
  2. Ensure the database is consistent with the states of CryoSPARC project directories. Malfunction and data corruption are the likely consequences of using an outdated copy of the database with CryoSPARC project directories whose contents have changed after the database copy has been initiated. Similarly, a database should not be operated with outdated copies of project directories.