About Library Data Collection

STA begins receiving library data as soon as you establish a connection to the library. However, the STA user interface does not display the data until STA builds the library configuration model.

To build the initial configuration model, you should initiate a manual data collection as soon as you establish the library connection. After the initial data collection, STA updates the library configuration model through scheduled and triggered data collections.

What is Collected During the Initial Data Collection

  • Locations of activated storage cells
  • Partition information
  • Drive types, identifiers, and locations
  • Media types, volume serial numbers (volsers), and locations

Depending on the size and activity level of the library, the initial data collection may take several minutes to over an hour. The STA user interface does not show a complete picture of the library environment and exchange activity until the data collection completes. During this time, you may see fluctuations in various analytic and summary data. This is normal.

How Data Collections Are Initiated

  • Scheduled—A full collection of all library configuration data occurs automatically every 24 hours at a user-defined time. Schedule this during low levels of library activity.
  • Triggered—STA automatically initiates data collections whenever it detects significant changes in the library state or configuration (for example, the addition of a drive or media, or a change in partition configuration). This is a partial data collection that updates only the library configuration affected by the change. For example, a data collection triggered by the addition of a new media, will only update the media configuration information. Triggered data collections take a short time.
  • Manual—You can initiate a manual data collection at any time, as long as there is an active connection to the library. This is a full collection of all library configuration data. See Manually Collect Library Data.

Affect of Data Collections on Library Performance

The libraries process data collections at a lower priority than regular library operations, so data collections have little impact on library performance. However, performing a data collection during periods of heavy library activity can cause the data collection itself to take longer to complete. Oracle recommends that you perform scheduled and manual data collections during periods of lower library activity.

What Data is Collected from the Library

STA uses data received from the monitored libraries to created and maintain the STA data store. It includes the following information types.

  • Library configuration model — A hierarchical view of the library and device configurations, properties, and statuses.
  • Exchange records — Detailed information about all drive and media exchanges, including drive clean activities.
  • Errors and events — Significant library errors and events.