Data Migration System Using HSM Interface for File Tiering

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current data migration methods fail to effectively migrate files from a file server without an HSM interface to a destination server with an HSM interface, leading to inadequate file tiering and performance issues, as they cannot acquire necessary tier information without the HSM interface.

Innovation Solution

A data migration system and method that utilize standard file access interfaces to set a migration policy based on attribute information, determining the destination tier for file storage and performing migration accordingly, even from a source server without an HSM interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data migration is performed from a file server without HSM interface to a file server with HSM interface using conventional methods, then migration can be completed, but file tiering cannot be properly established and performance deteriorates

Engineering Contradiction:

Improvefile tiering accuracyVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent introduces an HSM interface as an intermediary component on the migration source file server. This interface acts as a mediator that enables the source server to communicate tiering information to the migration destination, allowing proper file placement decisions to be made during migration even though the original source server did not have native HSM capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the migration process into distinct phases: first acquiring tiering information through the HSM interface, then using migration policies to determine destination tiers, and finally executing the actual file migration. This segmentation allows each aspect to be handled independently and optimally.

Inventive Principle:

Principle #1Segmentation

2Quantity of substance

If all files are migrated to a single tier storage volume, then storage capacity is sufficient, but performance decreases sharply due to frequent tier movements

Engineering Contradiction:

Improvestorage capacityVSAvoidaccess performance

Core Design Contradiction:

Quantity of substanceVSProductivity

Solution Approach 1:

The patent performs preliminary actions by establishing migration policies before the actual migration process. These policies are created based on acquired tiering information and are used to pre-determine the appropriate destination tier for each file, preventing the need for frequent tier movements after migration and ensuring optimal performance from the start.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of file placement by using migration policies that map source tier information to destination tier selections. Instead of uniform placement, files are distributed across multiple tiers based on their characteristics and usage patterns, optimizing the balance between capacity utilization and access performance.

Inventive Principle:

Principle #35Parameter changes

3Quantity of substance

If high capacity storage volumes are used to accommodate all migrated files, then storage capacity is sufficient, but storage cost increases

Engineering Contradiction:

Improvestorage capacityVSAvoidstorage cost

Core Design Contradiction:

Quantity of substanceVSLoss of energy

Solution Approach 1:

The patent applies local quality by placing different types of files in different storage tiers based on their specific characteristics and access requirements. Frequently accessed files are placed in high-performance tiers while less frequently accessed files are placed in lower-cost tiers, optimizing the match between storage quality and file requirements rather than using uniform high-capacity storage for all files.

Inventive Principle:

Principle #3Local quality

4Adaptability or versatility

If migration policy is set using standard file access interface without HSM interface, then migration can proceed from non-HSM sources, but tier information acquisition is limited

Engineering Contradiction:

Improvemigration source compatibilityVSAvoidtier information

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The HSM interface serves as an intermediary that bridges the gap between non-HSM source servers and HSM destination servers. It enables the acquisition of tiering information that would otherwise be unavailable, allowing the migration system to make informed decisions about file placement while maintaining compatibility with diverse source systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9189168B2Data migration system and data migration method

Publication Date: 2015.11.17 HITACHI VANTARA LTD

AI summary

When performing migration of data from a migration source file server which is not endowed with any HSM interface, to a migration destination file server which is endowed with HSM, a volume of high capacity is needed for the migration destination file server, and moreover the performance deteriorates directly after the migration. However, with this system, the manager is enabled to set a migration policy using attribute information which can be acquired through a standard file access interface possessed by a file server program, and, when setting the attribute information of the migration destination file, the tier of the file which is to be created is determined, and the migration destination file is created, on the basis of this attribute information and migration policy.