Automated Log Collection for Data Storage Libraries

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Automated data storage libraries often fail to capture and retain critical log data during maintenance or error events, leading to loss of diagnostic information due to the urgency to restore operations, resulting in incomplete analysis during troubleshooting.

Innovation Solution

Implementing a processor-based method for automatic log collection that captures snapshots of error logs, service logs, and accessor logs upon detecting specific triggering events, such as door openings or component replacements, and stores them for later retrieval, with mechanisms to manage snapshot storage by overwriting older logs if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If log data is stored continuously in automated data storage libraries, then diagnostic information is preserved, but storage space is consumed and system complexity increases

Engineering Contradiction:

Improvelog data preservationVSAvoidlog management system complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The system proactively captures log snapshots at predetermined trigger events (errors, warnings, maintenance activities) before diagnostic information is lost. This preliminary action ensures critical data is preserved without requiring continuous storage of all log data, thereby reducing storage consumption and system complexity while maintaining diagnostic capability.

Inventive Principle:

Principle #10Preliminary action

2Loss of information

If log snapshots are captured frequently to ensure complete diagnostic information, then troubleshooting effectiveness is improved, but storage space is consumed

Engineering Contradiction:

Improvediagnostic information completenessVSAvoidstorage space consumption

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The system captures log snapshots at predetermined trigger events (errors, warnings, maintenance activities) before diagnostic information is lost. This preliminary action ensures critical data is preserved without requiring continuous storage of all log data, thereby reducing storage consumption and system complexity while maintaining diagnostic capability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of capturing all log data continuously (excessive action), the system selectively captures only relevant log snapshots at trigger events (partial action). This approach captures sufficient diagnostic information for effective troubleshooting while minimizing storage space consumption by avoiding redundant continuous logging.

Inventive Principle:

Principle #16Partial or excessive action

3Loss of information

If manual log collection is performed during maintenance events, then diagnostic data can be retrieved, but time is lost and data may be overwritten

Engineering Contradiction:

Improvelog data retrievalVSAvoidmaintenance time

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system automatically captures and stores log snapshots without requiring manual intervention during maintenance events. This self-service capability eliminates the time loss associated with manual log collection and prevents data overwrite by ensuring logs are captured and preserved automatically at the moment of trigger events.

Inventive Principle:

Principle #25Self-service

4Loss of information

If all log data is retained without management mechanisms, then complete diagnostic history is available, but storage resources are wasted

Engineering Contradiction:

Improvediagnostic history completenessVSAvoidstorage resource waste

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10713126B2Automatic log collection for an automated data storage library

Publication Date: 2020.07.14 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Embodiments for automatic log collection of an automated data storage library by a processor. A snapshot of one or more error logs, service logs, accessor logs, and data logs is captured in the automated data storage library upon detection of an occurrence of a triggering event within the automated data storage library. The snapshot of the one or more logs in the automated data storage library is stored.