Okay, so I have a set of Zabbix instances which I am performing nightly backups on via mysqldump. The backups are taken in three "stages" (three separate .sql files).
The stages are set up as follows:
Stage 1:
Bare Schema
Stage 2:
"Configuration Data" i.e. hosts, users, triggers, actions, etc.
Stage 3:
"Historical Data" i.e. graphs, events, etc.
Backups are taken nightly in that exact order, and are also restored in that exact order.
So with that explanation out of the way, there is a problem I'm facing:
When I restore the backups. Certain tables seem to end up with the same problem...
Let's say for instance, I restore from a backup, and then try to add a new user or add a new trigger via the web interface. I end up with the following error:
Duplicate entry for key 'PRIMARY'
Anyone seen this before?
The stages are set up as follows:
Stage 1:
Bare Schema
Stage 2:
"Configuration Data" i.e. hosts, users, triggers, actions, etc.
Stage 3:
"Historical Data" i.e. graphs, events, etc.
Backups are taken nightly in that exact order, and are also restored in that exact order.
So with that explanation out of the way, there is a problem I'm facing:
When I restore the backups. Certain tables seem to end up with the same problem...
Let's say for instance, I restore from a backup, and then try to add a new user or add a new trigger via the web interface. I end up with the following error:
Duplicate entry for key 'PRIMARY'
Anyone seen this before?