Dynamic Database Replica Management for Data Loss Prevention

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Large-scale data centers face increased risk of data loss due to fixed replica numbers, which become inadequate as database size grows, leading to prolonged rebuild times and higher risks during replica failure.

Innovation Solution

Dynamically varying the number of database replicas based on actual database size using two thresholds (hard and soft) to manage replica creation and deletion, ensuring adequate redundancy and minimizing data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a fixed number of replicas is used for all databases, then device complexity is reduced, but reliability deteriorates as database size grows

Engineering Contradiction:

Improvedata loss riskVSAvoidreplica management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies dynamics by making the number of replicas variable rather than fixed. The system dynamically adjusts the replication factor based on database size, transitioning from a static configuration to a dynamic one that adapts to changing data volumes, thereby maintaining appropriate redundancy levels without excessive complexity

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of replica count based on database size thresholds. When database size exceeds a threshold, the system increases the number of replicas; when size decreases below a threshold, it reduces replicas. This parameter adjustment resolves the contradiction by aligning redundancy levels with actual data requirements

Inventive Principle:

Principle #35Parameter changes

2Reliability

If a predetermined number of replicas is used for all databases, then ease of operation is improved, but reliability worsens when database size exceeds threshold

Engineering Contradiction:

Improvedata redundancyVSAvoidreplica configuration

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system performs self-service by automatically monitoring database size and adjusting replica counts without manual intervention. The database management system autonomously detects when to add or remove replicas based on size thresholds, eliminating the need for user configuration while maintaining appropriate redundancy

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent implements feedback mechanisms where the system continuously monitors database size and adjusts replica configuration accordingly. This closed-loop feedback ensures that redundancy levels automatically adapt to data volume changes, maintaining reliability without requiring manual user input

Inventive Principle:

Principle #23Feedback

3Reliability

If additional replicas are added when database size increases, then reliability is improved, but use of energy and resources increases

Engineering Contradiction:

Improvedata loss protectionVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent changes the resource allocation parameter by adjusting replica count based on database size thresholds. The system only adds replicas when necessary (when size exceeds threshold) and removes them when no longer needed (when size drops below threshold), optimizing resource consumption while maintaining reliability

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The system applies partial action by adding only the necessary number of replicas when database size increases, rather than maintaining a fixed high number of replicas always. This partial deployment of redundancy resources only when needed reduces overall energy consumption while maintaining adequate protection

Inventive Principle:

Principle #16Partial or excessive action

4Reliability

If the number of replicas is increased to prevent data loss, then reliability is improved, but device complexity and resource management difficulty increase

Engineering Contradiction:

Improvedata integrityVSAvoidreplica management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The database management system performs self-service by automatically managing replica creation and deletion based on size thresholds. This autonomous management eliminates complex manual replica coordination while maintaining data integrity through appropriate redundancy levels

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system transitions from static replica configuration to dynamic adjustment based on real-time database size monitoring. This dynamic approach simplifies management by automatically adapting replica counts to actual needs rather than requiring complex manual configuration

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS9053166B2Dynamically varying the number of database replicas

Publication Date: 2015.06.09 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Embodiments of the invention dynamically vary the number of replicas based on certain conditions to protect users from data loss. The size of the database is one condition that can be used to determine the number of replicas required. A database system may create three replicas. When the database size exceeds a first threshold, a fourth replica may be created. The fourth replica is maintained as long as the database size is above a second threshold that is smaller than the first threshold. However, when the database shrinks below the second threshold, then the fourth replica is deleted. Using two different thresholds in this manner prevents the system from frequently cycling between three and four replicas.