Brief note on backup and cloning (versions prior to 2.0)
Uptime Kuma
1
Posts
1
Posters
46
Views
2
Watching
-
I created a new backup of a running Uptime Kuma instance three times and attempted to clone it, as this was a “dry run” for version 2.0.
Each clone generated the following message due to a corrupted database
Trace: [Error: select * fromheartbeatwhere monitor_id = 75 ORDER BY time DESC limit 1 - SQLITE_CORRUPT: database disk image is malformed].The following instructions https://github.com/louislam/uptime-kuma/issues/5281#issuecomment -2452376039 created a 0-byte copy of the database, and nothing else from stackoverflow and Co. worked for me.
The only option was to start my running Uptime Kuma in recovery mode and back up this state. Restoring from this backup created a “valid”, undamaged database.
-
L luckow referenced this topic