Migrating ManicTime Server

This document will help you to move ManicTime Server to a different machine.

Before migration

If you are using MS SQL or PostgreSQL and you will also migrate the database server, then install the database server.

1. Stop the server:

Windows
Go to where ManicTime Server is installed (on Windows by default in Program files (x86)/ManicTime Server), open command prompt and type:

ManicTimeServer stop

Linux
stop ManicTimeServer process

2. Migrating the database (skip if you are using SQLite)

MS SQL or PostgreSQL
If database is on another machine and you would still like to use the same database, you can skip this step. The new server will continue using the same databases.

If you will setup a new database server as well:

  1. make a backup of both ManicTimeCore and ManicTimeReports database.
  2. restore them on the new machine
  3. create a user on the database server which has owner access for both databases. This user will be used in connection string.

3. Migrating ManicTime server

  1. Install ManicTime Server on the new machine.

  2. Copy ManicTime Server data folder from the old machine to the new one.
    Windows

     c:\ProgramData\ManicTime\Server\Data\

    Linux

     [ManicTimeServer folder]/[Data]/

    Copy it to the same location on the new machine.

  3. Check settings
    In Data folder, there is a file ManicTimeServerSettings.json. If you are using MS SQL or PostgreSQL, open it and check if connection strings are OK.
    Do they point to the correct database?

    Does the user, which is used in connection string, have sufficient rights on the server (access to ManicTimeCore and ManicTimeReports database)?

4. Start the server

Windows
Go to where ManicTime Server is installed (on Windows by default in Program files (x86)/ManicTime Server), open command prompt and type:

ManicTimeServer start

Linux
run ManicTimeServer in folder where you installed ManicTime

5. Troubleshooting

In the /Data folder, there is a sub-folder Logs. If you have any problems, you can check the log files for more information.