This page explains how to sync test server database with latest production data copy. Having the data in sync might be needed for reasons like:
...
- Take a full data dump from production.(including triggers, views, functions etc.)
- NOTE: If required as per center requirements, production database can be de-identified first before syncing with test server.
- Bring down test server Tomcat
- Take a backup of current test server database before sync
- Drop the test server database and create new database with same name so that configurations need not be changed
- Import the production data dump into this new database
- Bring up the Tomcat server
- Once the OpenSpecimen server is up, update settings like below to reflect it is test server
- Deployment Environment
- Application URL
- Data Directory: If the path is different compared to production
- Optional: To disable notifications or remove email settings
- Optional: Other user authentication settings like 'Inactive Account' can be set to 0 if you do not want users to be locked on test server
- Other settings which point to production DB path like System Workflow JSON.
Steps to sync the data directory from production:
...
| Info |
|---|
If the data directory sync is not done, you have to delete all jobs sub-directories under bulk-import/ directory. This is to ensure that bulk import works fine and the report downloaded does not refer to obsolete files. |