Offsite Disaster Recovery Failover With Preloaded Backup Environments

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing disaster recovery systems require manual intervention for switching between primary and backup sites, leading to prolonged recovery times and instability.

Innovation Solution

An offsite disaster recovery method that automatically determines change information to switch nodes from backup to primary, synchronizes data, and loads environments, using communication channels and resource management to enhance switching speed and stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual intervention is used for switching between primary and backup sites, then system stability is maintained, but switching time is prolonged

Engineering Contradiction:

Improvesystem stabilityVSAvoidswitching time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The backup node pre-loads the running environment and necessary data in advance during normal operation. When a failover is triggered, the pre-loaded environment can be immediately activated without requiring time-consuming loading operations, thus reducing switching time while maintaining system stability through automated procedures.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements automated failover mechanisms where the backup node automatically detects primary node failures, activates its pre-loaded environment, and takes over service provision without manual intervention. This self-service approach eliminates human response time while maintaining stability through automated health checks and controlled transition procedures.

Inventive Principle:

Principle #25Self-service

2Speed

If the environment is loaded in the backup node before switching, then switching speed is improved, but system resource consumption increases

Engineering Contradiction:

Improveswitching speedVSAvoidresource consumption

Core Design Contradiction:

SpeedVSUse of energy by moving object

Solution Approach 1:

Instead of loading the complete environment in the backup node continuously, the system loads only critical components and data locally in the backup node, while maintaining the ability to retrieve additional resources from the primary node or external storage during failover. This selective local loading reduces ongoing resource consumption while ensuring sufficient speed for switching.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system loads a partial environment in the backup node that contains essential components for immediate service restoration. Less critical components can be loaded on-demand during the failover process, balancing the need for fast switching with resource conservation during normal operation.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS20260037398A1Offsite disaster recovery method and device

Publication Date: 2026.02.05 RUIJIE NETWORKS CO LTD

AI summary

This application provides an offsite disaster recovery method and apparatus, a device, and a storage medium. The method is applied to any node in an offsite disaster recovery service, where the any node stores an environment for running a primary task of a primary node; the primary node is configured to control a network device to forward network packets; and the method includes: determining first change information, where the first change information is used to indicate that an identity of the any node changes from a backup node to a primary node, and the backup node is configured to synchronize data of the primary node; and based on the first change information, stopping synchronizing the data of the primary node and running the primary task in the environment.