Diagnostics database archiving guide

Irrespective of the repetitive inspection, carried out by archiving job of evweb periodically at every 6 hours, there could be situations where evweb database is stressed due to continuous flow events. To handle such stressed conditions, there is provision to clean the evweb DB by tracking the number of events received since the product startup. Once the number of events inserted in the evweb meets the threshold value of 100, the archiving is triggered automatically for clearing the space. For more information, see Archiving in Evweb under stressed conditions

Archiving in LOGDB/LOGARCHDB database

The archiving is triggered on the initial product start-up. Use the following commands for starting the product in

order to trigger archiving.

 

 

cimprovider -dm SFMProviderModule

(disabling the SFM)

cimprovider -em SFMProviderModule

(enabling the SFM)

 

OR

 

cimserver –s

(stopping the cimserver)

 

cimserver

(starting the cimserver)

 

As soon as the product restarts/starts, the job responsible for performing archiving in LOGDB registers itself as a repetitive job. Once successfully registered, it gets called after every 72 minutes. Itchecks if archiving is required based on the space and age conditions.

If any of the criteria as defined in the age/space condition are met, the archiving job triggers the archiving and deletes sufficient amount of space from the current and archive DBs.

The formula used for calculating the number of pages:

Pages to freed up = [Actual number of pages currently held] - [configured number of pages] + [15% (configured number of pages)]

To Trigger Archiving in IOProviders

The IO providers do not employ any mechanism for the archiving. The events in the respective database of IO providers use the following to delete the events from the database.

1.On restarting the product, the IO providers checks for the number of events in the DB. If the number of events in DB is more than 4000, then 25% of 4000 i.e., 1000 events are deleted from the database.

2.However, it is worth noting here that, the check for the number of events exceeding more than 4000 events is used only at the product startup.

Archiving in Evweb under stressed conditions

SysFaultMgmt has an internal counter which keeps track of the number of events been inserted in the evweb DB. When this counter exceeds 100, archiving is called to empty the space by either transferring from the current DB to archive DB or by deleting the events from the archive DB. Events from archive DB are deleted if the number of pages currently held by the archive DB exceeds configured limits.

Limitation of Archiving Mechanism

The archiving mechanism in the SysFaultMgmt deletes events in order to free up the space. The Postgres vacuum daemon refreshes the meta tables related to statistics regularly. But it is seen that the heavily accessed (insert, select, update) DBs, often requires VACCUUM FULL operation to be called on them to update the internal

6

Page 6 Page 8
Page 7
Image 7
HP UX 11i WBEM Software manual Limitation of Archiving Mechanism, To Trigger Archiving in IOProviders
Page 6 Page 8

UX 11i WBEM Software specifications

HP-UX 11i WBEM Software is a powerful tool designed to improve systems management in enterprise environments by utilizing the Web-Based Enterprise Management (WBEM) standard. This software is part of the HP-UX operating system, which is HP's proprietary Unix variant, and it offers a robust set of features designed to enhance the performance, reliability, and security of enterprise systems.

One of the main features of HP-UX 11i WBEM Software is its ability to provide a standardized interface for system management. WBEM is a protocol that allows for the management of networked hardware and software components in a consistent, interoperable manner. This feature is particularly beneficial for organizations that rely on a diverse range of hardware and applications, as it simplifies the integration of various system management tools into a unified framework.

Another important characteristic is the software’s support for CIM (Common Information Model). CIM is a standard designed to facilitate information exchange about the management of systems, networks, and services. HP-UX 11i WBEM Software uses CIM to enable administrators to gain a comprehensive view of their IT infrastructure, facilitating better decision-making and more effective resource management.

The adaptability of HP-UX 11i WBEM Software is noteworthy. It is designed to be extensible, allowing developers to create custom extensions and models that cater to specific business needs. This extensibility ensures that organizations can tailor the software to their unique environments, optimizing performance and enhancing operational efficiency.

Security is also a critical focus of HP-UX 11i WBEM Software. The architecture includes strong authentication mechanisms and access controls to safeguard sensitive data and management operations. This focus on security helps organizations maintain compliance with industry regulations and protects against unauthorized access.

Integration with existing management tools is another significant advantage. HP-UX 11i WBEM Software can be used alongside other system management solutions and protocols, allowing for seamless interoperability in diverse IT environments. This characteristic encourages organizations to leverage their current investments in management solutions while enhancing their capabilities through the use of WBEM.

In summary, HP-UX 11i WBEM Software is an integral part of HP's commitment to providing innovative solutions for enterprise systems management. Its standardized management interface, CIM support, extensibility, robust security features, and integration capabilities make it a valuable asset for organizations aiming to streamline their IT operations and improve overall system performance.
Top Page Image Contents