Cloud Server Migration with Automated Dependency Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for migrating servers to a cloud-computing environment lack the ability to manage the migration of applications and data effectively, particularly in selecting and configuring servers, dependencies, and post-recovery operations, limiting the functionality of server data migration.

Innovation Solution

A computerized method that allows administrators to select and migrate a subset of servers to a cloud-computing platform using a dashboard view in a web browser, automatically determining server attributes and dependency modules, and generating a plan for migration, including capturing and replicating server images in dedupe-storage format for recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current migration methods are used, then data copying is possible, but application migration functionality is lacking

Engineering Contradiction:
Improvemigration functionalityVSAvoidapplication recovery
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The migration system segments the migration process into distinct phases: server selection, attribute determination, dependency module identification, plan generation, and execution. This segmentation allows each phase to be independently managed and optimized, enabling comprehensive application migration while maintaining reliability through structured control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by automatically determining server attributes and identifying dependency modules before migration execution. This advance preparation ensures that all necessary components are identified and configured prior to migration, preventing reliability issues during the actual migration process.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If manual migration planning is used, then control over migration steps is possible, but migration complexity increases

Engineering Contradiction:
Improvemigration managementVSAvoidmigration process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically determining server attributes and identifying dependency modules without requiring manual intervention. This automation reduces the operational burden on administrators while managing the inherent complexity of application migration, making the process easier to operate despite the sophisticated capabilities involved.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system generates migration plans that provide feedback on the migration process, allowing administrators to review and control migration steps. This feedback mechanism maintains ease of operation by keeping administrators informed and in control, while the system handles the complex automatic determination and identification processes.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If server attributes are manually selected, then configuration accuracy is possible, but time consumption increases

Engineering Contradiction:
Improveattribute selectionVSAvoidmigration preparation
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system automatically determines server attributes without manual selection, eliminating time consumption while maintaining precision through automated analysis. The system independently identifies and configures all necessary server attributes, eliminating the trade-off between accuracy and time.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary automatic determination of server attributes before migration execution, ensuring that all attribute selections are completed in advance with high precision. This preliminary automated action eliminates the need for time-consuming manual selection while maintaining configuration accuracy.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If dependency modules are not identified, then migration speed is possible, but post-recovery operations fail

Engineering Contradiction:
Improvemigration speedVSAvoidpost-recovery operations
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary identification of dependency modules before migration execution, ensuring that all necessary components are identified in advance. This preliminary action enables fast migration execution while guaranteeing that post-recovery operations can be successfully executed, as all dependencies are already known and configured.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system incorporates dependency module identification into the migration plan generation process, providing feedback that ensures all necessary modules are accounted for. This feedback mechanism maintains migration speed by automating the identification process while ensuring reliability through comprehensive dependency coverage.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11086662B2Method and system of migrating applications to a cloud-computing environment
Publication Date: 2021.08.10 PERSISTENT SYSTEMS INC
  • US11086662B2 patent drawing
  • US11086662B2 patent drawing
  • US11086662B2 patent drawing

AI summary

In one aspect, a computerized method includes the step of selecting a subset of servers of a set of servers to migrate to a specified cloud-computing platform. An administrator utilizes a dashboard view provided in a web browser to identify the subset of servers. The computerized method includes the step of selecting a sequence of migration steps to manage a migration of the subset of servers to the specified cloud-computing platform, wherein the administrator utilizes the dashboard view to generate a plan for a server-data migration of the subset of servers. The computerized method includes the step of automatically determining a set of attributes of the subset of servers. The computerized method includes the step to automatically determining a set of dependency modules associated with the subset of servers to migrate and reinstall upon migration of the subset of servers.