Storage System Data Transformation for Application Instances

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current systems require dedicated conversion programs to handle application-instance specific data, which can be time-consuming and resource-intensive, especially when accessing or recovering data across different instances of applications like IBM Db2 Database.

Innovation Solution

A mechanism that transforms application-instance specific data at the storage system independently of data access, allowing components to be modified either at the storage system or during access by a different instance, reducing the need for dedicated host-based conversion programs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a dedicated conversion program runs on the host system to transform application-instance specific data, then the data can be properly adapted for access by different instances, but the host resources are significantly consumed and other running processes are detrimentally affected

Engineering Contradiction:

Improvedata adaptabilityVSAvoidhost resource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The data transformation function is extracted from the host system and relocated to the storage system. The storage system independently performs the transformation of application-instance specific data components (such as OBIDs) without requiring host-based conversion programs, thereby freeing host resources for other processes while maintaining data adaptability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The storage system acts as an intermediary between different application instances and the stored data. It performs the necessary data transformation and adaptation functions, serving as a mediator that enables cross-instance data access without requiring the host to run dedicated conversion programs.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a dedicated conversion program is used to transform application-instance specific data, then data can be accessed across different instances, but the process is time-consuming and reduces overall system productivity

Engineering Contradiction:

Improvecross-instance data accessVSAvoidsystem throughput

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The storage system performs data transformation in advance or independently of host access operations. By pre-processing or independently transforming application-instance specific data components, the system eliminates the need for time-consuming conversion programs to run on the host during data access operations, thereby improving overall system productivity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The storage system provides self-service by autonomously performing the data transformation function. It identifies and transforms application-instance specific data components without requiring external host-based conversion programs, thereby reducing processing time and improving system throughput while maintaining cross-instance data accessibility.

Inventive Principle:

Principle #25Self-service

3Use of energy by moving object

If application-instance specific data is transformed at the storage system independently of data access, then host resources are freed for other processes, but the transformation must be performed separately from access operations

Engineering Contradiction:

Improvehost resource availabilityVSAvoidtransformation process complexity

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The storage system is enhanced with universal data transformation capabilities that work across different application instances and data types. This multi-functional approach allows the storage system to handle various application-instance specific data components (such as OBIDs for different database instances) using a unified transformation mechanism, managing complexity through standardization.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The storage system autonomously performs transformation of application-instance specific data components independently of host access operations. It self-identifies data requiring transformation and executes the transformation process without host intervention, freeing host resources while managing transformation complexity through automated storage-side processing.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11822792B2Transforming application-instance specific data

Publication Date: 2023.11.21 EMC IP HLDG CO LLC

AI summary

Transforming data that is provided by a first instance of an application that uses application-instance specific data includes determining if a component of the data is an application-instance specific component and, if the component is an application-instance specific component, transforming the component either at a storage system containing the data or as the component is being accessed by a second instance of the application, different from the first instance. Transforming the component at a storage system containing the data may be performed independently of any accesses of the data. Transforming the component at a storage system containing the data may be performed by the storage system. The first instance of the application may run on a first host and the second instance of the application may run on a second host different from the first host. The first and second instances of the application may run on a same host.