Cloud Management Node Disaster Recovery Method Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In hybrid cloud environments, existing disaster recovery systems incur high resource costs at secondary cloud sites due to increased usage when providing services from primary on-premise sites, as they require maintaining high performance capabilities, which is not cost-effective for all services.

Innovation Solution

A disaster recovery system with a cloud management node that determines the appropriate disaster recovery method and data transfer settings based on the importance of applications, using multi-site or pilot-light types, and optimizes resource allocation by selecting suitable storage and network resources, reducing unnecessary resource usage and costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the same system as the primary site is constantly operated in the secondary site (multi-site type), then the reliability of disaster recovery is improved, but the resource cost at the cloud side increases

Engineering Contradiction:
Improvedisaster recovery reliabilityVSAvoidresource cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by differentiating the disaster recovery configuration based on service importance. Critical services use the multi-site type with full system operation in the secondary site, while non-critical services use the pilot-light type with minimal standby resources. This localized differentiation resolves the contradiction by optimizing reliability and cost for each service category rather than applying a uniform approach.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the disaster recovery system into two distinct modes: multi-site type for critical services and pilot-light type for non-critical services. The cloud management node automatically selects the appropriate mode based on service importance levels. This segmentation allows the system to achieve high reliability for essential services while minimizing resource costs for less critical services.

Inventive Principle:
Principle #1Segmentation

2Loss of energy

If minimal standby resources are kept in the secondary site (pilot-light type), then the resource cost is reduced, but the recovery time increases

Engineering Contradiction:
Improveresource costVSAvoidrecovery time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent applies local quality by assigning different recovery configurations to services based on their importance. Non-critical services use the pilot-light type with minimal standby resources and longer recovery time, while critical services use the multi-site type with full readiness and shorter recovery time. This resolves the contradiction by allowing longer recovery time only for services where it is acceptable.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the recovery approach into two types: pilot-light for non-critical services accepting longer recovery time, and multi-site for critical services requiring fast recovery. The cloud management node automatically routes services to the appropriate type based on importance levels, optimizing the balance between cost and recovery time for each service category.

Inventive Principle:
Principle #1Segmentation

3Reliability

If high performance capabilities are maintained at the secondary cloud site, then the service quality is improved, but the resource usage and cost increase

Engineering Contradiction:
Improveservice qualityVSAvoidresource usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by providing high performance capabilities only to services that require them (critical services in multi-site type), while using minimal resources for non-critical services (pilot-light type). The cloud management node determines service importance and allocates appropriate performance levels, resolving the contradiction between service quality and resource usage.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11841779B2Disaster recovery system and disaster recovery method
Publication Date: 2023.12.12 HITACHI VANTARA LTD
  • US11841779B2 patent drawing
  • US11841779B2 patent drawing
  • US11841779B2 patent drawing

AI summary

In the disaster recovery system exemplified by the information processing system, the cloud management node manages the importance information indicating the importance placed on the performance of each application to be executed by the primary site in correspondence with the virtual computer for executing the application, determines the DR method applied to the virtual computer and the application by selection from multiple types of DR methods based on the importance information of the corresponding application for each of the virtual computers, and determines a content of a predetermined set item applied to transfer of data to be used by the virtual computer.