Database migrating exportimport scripts » History » Version 11
Anchi Cheng, 01/15/2021 06:00 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 | 11 | Anchi Cheng | As years goes by, the databases get 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 | 11 | Anchi Cheng | |
19 | The old databases can be kept as archive that you can still view with its own myamiweb but no longer write to. |
||
20 | 1 | Anchi Cheng | |
21 | These are in myami/dbschema/tools. These are not installed, so you do need a git clone myami to access it. |
||
22 | You need to know your sinedon.cfg of the system you migrate from and to. |
||
23 | |||
24 | 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. |
25 | |||
26 | Here are the ones you might want: |
||
27 | 10 | Anchi Cheng | 1. all projectdb except the two tables projectexperiments and processingdb (You can dump/restore the whole database and then empty the data in these two tables). |
28 | 5 | Anchi Cheng | 2. leginondb tables GroupData and UserData |
29 | |||
30 | If you want all old applications, you can also dump/import ApplicationData. Otherwise, individual application import/export is easiest using myamiweb administration tab. |
||
31 | |||
32 | 9 | Anchi Cheng | h2. Step 2: On the old system, run these: |
33 | 1 | Anchi Cheng | |
34 | 9 | Anchi Cheng | source_database_hostname is what is in your sinedon.cfg |
35 | 1 | Anchi Cheng | All output files except reference images are json files. The name format is used for parsing in the import. |
36 | |||
37 | h3. export_leginon_instruments.py |
||
38 | |||
39 | *Usage* export_leginon_instruments.py source_database_hostname <hostname1,hostname2> |
||
40 | (optional hostname1, hostname2 etc are specific instrument hostname to export. default will export all) |
||
41 | *Example* python export_leginon_instruments.py localhost Titan123456,GatanK3host |
||
42 | |||
43 | h3. export_leginon_cal.py |
||
44 | |||
45 | *Usage* export_leginon_cal.py source_database_hostname source_camera_hosthame camera_name <source_tem_name> |
||
46 | *Example* python export_leginon_cal.py localhost GatanK3host k3host EFKrios |
||
47 | |||
48 | h3. export_leginon_settings.py |
||
49 | |||
50 | 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. |
||
51 | |||
52 | *Usage* python export_leginon_settings.py <sessionname> <optional partial application name> <optional node name prefix> |
||
53 | *Example* python 20dec31a |
||
54 | |||
55 | h3. export_leginon_presets.py |
||
56 | |||
57 | This export presets used by a specific session, typically the same session as above to be used as default in your new system. |
||
58 | |||
59 | *Usage* python export_leginon_presets.py <sessionname> <optional partial application name> <optional node name prefix> |
||
60 | *Example* python 20dec31a |
||
61 | |||
62 | |||
63 | h3. export_leginon_ref.py |
||
64 | |||
65 | *Usage* python export_leginon_ref.py source_database_hostname source_camera_hosthame camera_name |
||
66 | *Example* python export_leginon_ref.py localhost k3host GatanK3 |
||
67 | |||
68 | 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. |
||
69 | |||
70 | 6 | Anchi Cheng | h2. Step 3: copy the resulting json and mrc files to the new leginon host (called new_host in the examples) |
71 | 1 | Anchi Cheng | |
72 | 6 | Anchi Cheng | h2. Step 4: On the clean installation that has already administrator user and other default in the installation, run these imports |
73 | 1 | Anchi Cheng | |
74 | h3. import_leginon_instruments.py |
||
75 | |||
76 | *Usage* import_leginon_instruments.py database_hostname |
||
77 | *Example* python import_leginon_instruments.py new_host |
||
78 | |||
79 | h3. import_leginon_cal.py |
||
80 | |||
81 | *Usage* import_leginon_cal.py database_hostname camera_cal_json_file |
||
82 | *Example* python import_leginon_cal.py new_host cal_titan123456+EFKrios+gatank3host+GatanK3.json |
||
83 | |||
84 | h3. import_leginon_settings.py |
||
85 | |||
86 | *Usage* python import_leginon_settings.py <applicationname or json filepath> |
||
87 | *Example* python import_leginon_settings.py 20dec31a.json |
||
88 | |||
89 | h3. import_leginon_presets.py |
||
90 | |||
91 | *Usage* python import_leginon_presets.py database_hostname tem_camera_presets_json_file |
||
92 | *Example* python import_leginon_presets.py new_host preset_titan123456+EFKrios+gatank3host+GatanK3.json |
||
93 | |||
94 | h3. import_leginon_ref.py |
||
95 | |||
96 | *Usage* import_leginon_ref.py database_hostname camera_ref_json_file |
||
97 | *Example* python import_leginon_ref.py new_host ref_titan123456+EFKrios+gatank3host+GatanK3.json |