Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore Import Backup #5045

Closed
2 tasks done
water2022 opened this issue Aug 24, 2024 · 3 comments
Closed
2 tasks done

Restore Import Backup #5045

water2022 opened this issue Aug 24, 2024 · 3 comments
Labels
area:deployment related to how uptime kuma can be deployed area:settings Related to Settings page and application configration help

Comments

@water2022
Copy link

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Hi, I changed my server and now I need to import backup files from another server, what is the best way to accomplish this now?

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Debian12

🌐 Browser

google

🖥️ Deployment Environment

  • Runtime:
  • Database:
  • Filesystem used to store the database on:
  • number of monitors:
@water2022 water2022 added the help label Aug 24, 2024
@CommanderStorm
Copy link
Collaborator

The backup feature is depcrecated and should not be used. Please

  • shut down the instance,
  • transfer the data folder,
  • do a checksum check to ensure successfull transmission to the new machine and
  • then start it up at the new place.

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 based1 or infrastructure based2 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:

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

@CommanderStorm CommanderStorm added area:deployment related to how uptime kuma can be deployed area:settings Related to Settings page and application configration labels Aug 24, 2024
@water2022
Copy link
Author

无标题
Hi, which file exactly is being migrated?

@CommanderStorm
Copy link
Collaborator

Your screenshot shows the directory in which docker stores all (?) it's data.
You want the volume where you mounted the data folder instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:deployment related to how uptime kuma can be deployed area:settings Related to Settings page and application configration help
Projects
None yet
Development

No branches or pull requests

2 participants