Database migrating exportimport scripts » History » Version 8
Anchi Cheng, 01/15/2021 05:52 PM
1 | 1 | Anchi Cheng | h1. Database migrating export/import scripts |
---|---|---|---|
2 | |||
3 | When you need to move all your data in the database to a new computer, you can |
||
4 | |||
5 | Either |
||
6 | |||
7 | 2 | Anchi Cheng | copy the all the database files over. See where in [[standard mysql database file locations]] (This only works well if your new computer is identical in setup. |
8 | 1 | Anchi Cheng | |
9 | Or |
||
10 | |||
11 | # do a full [[Mysqldump_of_your_database|mysqldump]] which includes instruction on how to recreate it through mysql command and then |
||
12 | 7 | Anchi Cheng | # [[Load_mysqldumped_databases|restore it]] on the new host |
13 | 1 | Anchi Cheng | |
14 | h2. Start fresh but keep the instruments/calibrations/settings even most recent gain/dark references and other tables that you really care. |
||
15 | |||
16 | 8 | Anchi Cheng | As years goes by, the database gets too big to backup or congested with old instrument and images you no longer own or care. A few scripts were written to |
17 | 1 | Anchi Cheng | make it possible to take a clean installation and migrate from the old system the stuff you need to care over. |
18 | |||
19 | These are in myami/dbschema/tools. These are not installed, so you do need a git clone myami to access it. |
||
20 | You need to know your sinedon.cfg of the system you migrate from and to. |
||
21 | |||
22 | 5 | Anchi Cheng | h2. Step 1: Use mysqldump to migrate single tables (see above and mysql documentation on the internet) and restore them on the new host. |
23 | |||
24 | Here are the ones you might want: |
||
25 | 1. all projectdb except the two tables projectexperiments and processingdb |
||
26 | 2. leginondb tables GroupData and UserData |
||
27 | |||
28 | If you want all old applications, you can also dump/import ApplicationData. Otherwise, individual application import/export is easiest using myamiweb administration tab. |
||
29 | |||
30 | 6 | Anchi Cheng | h2. Step 2: On the old system, run these. source_database_hostname is what is in your sinedon.cfg |
31 | 1 | Anchi Cheng | |
32 | All output files except reference images are json files. The name format is used for parsing in the import. |
||
33 | |||
34 | h3. export_leginon_instruments.py |
||
35 | |||
36 | *Usage* export_leginon_instruments.py source_database_hostname <hostname1,hostname2> |
||
37 | (optional hostname1, hostname2 etc are specific instrument hostname to export. default will export all) |
||
38 | *Example* python export_leginon_instruments.py localhost Titan123456,GatanK3host |
||
39 | |||
40 | h3. export_leginon_cal.py |
||
41 | |||
42 | *Usage* export_leginon_cal.py source_database_hostname source_camera_hosthame camera_name <source_tem_name> |
||
43 | *Example* python export_leginon_cal.py localhost GatanK3host k3host EFKrios |
||
44 | |||
45 | h3. export_leginon_settings.py |
||
46 | |||
47 | This export settings used by a specific session, typically a session you know containing good settings to be used as default in your new system. |
||
48 | |||
49 | *Usage* python export_leginon_settings.py <sessionname> <optional partial application name> <optional node name prefix> |
||
50 | *Example* python 20dec31a |
||
51 | |||
52 | h3. export_leginon_presets.py |
||
53 | |||
54 | This export presets used by a specific session, typically the same session as above to be used as default in your new system. |
||
55 | |||
56 | *Usage* python export_leginon_presets.py <sessionname> <optional partial application name> <optional node name prefix> |
||
57 | *Example* python 20dec31a |
||
58 | |||
59 | |||
60 | h3. export_leginon_ref.py |
||
61 | |||
62 | *Usage* python export_leginon_ref.py source_database_hostname source_camera_hosthame camera_name |
||
63 | *Example* python export_leginon_ref.py localhost k3host GatanK3 |
||
64 | |||
65 | This script and its import counter part are also used as a regular backup to quickly recover from file server issue that require us to use a different file disk and avoid accessing the problem disk. |
||
66 | |||
67 | 6 | Anchi Cheng | h2. Step 3: copy the resulting json and mrc files to the new leginon host (called new_host in the examples) |
68 | 1 | Anchi Cheng | |
69 | 6 | Anchi Cheng | h2. Step 4: On the clean installation that has already administrator user and other default in the installation, run these imports |
70 | 1 | Anchi Cheng | |
71 | h3. import_leginon_instruments.py |
||
72 | |||
73 | *Usage* import_leginon_instruments.py database_hostname |
||
74 | *Example* python import_leginon_instruments.py new_host |
||
75 | |||
76 | h3. import_leginon_cal.py |
||
77 | |||
78 | *Usage* import_leginon_cal.py database_hostname camera_cal_json_file |
||
79 | *Example* python import_leginon_cal.py new_host cal_titan123456+EFKrios+gatank3host+GatanK3.json |
||
80 | |||
81 | h3. import_leginon_settings.py |
||
82 | |||
83 | *Usage* python import_leginon_settings.py <applicationname or json filepath> |
||
84 | *Example* python import_leginon_settings.py 20dec31a.json |
||
85 | |||
86 | h3. import_leginon_presets.py |
||
87 | |||
88 | *Usage* python import_leginon_presets.py database_hostname tem_camera_presets_json_file |
||
89 | *Example* python import_leginon_presets.py new_host preset_titan123456+EFKrios+gatank3host+GatanK3.json |
||
90 | |||
91 | h3. import_leginon_ref.py |
||
92 | |||
93 | *Usage* import_leginon_ref.py database_hostname camera_ref_json_file |
||
94 | *Example* python import_leginon_ref.py new_host ref_titan123456+EFKrios+gatank3host+GatanK3.json |