Database Migration Endpoint Encryption Compatibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Database migration in high availability and disaster recovery (HADR) computing environments is complex and prone to significant downtime due to the complexity of clustered architectures, hardware/OS end-of-life issues, and the need for multiple configuration changes, which can lead to data loss and corruption.

Innovation Solution

The method involves modifying endpoints to use compatible encryption mechanisms (AES and RC4), configuring database mirroring and AlwaysOn availability groups, and performing a failover operation to migrate databases while minimizing changes and ensuring data synchronization, thereby allowing a single connection string change and near-zero downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database mirroring and AlwaysOn availability groups are configured in hybrid HADR environments, then high availability and disaster recovery are ensured, but system complexity and configuration difficulty increase significantly

Engineering Contradiction:

Improvehigh availability and disaster recoveryVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines database mirroring and AlwaysOn availability groups into a unified HADR configuration, allowing both high availability mechanisms to coexist and work together within the same system architecture, thereby ensuring comprehensive reliability while managing complexity through integration

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system design allows the database endpoint to support multiple encryption mechanisms (AES and RC4) simultaneously, making it universally compatible with both database mirroring and AlwaysOn availability group protocols, thereby enabling a single configuration to serve multiple HADR functions

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If encryption mechanisms are modified to support multiple algorithms, then compatibility with both mirroring and AlwaysOn is achieved, but endpoint configuration complexity increases

Engineering Contradiction:

Improveencryption compatibilityVSAvoidendpoint configuration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The endpoint is configured to support multiple encryption algorithms (AES and RC4) simultaneously, making it universally compatible with both database mirroring and AlwaysOn availability group protocols, thereby enabling a single configuration to serve multiple HADR functions without requiring separate endpoints for each protocol

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The endpoint encryption parameters are modified to accept and process multiple encryption algorithms, transitioning from a single-algorithm configuration to a multi-algorithm configuration that can dynamically select the appropriate encryption method based on the communication protocol being used

Inventive Principle:

Principle #35Parameter changes

3Productivity

If database migration is performed in HADR environments, then system modernization and hardware updates are achieved, but downtime and data loss risks increase

Engineering Contradiction:

Improvesystem modernizationVSAvoiddowntime

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The target database server is pre-configured with both database mirroring and AlwaysOn availability group settings before the migration begins, allowing the failover to execute smoothly without requiring post-migration configuration adjustments, thereby minimizing downtime and preventing data loss

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements continuous data synchronization and status monitoring during the migration process, providing real-time feedback on replication health and consistency, which allows for immediate detection and correction of any issues that could lead to data loss or extended downtime

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11144405B2Optimizing database migration in high availability and disaster recovery computing environments

Publication Date: 2021.10.12 DELL PROD LP

AI summary

Disclosed herein are methods, systems, and processes to optimize migration of databases in high availability and disaster recovery (HADR) computing environments. An endpoint associated with a new primary database server is modified to be compatible with a first encryption mechanism and a second encryption mechanism. Database mirroring between an old primary database server and an old secondary database server is disabled, and database mirroring is configured between the old primary database server and the new primary database server. A failover operation is performed by migrating one or more databases from the old primary database to the new primary database, and database mirroring between the old primary database server and the new primary database server is disabled.