I made again the same migration multiple times without facing the same issue. It does not seem to be related to the backup.
On my first migration I untar the snapshot then started mycontroller. I then remembered I have to disable https and change the default port so I stopped mycontroller a few seconds after.
I guess the database migration triggered on first launch was not finished and the database was altered. I see many database exceptions in the logs.
I have reproduced a database corruption with a fresh install. start then stop within 3 seconds. On my RPI3 the db migration left the database corrupted and mycontroller was unable to restart.
I don't know if you can prevent a shutdown during db initialization/migration. If you can't I take the full responsibility of this bad user behaviour !

Thanks, that fixed my issue.
After the update I could not login (wrong username/password) even with a cleared cache and browser restarted. I had to apply the password recovery solution from https://github.com/mycontroller-org/mycontroller/issues/233
I did not had that login problem when updating from 0.0.3Alpha2 to 0.0.3Final from feb 12.

Hi
I have an issue with this 0.0.3-Final (snapshot from feb 13). My nodes are battery powered and on the node details the battery graph can only display the last 6 hours.
Changing the view to last week or last month does not change the graph.
Changing the default interval in the metrics configuration also has no impact.
On Alpha2 the dropdown list also had no action but the default interval from the metrics configuration was taken into account.
Thanks