Migrate DB from Main fork #338
-
|
I just found this fork, after installing and configuring the main fork. How do I copy the known devices, archived devices, etc from the previous install? I still have the sad card with the previous install. I installed this fork on a new sd card. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
|
Still no luck figuring out how to migrate db. I did a fresh install of this fork, and now I get "DataTables warning: table id=tableEvents - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1" |
Beta Was this translation helpful? Give feedback.
-
|
Hello, thank you for your interest in my fork. Unfortunately, over time it is no longer quite so easy to migrate from the main project to my version. In principle, you would even have to take an intermediate step. I'm just writing from the gut without having tested it myself. First of all, always work with a copy of your database so that you have a backup. In my project, I provide the pialert-cli script in the "pialert/back/" folder. The update_db parameter is used to add all the necessary fields to the database. However, as I have recently removed old updates, you would have to make an interim update with an older pialert-cli. So.
If I haven't forgotten anything, that should be it. However, I apologize if I have overlooked anything. Over time, the migration of the original project became less and less important to me, which is why I no longer offer an exact migration path. |
Beta Was this translation helpful? Give feedback.
-
|
OMG, you rock! That worked perfectly! Your directions couldn't be clearer and you saved me from identifying over 100 devices I had already marked as known! Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
OMG, you rock! That worked perfectly! Your directions couldn't be clearer
and you saved me from identifying over 100 devices I had already marked as
known! Thank you!
…On Tue, Jul 16, 2024 at 11:22 AM leiweibau ***@***.***> wrote:
Hello,
thank you for your interest in my fork. Unfortunately, over time it is no
longer quite so easy to migrate from the main project to my version. In
principle, you would even have to take an intermediate step. I'm just
writing from the gut without having tested it myself.
First of all, always work with a copy of your database so that you have a
backup.
In my project, I provide the pialert-cli script in the "pialert/back/"
folder. The update_db parameter is used to add all the necessary fields to
the database. However, as I have recently removed old updates, you would
have to make an interim update with an older pialert-cli.
So.
1. install the current version of my Pi.Alert
2. open the terminal, change to the directory pialert/back/
3. enter ./pialert-cli disable_scan 60 and confirm (Pi.Alert is paused
for 60min)
4. rename pialert-cli e.g. to pialert-cli.org
5. download an old version of pialert-cli (
https://raw.githubusercontent.com/leiweibau/Pi.Alert/fab2e1a7fd314ecdbc108fbcdc0301389743df95/back/pialert-cli
)
6. copy it into the directory where the original file was already
located and make it executable with chmod +x pialert-cli
7. copy a copy of your database into the directory db. You can
overwrite the existing DB.
8. execute "./pialert-cli update_db" in the directory "pialert/back/".
If there are no errors, delete the pialert-cli file and rename
pialert-cli.org again.
9. again, execute "./pialert-cli update_db" in the directory
"pialert/back/"
10. "./pialert-cli enable_scan"
If I haven't forgotten anything, that should be it. However, I apologize
if I have overlooked anything. Over time, the migration of the original
project became less and less important to me, which is why I no longer
offer an exact migration path.
—
Reply to this email directly, view it on GitHub
<#338 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKILRB3MD3ZF3UDCCTHEDZDZMU3DBAVCNFSM6AAAAABK2W57YWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBWGM4TSMA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hopefully this is a quick and easy question: I installed it on a RPi 3B+ and it's working so good that I am going to make it my main DNS and DHCP server (with Pi-Hole). How would I migrate this to a RPi 5 and save my database? I'm not worried about the Pi-Hole database, as that is a fresh install, so I can just install a new installation of that. |
Beta Was this translation helpful? Give feedback.
-
|
If you want to install pihole and Pi.Alert on the same system, I recommend that you install pihole as part of the Pi.Alert installation. You will be asked during setup whether you want to install pihole. The background to this is that the web server will then be configured correctly. If you install pihole beforehand, the web server configuration may break. In the event that you install a fresh system: The safest option would be to check in the settings that no scan is currently running and then make a copy of the database. If you have already activated an automatic database backup, you can also use one of these archives. This can then be transferred to the new installation. If may be necessary to repair the database permissions again with “./pialert-cli set_permissions”.
I don't know what you mean here? I thought you wanted to set up a new system for the Pi5. I would write a new image with the Raspberry Pi Imager. With the Pi3 you are probably using a 32bit system (even if it could use 64bit), with the Pi5 you could use a 64bit system. |
Beta Was this translation helpful? Give feedback.
-
|
That's how I installed Pi-Hole, through your Pi-Alert fork script. I installed it on a 3B+ with Raspbian 64 lite through Pi Imager. I just haven't done much except the defaults and DNS with it. Ri-clone is a script to make a copy of a Rpi as card to a SSD, so you can boot off of the SSD instead of an SD card. It works flawlessly. I just don't know if I cline the 3B+ card and put it in a 5, whether that will work. If not, I'll do a fresh Raspbian 64 lite on the 5, install Pi-Alert and choose to also install Pi-Hole during that install. It will be fresh and then I'll copy the DB over and follow your instructions on migrating the data. The only other option I was considering was using the Pi-Hole teleporter option but I didn't know if that will include your DB as well. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
The Pi-hole teleporter is only for Pi-hole itself |
Beta Was this translation helpful? Give feedback.
-
|
That worked perfectly. Sorry it took so long, I was waiting for the Amazon guy to deliver the new Pi 5.
|
Beta Was this translation helpful? Give feedback.
Hello,
thank you for your interest in my fork. Unfortunately, over time it is no longer quite so easy to migrate from the main project to my version. In principle, you would even have to take an intermediate step. I'm just writing from the gut without having tested it myself.
First of all, always work with a copy of your database so that you have a backup.
In my project, I provide the pialert-cli script in the "pialert/back/" folder. The update_db parameter is used to add all the necessary fields to the database. However, as I have recently removed old updates, you would have to make an interim update with an older pialert-cli.
So.