In-Memory Database Server Migration via Queue Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In-memory database systems face challenges in accurately replicating data and functionality during server migration without significant downtime, as existing methods struggle to maintain real-time synchronization and precise control over the migration process.

Innovation Solution

A system and method for replicating and migrating in-memory database systems that involves active monitoring of queues to determine when data is flushed to disk, allowing for automated shutdown and reboot of servers, and transforming the target server into an exact copy of the source server, minimizing downtime through precise timing and synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional server migration methods are used, then data can be moved between servers, but significant downtime occurs and replication accuracy is compromised

Engineering Contradiction:
Improvereplication accuracyVSAvoidmigration downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by continuously monitoring queue status and determining when data is flushed to disk before initiating the migration process. This allows the target server to be prepared in advance with complete data replication, enabling the source server to be shut down at the optimal moment when data is already synchronized, thereby minimizing downtime while ensuring replication accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by actively monitoring queue status and flush completion to determine the precise moment for migration. This continuous feedback loop ensures that data replication is complete and accurate before the migration executes, allowing the system to adapt the migration timing based on real-time data synchronization status, thus reducing downtime without compromising reliability.

Inventive Principle:
Principle #23Feedback

2Productivity

If manual intervention is used in migration processes, then control over the migration can be maintained, but migration efficiency decreases and downtime increases

Engineering Contradiction:
Improvemigration efficiencyVSAvoidmigration time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically monitoring queue status, determining data flush completion, and executing the migration process without requiring manual intervention. The automated process continuously tracks replication status and triggers the migration at the optimal moment, significantly improving migration efficiency and reducing overall migration time compared to manual methods.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual mechanical control with automated electronic monitoring and control mechanisms. By using software-based queue monitoring and automated decision-making algorithms, the system eliminates human intervention in the migration process, enabling faster, more efficient migrations with precise timing that minimizes downtime while maintaining full control over the migration execution.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20230367742A1System and method for system replication and migration for in-memory database systems
Publication Date: 2023.11.16 OPEN TEXT CORP
  • US20230367742A1 patent drawing
  • US20230367742A1 patent drawing
  • US20230367742A1 patent drawing

AI summary

Systems and methods for performing server migrations in an in-memory database system environment are provided. Various embodiments of the present technology provide systems and methods for actively monitoring a queue of the in-memory database system at the target file system to determined when all of the contents of the queue have been flushed to disk. Responsive to the determination, the source file system can be shut down, and replicated to the target file system.