Data Manager emergency mode
The emergency mode (EM) is designed to ensure that the database is not damaged in the event of low memory space or insufficient virtual memory. In earlier versions, only the disk space was checked by the Data manager. If the value was lower than a defined limit, historical data would not be backed up. If sufficient disk space was available again, the Data manager left EM and resumed normal operation.
You cannot start the DataBG directly from the console.
For the EM, the Data Manager does not only check the disk space but also the virtual memory in short intervals. If the value is below one of two limits, DataBG is ended and the database is closed. The aim of this is to provide a functional database (except when there are default alarms on these occasions).
| Chapter | Content |
| Data manager emergency mode, basics | Introduction and Links to the topics |
| Monitoring the hard disk | The panel for monitoring the hard disk shows the free memory space, enables configuration of the storage limits and contains the status display for the EM. |
| Monitoring virtual memory | The panel shows the free memory space, enables configuration of the storage limits and contains the status display for the EM. |
| Details on monitoring hard disks | For each hard disk to be checked, there is a data point of the type _DiskSpaceCheck. |
| Details on monitoring the virtual memory | Configuring virtual memory monitoring is also realized through an internal data point. This one is of the type _MemoryCheck. |
| Triggering the emergency mode | How to get to the emergency mode and reaction by the Data manager. |
| Data manager in the emergency mode | The highest aim in emergency mode is to maintain a consistent database. However, the system should still be able to run, even if this is with restrictions. |
| Redundancy in the emergency mode | A redundant project does not start if the other system is in backup or emergency mode. |
