Hierarchical Data Archiving System for Cloud Repositories

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data archiving methods result in loss of fidelity, especially for unstructured data, and incur high costs due to system maintenance and storage overhead, as they often convert data to formats like XML or PDF/A, which can be incompatible with native applications and lead to system downtime and increased retrieval latency.

Innovation Solution

A hierarchical archiving system that allows data to be initially archived in native format, with options to transfer it to a long-term format like XML or PDF/A based on specified criteria, such as age or access frequency, enabling balanced long-term readability and short-term usability, while maintaining data in a format compatible with native applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If data is converted to standardized formats like XML or PDF/A for long-term archiving, then long-term readability and accessibility are improved, but data fidelity is lost and conversion overhead increases

Engineering Contradiction:
Improvelong-term readabilityVSAvoiddata fidelity
Core Design Contradiction:
Duration of action of stationary objectVSLoss of information

Solution Approach 1:

The patent segments the archiving process into two distinct phases: short-term archiving in native format to preserve data fidelity and enable immediate accessibility, and long-term archiving in standardized formats (XML, PDF/A) to ensure enduring readability. This segmentation allows the system to optimize for different time horizons separately, avoiding the trade-off by applying different formats to different time periods.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary validation and verification of data before final archiving to ensure data integrity is maintained during the transition from native to standardized formats. This preliminary action includes validating data structure, checking completeness, and verifying accessibility, which minimizes information loss during conversion while still achieving long-term readability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If all production data is archived to ensure compliance and availability, then data accessibility is improved, but storage costs and retrieval processing time increase significantly

Engineering Contradiction:
Improvedata availabilityVSAvoidretrieval processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies different archiving qualities to different data based on local characteristics such as access frequency, data type, and compliance requirements. Frequently accessed data remains in native format for quick retrieval, while less frequently accessed data is converted to standardized formats. This local quality approach ensures data availability while minimizing retrieval processing time by avoiding unnecessary conversions.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the archiving parameters (format, storage location, validation level) based on data characteristics and access patterns. By dynamically adjusting these parameters, the system maintains data availability for compliance purposes while optimizing retrieval speed by keeping commonly accessed data in easily retrievable formats and locations.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If data is archived in native format to maintain fidelity, then data usability is improved, but long-term accessibility and standardization are compromised

Engineering Contradiction:
Improvedata usabilityVSAvoidlong-term accessibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic archiving system that automatically transitions data between native and standardized formats based on time elapsed, access patterns, and compliance requirements. This dynamic approach allows data to maintain high usability in native format during the short term while automatically converting to standardized formats for long-term accessibility, thus adapting to changing needs over time.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses an intermediary validation and conversion layer that bridges native and standardized formats. This intermediary performs intelligent conversion, validating data during the transition and preserving usability characteristics while achieving long-term accessibility. The intermediary ensures that data maintains its essential properties regardless of format changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If legacy systems are maintained to access historical data, then data accessibility is improved, but maintenance costs and system reliability risks increase

Engineering Contradiction:
Improvedata accessibilityVSAvoidsystem maintenance
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts data from legacy systems and archives it in standardized formats that are independent of the original legacy applications. This extraction process separates the data from the legacy system infrastructure, allowing the legacy system to be decommissioned while maintaining data accessibility through the standardized archive. This eliminates the need to maintain complex legacy systems while preserving data reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10019462B1System and method of hierarchical archive management
Publication Date: 2018.07.10 DELL EMC
  • US10019462B1 patent drawing
  • US10019462B1 patent drawing
  • US10019462B1 patent drawing

AI summary

A method, article of manufacture, and apparatus for managing a computing environment, such as a cloud data repository. In some embodiments, this includes providing a data archive, and relegating data items to a second, long-term data archive. In some embodiments, data items may be converted to an archive format prior to being relegated.