| 1 | == Migrate the repository == |
| 2 | |
| 3 | Here are the steps on how to migrate your data from MGOS 1.2 to MGOS 2.0 (note that these steps could take a long time if you have large repositories): |
| 4 | |
| 5 | 1. Shut down the existing MG Server (MGOS 1.2) if it is running. |
| 6 | |
| 7 | 2. Change to the !RepositoryAdmin directory (e.g. "C:\Program Files\!MapGuideOpenSource\Server\!RepositoryAdmin" or "/usr/local/mapguide/server/!RepositoryAdmin"). |
| 8 | |
| 9 | 3. Run !BackUpOnlineRepositories.bat (or !BackUpOnlineRepositories.sh for Linux). |
| 10 | |
| 11 | 4. Run !RestoreRepositories.bat (or !RestoreRepositories.sh for Linux). |
| 12 | |
| 13 | 5. Uninstall MGOS 1.2. Note that the existing repositories will not get removed. |
| 14 | |
| 15 | 6. Install the new MGOS 2.0 Server. Note that the Server will fail to start if it tries to open old repositories. |
| 16 | |
| 17 | 7. Change to the !RepositoryAdmin directory (e.g. "C:\Program Files\!MapGuideOpenSource\Server\!RepositoryAdmin" or "/usr/local/mapguide/server/!RepositoryAdmin", etc.). |
| 18 | |
| 19 | 10. Run !UpgradeRepositories.bat (or !UpgradeRepositories.sh for Linux). |
| 20 | |
| 21 | 11. Run !SetupRepositoryIndices.bat (or !SetupRepositoryIndices.sh for Linux). |
| 22 | |
| 23 | The above steps are required because of the [wiki:MapGuideRfc23 Oracle Berkeley DB XML upgrade]. |