Migrate current database
From TBwiki
(Difference between revisions)
William Wong (Talk | contribs) |
William Wong (Talk | contribs) |
||
| Line 15: | Line 15: | ||
* When upgrading to the next major software version, and this mext major software version had not been upgraded before (for example, 2.7.148 -> 2.8.132, and 2.8.132 had not been upgraded for this system before), it does not matter to check on this '''Migrate current database''' checkbox or not. It it recommended to check and enable it for simplicity. | * When upgrading to the next major software version, and this mext major software version had not been upgraded before (for example, 2.7.148 -> 2.8.132, and 2.8.132 had not been upgraded for this system before), it does not matter to check on this '''Migrate current database''' checkbox or not. It it recommended to check and enable it for simplicity. | ||
| − | * If from above example, 2.8.132 had been upgraded before for this system, and somehow user had downgraded again to current lower major software 2.7.148, then user will have the choice when doing a major upgrade whether to discard the change made in 2.7.148 (while in 2.7.148 after downgrade), and | + | * If from above example, 2.8.132 had been upgraded before for this system, and somehow user had downgraded again to current lower major software 2.7.148, then user will have the choice when doing a major upgrade again whether to discard the change made in 2.7.148 (while in 2.7.148 after downgrade), and say, to 2.8.132 (as example from above, can be other higher versions) with database from previous database that containing the previous configuration after upgraded to 2.8.132. Since discarding any change while in one software version is uncommon, it is recommended to check on this '''Migrate current database''' checkbox to migrate/clone the current database to next major softwar version keeping the change made in current software version. If '''Migrate current database''' is not checked, then a fresh database in 2.8.132 will be built. |
| + | |||
| + | * For downgrade, same concept as upgrade above that database will be cloned back to lower version database. But since, higher database structure may be different from lower version database structure, when checked and downgrade, some data may be lost. So, when doing downgrade, it is not recommended to check this '''Migrate current database'''. | ||
* Note that when doing a major upgrade, the current database of current software version will be backup and remain, in case when there is a need to fall back to this current version at original stage. | * Note that when doing a major upgrade, the current database of current software version will be backup and remain, in case when there is a need to fall back to this current version at original stage. | ||
Revision as of 04:23, 20 December 2018
Applies to versions: v2.7, v2.8, v2.9, v2.10
Note: This checkbox will be available starting from v2.7.148 in Activate package section when doing a major upgrade from web portal.
1- Click Migrate current database in the Activate package section.
2- Migrate current database clarification,
- When upgrading to the next major software version, and this mext major software version had not been upgraded before (for example, 2.7.148 -> 2.8.132, and 2.8.132 had not been upgraded for this system before), it does not matter to check on this Migrate current database checkbox or not. It it recommended to check and enable it for simplicity.
- If from above example, 2.8.132 had been upgraded before for this system, and somehow user had downgraded again to current lower major software 2.7.148, then user will have the choice when doing a major upgrade again whether to discard the change made in 2.7.148 (while in 2.7.148 after downgrade), and say, to 2.8.132 (as example from above, can be other higher versions) with database from previous database that containing the previous configuration after upgraded to 2.8.132. Since discarding any change while in one software version is uncommon, it is recommended to check on this Migrate current database checkbox to migrate/clone the current database to next major softwar version keeping the change made in current software version. If Migrate current database is not checked, then a fresh database in 2.8.132 will be built.
- For downgrade, same concept as upgrade above that database will be cloned back to lower version database. But since, higher database structure may be different from lower version database structure, when checked and downgrade, some data may be lost. So, when doing downgrade, it is not recommended to check this Migrate current database.
- Note that when doing a major upgrade, the current database of current software version will be backup and remain, in case when there is a need to fall back to this current version at original stage.
