Disaster Recovery Tool for Server Configuration and Security Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing disaster recovery systems fail to preserve configuration, security, and runtime data, leading to incomplete restoration of servers and databases after disastrous events, as they only maintain copies of application data, which is insufficient for complex software applications to function correctly.

Innovation Solution

A disaster recovery tool that includes a server monitoring engine, configuration engine, security engine, and runtime engine to detect and copy database configuration files, user logins, file sharing credentials, database jobs, and schedules from production servers to disaster recovery servers, ensuring that all necessary data is maintained and updated.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If only application data is copied to disaster recovery servers, then storage space is conserved and copying speed is improved, but the restored server cannot function correctly because configuration, security, and runtime data are missing

Engineering Contradiction:
Improvefunctional completeness of restored serverVSAvoidcomplexity of data copying process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data copying process into four distinct engine components: server monitoring engine, configuration engine, security engine, and runtime engine. Each engine is responsible for copying specific types of data (application data, configuration data, security data, and runtime data respectively), allowing the system to comprehensively restore all necessary data while maintaining organized and manageable complexity through functional decomposition.

Inventive Principle:
Principle #1Segmentation

2Reliability

If all necessary data including configuration, security, and runtime data is copied, then the restored server can function correctly, but the amount of data to be copied and managed increases significantly

Engineering Contradiction:
Improvefunctional completeness of restored serverVSAvoidvolume of data to be copied
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent creates a universal disaster recovery system where the multi-functional engine architecture can handle multiple types of data (application, configuration, security, runtime) through a unified framework. This allows the system to manage diverse data types systematically, reducing the operational burden despite the increased total data volume, as each engine type processes its specific data category using standardized procedures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If multiple engines are used to copy different types of data, then data completeness is improved, but the system complexity and implementation difficulty increase

Engineering Contradiction:
Improvecompleteness of disaster recoveryVSAvoidease of system implementation
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent divides the complex disaster recovery system into four specialized engine components, each handling a specific data type. This segmentation makes the system easier to implement because each engine can be developed, tested, and deployed independently with well-defined responsibilities, reducing the overall implementation difficulty despite the multi-component architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10255138B2Disaster recovery tool
Publication Date: 2019.04.09 BANK OF AMERICA CORP
  • US10255138B2 patent drawing
  • US10255138B2 patent drawing
  • US10255138B2 patent drawing

AI summary

A disaster recovery tool includes a server monitoring engine, a configuration engine, a security engine, and a runtime engine. The server monitoring engine detects a production server and determines that a disaster recovery server should be created for the production server. The configuration engine compares database configuration files for the production server and the disaster recovery server and copies the database configuration file for the production server to the disaster recovery server. The security engine compares user logins and file sharing credentials of the production server and the disaster recovery server and copies the user login and file sharing credential of the production server to the disaster recovery server. The runtime engine compares database jobs and schedules of the production server and the disaster recovery server and copies the database job and schedule of the production server to the disaster recovery server.