In a normal distributed environment all slaves have the same config. That means the backup of the master contains the same configuration as it on every slave.
Only the event history and the performance data of the monitored objects are stored on every slave alone.
If only the configuration is important than a backup on the master is enough.
We need the events and perfdata backed up on the slaves as well, so what I did was on each slave set up a backup job in WATO. The backup gets saved in a special directory on the slave that apache has access to (apache is configured so that only the master IP can access that directory). On the master, I’ve then got cron entries which regularly wgets the backup files from the slave URLs and saves them into a redundant NFS share.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.