Restoring a Zabbix database backup - not just about restoring the database?

[ZabbixSeeker]

Greetings,

I use xtrabackup to copy and restore the mysql databse. It's about 1 TB large.

I shut down zabbix-server and zabbix-web while restoring. I don't trust them to not keep some query lingering waiting to be executed, that isn't compatible with a restored database.
I let the proxies keep running though ... I have hundreds of them.

Here's what's unclear to me:
- when I start the server again, can it contain inconsistent caches somewhere, (e.g. as files, temporary files or local app data) that may corrupt the restored database or state?
- can proxies corrupt or mess up the database or state?

So my question about restoring backups are:
* Do I need to "reset" or re-install the server or do anyhing more than just shutting it down?
* Do I need to shut down proxies? Do I have to "reset" or re-install them potentially?

Are these things well documented and/or guaranteed?

[cyber]

If you shut down server(s), then your proxies have no place to send their data. Thus, they cannot screw anything up.. During startup your server reads all of its config from DB, there is no files etc to mess with... Even if your proxies send in some data that was collected based on the config they received before server shutdown, server still validates it. And proxies ask for updates very quickly so they sort out their config also quickly... You probably get a gap in data from the restore point to starting server up again... I dont see a big case here, that something could screw your restored DB...

[ZabbixSeeker]

If you shut down server(s), then your proxies have no place to send their data. Thus, they cannot screw anything up.. During startup your server reads all of its config from DB, there is no files etc to mess with... Even if your proxies send in some data that was collected based on the config they received before server shutdown, server still validates it. And proxies ask for updates very quickly so they sort out their config also quickly... You probably get a gap in data from the restore point to starting server up again... I dont see a big case here, that something could screw your restored DB...

Thanks. I assume that I should shut down the web service though? It (or a browser) might hold some invalid state that might clear if I restart the web service?