Host Device Configuration Conversion to Intermediate Format

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing storage systems face challenges when upgrading multi-pathing software, particularly in transitioning configuration information between different database types, leading to potential lock-in with third-party database libraries and restricted flexibility in database library usage post-upgrade.

Innovation Solution

The implementation of a technique that converts configuration information into an intermediate format, such as XML or JSON, during the software upgrade process, allowing seamless transition from one database type to another, thereby avoiding lock-in and enabling flexibility in choosing database libraries post-upgrade.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-pathing software is upgraded to utilize a new database type, then software functionality and performance are improved, but the system becomes locked-in to a specific third-party database library

Engineering Contradiction:

Improvesoftware functionalityVSAvoiddatabase library flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary conversion process that translates configuration information between different database types. A conversion module acts as a mediator, exporting configuration from the old database format, transforming it to an intermediate representation, and then importing it into the new database format. This intermediary mechanism allows the system to upgrade to new database types without being locked in, as the conversion layer abstracts the database-specific details.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of database type compatibility by implementing a configurable conversion framework. The system maintains flexibility by allowing parameter changes in database schema and type while preserving configuration data through structured conversion processes. This enables the system to adapt to different database parameters and types across software upgrades.

Inventive Principle:

Principle #35Parameter changes

2Stability of the object's composition

If configuration information is stored in a proprietary database format, then data integrity is maintained, but migration to different database types becomes difficult

Engineering Contradiction:

Improvedata integrityVSAvoidmigration difficulty

Core Design Contradiction:

Stability of the object's compositionVSEase of manufacture

Solution Approach 1:

The conversion module serves as an intermediary that preserves data integrity during migration. It exports configuration information from the source database using structured queries, transforms the data through an intermediate representation that maintains all necessary information, and imports it into the target database. This intermediary process ensures no data loss occurs during format transitions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a complete copy of the configuration information in an intermediate format during the conversion process. This copying mechanism allows the system to preserve the original configuration data while creating a transformed version for the new database type, ensuring data integrity can be verified and restored if needed.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If database schema changes are implemented across software upgrades, then system adaptability is improved, but configuration compatibility is lost

Engineering Contradiction:

Improveschema flexibilityVSAvoidconfiguration compatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The conversion module acts as an intermediary that handles schema changes while preserving configuration compatibility. It translates configuration data from old schema structures to new schema structures through structured transformation rules, ensuring that the semantic meaning and relationships in the configuration data are maintained despite schema evolutions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary configuration export and validation before executing schema changes. By preparing the configuration data in advance and validating its structure, the system ensures compatibility is maintained through the transition, allowing schema flexibility without losing configuration integrity.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11989156B1Host device conversion of configuration information to an intermediate format to facilitate database transitions

Publication Date: 2024.05.21 DELL PROD LP

AI summary

An apparatus comprises at least one processing device that includes a processor coupled to a memory. The processing device is configured to store configuration information, for utilization by software of a host device, in at least one file of a first database of a first type, and in conjunction with an upgrade of at least a portion of the software, to export the configuration information from the at least one file of the first database to one or more files in an intermediate format, to remove the at least one file of the first database, to export the configuration information from the one or more files in the intermediate format to at least one file of a second database of a second type different than the first type, and to configure the upgraded software to utilize the configuration information of the at least one file of the second database.