Default language.

Important This documentation space contains information about the on-premises version of BMC Helix Discovery. If you are using the SaaS version of BMC Helix Discovery, see BMC Helix Discovery (SaaS).

Partitions and history

This topic is included for users who are interested in the internal mechanisms used by BMC Discovery to store data.

The datastore is divided into the following default partitions:

  • AccessControl — reserved for system use. No user interaction is permitted.
  • Audit — used by the auditing system. No user interaction is permitted.
  • Conjecture — used by the Host Grouping system. User interaction is permitted.
  • DDD — used for Directly Discovered Data in the model. User interaction is permitted.
  • Default — the default partition for storing the modeled IT infrastructure. User interaction is permitted.
  • Logs — used to store system logs.
  • Taxonomy — used to store the taxonomy which is the template defining the nodes, attributes, and relationships used to model networks and applications in the datastore. The taxonomy does not limit you to predefined data, additional kinds can be created too. No user interaction is permitted.
  • _Configuration — used to store system configuration. No user interaction is permitted.
  • _System — used for system tasks. No user interaction is permitted.
  • Shadow partitions are created for each inferred consolidation connection on an inferred consolidation receiver. The shadow partitions are not deleted when the connection is removed, but if the same sender subsequently reconnects, they are reused. No user interaction is permitted, and the shadow partition must not be deleted.

The Default and Taxonomy partitions store a history of all changes for all nodes by default. The Default and Taxonomy partitions can be purged by a user with the model/datastore/partition/partitionname/write permission (where partitionname is a named partition or * for all).

History is not recorded for attributes whose names begin with a double underscore, for example __patch_checksum.

Some default reports rely on history being enabled. When any changes are made to a node, they are recorded by default. Any of the following operations can make the changes:

  • Automatic changes made by:
    • Reasoning
    • Import tools
  • Changes made through the UI

Changes are stored on the node that has been changed. The following items are stored regarding the change:

  • Date Time — A timestamp for the change.
  • User — The user who made the change. Internal users, such as Reasoning, are recorded as such.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*