User Tools
niota-docs:niota_migrate_meta
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
niota-docs:niota_migrate_meta [2021/11/11 15:38] admin |
niota-docs:niota_migrate_meta [2025/07/17 14:11] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| <code> | <code> | ||
| At the same time on a machine there must not be a second server that is using the same port number. | At the same time on a machine there must not be a second server that is using the same port number. | ||
| - | So if you want to use the same port number for old N-MDDB and new N-MDDB you must temporarily switch the port of one of this services during data migration | + | So if you want to use the same port number for old NMDDB and new NMDDB you must temporarily switch the port of one of this services during data migration |
| </code> | </code> | ||
| + | |||
| + | To migrate metadata it's recommended to have two MySQL services running on the same machine. If there are no firewall restriction you can run services also on different machines. | ||
| + | |||
| + | service #1 - is the service where the new meta-database is installed - it has to run in federated mode. | ||
| + | |||
| + | service #2 - is the service where the old meta-database is installed - it may also run in federated mode. | ||
| + | |||
| + | |||
| + | use database niota_mdv20 as your working/migration database. | ||
| + | |||
| + | |||
| * stop MySQL service where your metadata are located if it's not running with "--federated" option | * stop MySQL service where your metadata are located if it's not running with "--federated" option | ||
niota-docs/niota_migrate_meta.1636641481.txt.gz · Last modified: 2025/07/17 14:11 (external edit)