Traccar backup server
What problem are you trying to solve?
have a second server as a copy server active 24/7 in case of failure of the first one to be able to access the second one at that time. As indicated I currently have a working one and use server.forward to the second one. To keep users and users up to date, I copied the tc.users tc.devices tc.user.devices tables and some more on a daily basis. I do not copy tc positions since they are being received by the forward. But in that case I have the problem that not everything arrives and of course having to copy the tables daily. I saw the horizontal scalling broafcasting option. But I think they must be in the same database? That's what I don't want. I want everyone to have their own database, so (plus traffic and size) I don't copy the database daily. Also, in case the first fails, just point the GPS at the second and everything is functional.
You can have a database cluster.
greetings to all. I would like to have 2 tracking instances on 2 different vps but there is something about synchronization. I explain. one instance as functional and another as backup. I have used the server.forward option and update the user and device tables daily. (I don't want to have a 3xact copy of the databases since if one is wrong and it is an exact copy, the second will still fail in the long run). but I think that in addition to that the server.forward command actually ends up sending 70% of what happened. I have seen the horizontal scallibg option and the Broadcast. I can use that as an option but each vps with its separate database? Is there any other option you could give me. thank you