Andrey/uptime-kuma
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated Migration From v1 To v2 (markdown)

Frank Elsinga 2025-10-31 17:22:34 +01:00
parent ed44aae335
commit 46b601cbb7
1 changed files with 15 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Migration-From-v1-To-v2.md

@ -1,16 +1,22 @@
> [!WARNING]
> It is a major version update. It contains some breaking changes. Please read the migration guide carefully if you want to upgrade from v1 to v2.
## Before You Start
- Stop your Uptime Kuma and:
- Backup your `data` directory.
- Make sure you have a backup of your `data` directory again.
- Make sure you have a backup of your `data` directory again and again.
- The migration process could take some time to complete, depending on the size of your database.
- You should be able to view logs of the migration process in the console.
- Do not interrupt the migration process.
- FYI: My Uptime Kuma had 20 monitors and 90 days of data, and it took around 7 minutes to migrate.
> [!NOTE]
> # Before You Start
>
> Stop your Uptime Kuma and:
> - Backup your `data` directory.
> - Make sure you have a backup of your `data` directory again.
> - Make sure you have a backup of your `data` directory again and again.
>
> The migration process could take some time to complete, depending on the size of your database.
> This is because we need to aggregate the heartbeat table into the new, more optimised format.
>
> - You should be able to view logs of the migration process in the console.
> - Do NOT interrupt the migration process. *If the migration process is interrupted, you must restore from backup and retry the upgrade.*
> - FYI: My Uptime Kuma had 20 monitors and 90 days of data, and it took around 7 minutes to migrate.
> *On slower hardware or with more monitors, this can take hours.*
## Breaking Changes