The core of Pandora's system is its Database. All the data collected by the monitored machines is stored in this data base, from the administrator's data, to the events, incidents and audit data generated in the system at any time. It is obvious that the efficiency and reliability of this module is vital for the correct functioning of Pandora. A regular data base maintainance is needed. To do so the data base managers can use standard MySQL commands. Maintaining Pandora database in good condition is critital for Pandora to work properly. As the database size will increase linearly, the data will be compacted to reduce the amount of stored data without loosing important information, specially the different graphs that are generated with the processed data. Going to "DB Maintenance" from the Administration menu we will find the Database configuration defined in the "Pandora Setup" option of the Administration menu to compact and delete data. The DB statistics are generated by Agent, on the "DB Maintenance">"DB Information" in the Administration menu, and are represented in two kinds of graphs: Number of modules configured for each of the agents. Number of packages sent by each agent. A package is the group of data linked to the module the agent sends in each interval of time. These graphs can be also viewed from "View Agents">"Statistics" in the Operation menu. Pandora counts with powerful tools for the Administrator to manually purge the majority of data stored in the Database. This includes data generated by both the agents and the own server. The option of purging selected data from a module is used to eliminate those out of range entries, whatever the reason - agent failure, out of range values, testing, DB errors, etc. Eliminating erroneous, incorrect or unnecessary data makes the graphical representation more acuarate and shows the data without peaks or unreal scales. From "DB Maintenance">"Database Debug" in the Administration menu any of the out of range data received from a agent's module can be deleted. The purge settings are: agent, module, minimum and maximum data range. Any parameter out of this minimum/maximum range will be deleted. For example, in a module registering the number of processes, if we are only interested in values between 0 and 100, any values above that number will be usually produced by errors, noise or abnormal circumstances. If we set to range between 0 and 100 all those values below and above - such as -1, 100 or 100000 - will be permanently deleted from the database. All the out of range data received by an agent can be deleted from the "DB Maintainance">"Database Purge" option in the Administration menu. The data is deleted by the following parameters from the "Delete data" screen: Purge all data Purge data over 90 days Purge data over 30 days Purge data over 14 days Purge data over 7 days Purge data over 3 days Purge data over 1 day All the audit data generated by the system can be deleted from "DB Maintenance">"Database Audit", in the Administration menu The data to be deleted is selected by setting the following parameters in the "Delete Data" screen Purge audit data over 90 days Purge audit data over 30 days Purge audit data over 14 days Purge audit data over 7 days Purge audit data over 3 days Purge audit data over 1 day Purge all audit data All the event data generated by the system can be deleted from "DB Maintenance">"Database Event", in the Administration menu The data to be deleted is selected by setting the following parameters in the "Delete Data" screen Purge event data over 90 days Purge event data over 30 days Purge event data over 14 days Purge event data over 7 days Purge event data over 3 days Purge event data over 1 day Purge all event data