Tiered Database Storage Segmentation for Replication Cost Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems face inefficiencies and high costs due to replicating entire production databases, either on the same high-quality storage system or on lower-quality secondary systems, which affects data retrieval and storage costs.

Innovation Solution

A storage control system that segregates production databases into sections based on replication frequency and storage tier, allowing high-frequency replication of critical data on high-quality systems and lower-frequency replication of less critical data on lower-quality systems, thereby optimizing storage costs and replication efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire production database is replicated to a backup database on the same enterprise class storage system, then data protection is improved, but storage costs and resource usage increase significantly

Engineering Contradiction:
Improvedata protectionVSAvoidstorage costs
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent divides the production database into multiple sections (e.g., frequently accessed sections and infrequently accessed sections) and replicates only specific sections to backup databases. This segmentation allows selective replication based on data importance and access patterns, reducing the volume of data that needs to be replicated while maintaining adequate data protection for critical sections.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different replication strategies to different sections of the database based on their specific characteristics. Critical sections that require high data protection are replicated to enterprise class storage systems, while less critical sections are replicated to lower quality storage systems or replicated less frequently. This local quality approach optimizes storage costs by matching replication quality to data importance.

Inventive Principle:
Principle #3Local quality

2Quantity of substance

If the entire production database is replicated to a lower quality secondary storage system, then storage costs are reduced, but data retrieval capability deteriorates

Engineering Contradiction:
Improvestorage costsVSAvoiddata retrieval capability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments the database into sections with different retrieval requirements. Frequently accessed sections are replicated to higher quality storage systems that provide better retrieval capabilities, while infrequently accessed sections are replicated to lower quality storage systems. This segmentation ensures that data retrieval capability is optimized for sections where it matters most while reducing costs for sections where retrieval speed is less critical.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different storage quality levels to different database sections based on their specific retrieval requirements. Critical sections requiring fast retrieval are stored on enterprise class storage systems, while non-critical sections are stored on lower quality systems. This local quality differentiation resolves the contradiction by ensuring adequate retrieval capability for important data while reducing overall storage costs.

Inventive Principle:
Principle #3Local quality

3Reliability

If the entire production database is replicated frequently, then data protection is improved, but system performance and resource usage deteriorate

Engineering Contradiction:
Improvedata protectionVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the database into sections with different replication frequency requirements. Critical sections are replicated frequently to ensure data protection, while non-critical sections are replicated less frequently. This segmentation reduces the overall replication burden on the system, improving performance while maintaining adequate data protection for sections that require it.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements different replication frequencies for different database sections based on their characteristics. Frequently changing or critical sections are replicated at higher frequencies, while stable or non-critical sections are replicated at lower frequencies. This periodic action with varying frequencies optimizes the balance between data protection and system performance by replicating only when necessary.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS7613747B1Tiered database storage and replication
Publication Date: 2009.11.03 T MOBILE INNOVATIONS LLC
  • US7613747B1 patent drawing
  • US7613747B1 patent drawing
  • US7613747B1 patent drawing

AI summary

A storage network comprising a production database configured to store a first production section on a first tier production storage system and a second production section on a second tier production storage system, a backup database configured to store a first backup section on a first tier backup storage system and a second backup section on a second tier production storage system, and a storage control system configured to replicate the first production section to the first backup session at a first frequency and replicate the second production section to the second backup section at a second frequency that is less than the first frequency.