== Migrate the repository ==
The repository needs to be migrated because of the [wiki:MapGuideRfc23 Oracle Berkeley DB XML upgrade].

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):

1. Shut down the existing MG Server (MGOS 1.2) if it is running.

2. Change to the !RepositoryAdmin directory (e.g. "C:\Program Files\!MapGuideOpenSource\Server\!RepositoryAdmin" on Windows).

3. Run !BackUpOnlineRepositories.bat (or !BackUpOnlineRepositories.sh for Linux).

4. Run !RestoreRepositories.bat (or !RestoreRepositories.sh for Linux).

5. Windows: uninstall the 1.2 server (note that this does not delete the existing repositories). Or stop the server and try out the instructions for a side-by-side install: http://trac.osgeo.org/mapguide/wiki/InstallSideBySide1.2and2.0Apache.

6. Install the new MGOS 2.0 Server. Note that the server will fail to start if it tries to open old repositories.

7. Shut down the newly installed MG Server (MGOS 2.2) if it is running.

8. If the server is installed at a new location, delete the "empty" repositories (e.g "C:\Program Files\!MapGuideOpenSource2.0\Server\Repositories" on Windows), then copy the 1.2 repositories over to your new install (e.g. from "C:\Program Files\!MapGuideOpenSource\Server\Repositories" to "C:\Program Files\!MapGuideOpenSource2.0\Server\Repositories" on Windows).

9. Change to the !RepositoryAdmin directory (e.g. "C:\Program Files\!MapGuideOpenSource2.0\Server\!RepositoryAdmin" on Windows).

10. Run !UpgradeRepositories.bat (or !UpgradeRepositories.sh for Linux).

11. Run !SetupRepositoryIndices.bat (or !SetupRepositoryIndices.sh for Linux).

12. Start your 2.0 server.