Automated Data Storage Library Snapshot for Host Errors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Automated data storage libraries often fail to capture critical logs related to host detected errors or service actions, leading to loss of diagnostic information due to the urgency to restore operations, resulting in incomplete data for root cause analysis.

Innovation Solution

Implementing a processor-based method within the automated data storage library to detect host-related triggering events and capture snapshots of logs, which are then stored for later retrieval, including the use of sensors to monitor door openings, component replacements, and service actions, with a snapshot filter to manage storage and prevent overwhelming log data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If automated data storage library operates without snapshot capture mechanism, then system complexity is reduced and operation speed is maintained, but diagnostic information is lost when host errors occur

Engineering Contradiction:
Improvediagnostic informationVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by continuously capturing and storing snapshots of operational logs before errors occur. When a host error is detected, the pre-captured snapshots containing diagnostic information are immediately retrieved, eliminating the need for post-error data collection and ensuring information preservation without adding complex real-time capture mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of log data in snapshot format and stores them separately from the main operational logs. This copying mechanism preserves diagnostic information without interfering with the primary system operations, allowing error analysis while maintaining system performance and minimizing complexity overhead.

Inventive Principle:
Principle #26Copying

2Reliability

If continuous log monitoring is implemented to capture all host errors, then diagnostic completeness is improved, but system resource consumption and complexity increase

Engineering Contradiction:
Improvediagnostic completenessVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of implementing continuous comprehensive monitoring of all system parameters, the system performs partial monitoring by capturing snapshots at specific intervals and triggering events. This approach achieves sufficient diagnostic completeness for host error analysis while avoiding the complexity and resource consumption of continuous full-system monitoring.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system implements periodic snapshot capture at defined intervals and uses event-triggered snapshots based on host error conditions. This periodic and event-driven approach ensures diagnostic information is captured when needed without requiring continuous monitoring, thereby reducing system complexity and resource usage while maintaining diagnostic completeness.

Inventive Principle:
Principle #19Periodic action

3Loss of information

If snapshots are captured immediately upon host error detection, then diagnostic information is preserved, but system response time for error handling is increased

Engineering Contradiction:
Improvelog data integrityVSAvoiderror handling time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary snapshot capture operations during normal operation, so when a host error occurs, the diagnostic data is already captured and stored. This eliminates the time delay associated with capturing logs after an error occurs, as the information is prepared in advance and immediately available for analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically captures and stores snapshots without requiring manual intervention or complex real-time processing when errors occur. The pre-configured snapshot mechanism serves itself by automatically retrieving and preserving the necessary log data, minimizing the time required for error handling while ensuring log integrity.

Inventive Principle:
Principle #25Self-service

4Loss of information

If all log data is stored without filtering, then complete diagnostic information is available, but storage resources are overwhelmed and retrieval efficiency decreases

Engineering Contradiction:
Improvediagnostic information completenessVSAvoidlog data volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system extracts and stores only the relevant portions of log data that are useful for diagnosing host errors in snapshot format. By taking out only the necessary diagnostic information rather than storing complete log files, the system maintains diagnostic completeness while significantly reducing the volume of stored data and improving retrieval efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies different quality standards to different portions of log data by capturing detailed snapshots for error-related operations while using summarized or filtered data for routine operations. This local quality approach ensures diagnostic information completeness for critical events while reducing overall data volume and storage requirements through selective detail capture.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10223192B2Automated data storage library snapshot for host detected errors
Publication Date: 2019.03.05 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10223192B2 patent drawing
  • US10223192B2 patent drawing
  • US10223192B2 patent drawing

AI summary

Embodiments for automated data storage library snapshot for host detected errors by a processor. A host related trigger associated with a host of an automated data storage library may be detected. The host related triggering event may be unrecognized or undetected as a library error by the automated data storage library. A snapshot of one or more logs in the automated data storage library may be captured upon detection of the host related triggering event. The snapshot of the one or more logs may be stored by the automated data storage library.