Why would you move it to another table? You should be doing proper DB partitioning instead.
Based on your response Anton, I'm guessing the answer is no.
To answer your question, because the data is so huge, the entire table gets included in the backup. Moving & archiving is currently the best solution in our architecture. MySQLdump backup does not selectively ignore specific partitions, so the backup will unnecessarily include the complete data, almost all of which (tc_positions & tc_events) is static old data.
For anyone else interested, this is how we currently do it.
We have a secondary instance of the environment where only the tc_positions & tc_events are restored on an as-needed basis and we run reports for the specific date range as needed.
The answer is no because that doesn't make sense to include something like this.
You can easily backup just part of a table. Your explanation makes even less sense.
Hi,
Is there a way to configure traccar to read past positions / events from archived tables?
I archive data once in 3 months, but if I need to view a report for a previous quarter, I cannot because the data isn't present in the current tc_positions table. Is there a setting that can tell traccar to read older data from archived table? Is there a specific table format (e.g., tc_positions_archive_2025_01 for Jan 2025 data)?
Thank you