After searching the forums, I found this brief description of what the history tables are used for:
history_uint - table that stores all integer values
history_log - table that stores all log values
history_text - table that store all text values
history_str - table that stores all string values
history - table that stores all float values
What about history_sync, history_str_sync, and history_uint_sync?
I ask because my Zabbix DB was having some serious corruption problems, and (shame for shame!) my last backup was ancient. So, I tried dropping the corrupted table (history_uint) and re-creating it, and now zabbix is working fine and I'm not really seeing any problems. There's a gap in the history (when the database was down) but apart from that things seem to be humming.
I'm just debating -- keep this database or restore from backup? What problems could arise from the new history_uint table?
Thanks.
history_uint - table that stores all integer values
history_log - table that stores all log values
history_text - table that store all text values
history_str - table that stores all string values
history - table that stores all float values
What about history_sync, history_str_sync, and history_uint_sync?
I ask because my Zabbix DB was having some serious corruption problems, and (shame for shame!) my last backup was ancient. So, I tried dropping the corrupted table (history_uint) and re-creating it, and now zabbix is working fine and I'm not really seeing any problems. There's a gap in the history (when the database was down) but apart from that things seem to be humming.
I'm just debating -- keep this database or restore from backup? What problems could arise from the new history_uint table?
Thanks.
Comment