1 Title: Automatically create backup of state file if state shrinks by more than 5% in size
9 If you do some unlucky misconfiguration (like setting disabled services for
10 all services instead of just a few) then you will loose the current state and
11 downtimes of all affected objects - even if you recreate them later again.
12 That is because from the point of view of the core vanished objects are
13 expected to be gone forever and their state is being dropped.
15 In such situations the CMC now automatically creates a copy <tt>state.1</tt>
16 of you state file before creating a new one in its place. Previous backups
17 are shifted to <tt>state.2</tt>, <tt>state.3</tt> and so an. Up to 30 backups
18 are being kept. These backup are <i>never</i> being restored automatically
19 at any time. If you like to get back to your old state, you can copy these
24 OM:cd var/check_mk/core
25 OM:mv state state.away
30 This backup always happens if the size of the new state file is by at least 5%
31 smaller then the old one.
33 Note: The state in this file contains the current OK/WARN/CRIT, the plugin
34 output, the next scheduled check execution, notification, downtimes, comments
35 and stuff like that. It does <i>not</i> contain historic performance data
36 or events. But these do not get lost in the cases mentioned above.