Export / Import Backup

[ArturAronov]

📑 I have found these related issues/pull requests

Export and Import of backup flattens the collections.
When importing or exporting the backup, the collections become flat again. Path name is recorded in backup file, however when file is imported, the data is not grouped into right collections.

Add status page set up to backup file.

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

No response

👟 Reproduction steps

https://url/dashboard -> Settings -> Back up -> Export / Import

👀 Expected behavior

The uptime pages should be organised by collections on import.
Status page entries are not exported

😓 Actual Behavior

The imported pages should be organised by collections
Status page entries should be exported

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Linux/X86_64 (Ubuntu)

🌐 Browser

Arc / Chromium

🖥️ Deployment Environment

• Runtime: AWS ECS Linux/X86_64 (Ubuntu)
• Database: SQLite
• Filesystem used to store the database on: EFS
• number of monitors: 1

📝 Relevant log output

No response

[louislam]

https://url/dashboard -> Settings -> Back up

Please read the warning message in the same page.

[CommanderStorm]

Chiming in with a more in-depth explanation:

Please see #2141 (comment)

In 1.18.3, the backup feature was deprecated due to [being left] unmaintained.

Backup & Restore with JSON has been deprecated and issues will not be fixed due to the amount of problems it has been causing for our users and us.
The current design is just not maintainable, causing countless bugs.
In v2.0 the deprecated backup tool is being removed because of this reason.
Please consider using SQL, API based¹ or infrastructure based² backup instead.

New approaches to these features should use SQLite dump or MariaDB dump respectively. (Here is our contribution guide)

You can subscribe to these issues meanwhile:

• Use two different database files for config and history #2496
• Automatic / periodical backups #477

Footnotes

1. using the third-party API: https://uptime-kuma-api.readthedocs.io/en/latest/ ↩

2. see https://github.com/louislam/uptime-kuma/issues/477#issuecomment-1557966187 for a setup example ↩

[clement-igonet]

F.Y.I., we prefered backup and restore notifications and monitors with python and uptime-kuma-api
( https://uptime-kuma-api.readthedocs.io/ ).
Unfortunately, it is not possible to get then add dicts as is, we needed to pop/remove some fields, and manage relationship between monitors and notifications. But it was valuable.