Difference between revisions of "2016 CyberShake database migration"
From SCECpedia
Jump to navigationJump to search (Created page with "=== Goals of DB Migration === *Swap hardware between moment and focal *On read-only server, have multiple DBs with Study 15.4 and Study 15.12 data *On production server, keep...") |
|||
| Line 4: | Line 4: | ||
*On read-only server, have multiple DBs with Study 15.4 and Study 15.12 data | *On read-only server, have multiple DBs with Study 15.4 and Study 15.12 data | ||
*On production server, keep Study 15.12 and 15.4 | *On production server, keep Study 15.12 and 15.4 | ||
| − | + | *Migrate older studies to alternative format, delete from production server. | |
=== Procedure for CyberShake DB Migration === | === Procedure for CyberShake DB Migration === | ||
Revision as of 23:07, 13 May 2016
Goals of DB Migration
- Swap hardware between moment and focal
- On read-only server, have multiple DBs with Study 15.4 and Study 15.12 data
- On production server, keep Study 15.12 and 15.4
- Migrate older studies to alternative format, delete from production server.
Procedure for CyberShake DB Migration
- Run mysqldump on entire DB on focal. Generate dumpfiles for all the metadata, and then each study separately, along with the runs which are not part of a study.
- Delete database on moment.
- Reconfigure DB on moment (single file per table, etc.)
- Load all files into DB on moment; confirm they are present.
- Delete database on focal
- Load metadata, Study 15.12, Study 15.4 onto focal for read-only access.
- Swap names of focal and moment so we don't have to change all our scripts.
Once this is done, we can finalize the alternative format we want. We may want to test SQLite to see if it can handle a large study.
