Data Recovery Strategy: Merging Position Data Between Two Traccar Instances
What DB are you use, for how many device you are talking about ?
If you are use MySQL DB, you can make it manually, device by device, one by one.
Go to phpmyadmin or use HeidiSQL, make query to select all data from tc_position for some deviceId, export the data as .sql, after that open the file, rename the old deviceId with the new one which is in the new server, save the file and import it in the new server in tc_positions table.
Repeat the procedure with all devices which you want to move in the new server.
I don't see how it would work, imagine first having to do it for about 200 or more devices, and if you copy the positions from the new server, the position ids will be different, so they won't be able to be seen in the replay logs, which is the idea, integrate the history not received into the main server
Of course it will work, when you will make some report or replay Traccar makes query from tc_positions, selecting all positions where deviceId is selected (in the range of the time which you selected). No matter the id of position, just this positionId must to be connected with the right deviceId.
Try with one car and you will see the result.
You have to update the device id to match before you import the data.
Greetings, Anton, I have a question, wasn't this tool for cases like this? to resend the old logs? https://github.com/traccar/traccar/blob/master/tools/recover.py
That tool hasn't been updated for a while. And it's much slower than copying database records directly.
Data Recovery Strategy: Merging Position Data Between Two Traccar Instances
Hello,
I'm facing an hipotetical data continuity challenge and would appreciate guidance on the best approach to resolve it.
Scenario:
Current situation:
Questions:
obviously I am referring only to GPS potions, not to devices and users created or deleted
Any guidance on the best practice for this scenario would be greatly appreciated.