technote:upgrade_replication
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| technote:upgrade_replication [2021/03/02 23:51] – Scott Cunliffe | technote:upgrade_replication [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Procedure Overview ===== | ===== Procedure Overview ===== | ||
| + | Stop master server | ||
| Stop replicant server | Stop replicant server | ||
| - | Stop master server | + | |
| + | Upgrade | ||
| + | |||
| + | Upgrade replicant server | ||
| Start master server | Start master server | ||
| + | |||
| Start replicant server | Start replicant server | ||
| If the upgrade of either the replicant or master involves moving to another server (change of IP) you will need to update the database config files to reflect the new DNS or IP. | If the upgrade of either the replicant or master involves moving to another server (change of IP) you will need to update the database config files to reflect the new DNS or IP. | ||
| - | It the upgrade of either the replicant or master involves a change of MAC address (new server hardware or VM) you will need to apply for a new license for each Framework Server with a new MAC address. | + | If the upgrade of either the replicant or master involves a change of MAC address (new server hardware or VM) you will need to apply for a new license for each Framework Server with a new MAC address. |
technote/upgrade_replication.1614729114.txt.gz · Last modified: 2025/01/21 22:07 (external edit)