Processed File Replication for Cross-Region Disaster Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems struggle to effectively minimize data loss and ensure data availability during cross-region disaster recovery in cloud configurations, particularly in the event of a major disaster affecting primary servers, while achieving prompt service availability in the secondary region.

Innovation Solution

A computer-implemented method for cross-regional disaster recovery involving data replication from an active deployment to a standby deployment, ensuring seamless transition and maintaining data availability by replicating files generated during processing to a scalable storage module in the standby deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is replicated from active deployment to standby deployment for disaster recovery, then data availability in secondary region is improved, but data loss during transition cannot be minimized

Engineering Contradiction:
Improvedata availabilityVSAvoiddata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by pre-replicating files generated during data processing from the active deployment to the standby deployment before a disaster occurs. This ensures that the standby deployment already has copies of processed files ready, minimizing data loss during failover while maintaining data availability in the secondary region.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If conventional disaster recovery systems are used, then service availability in secondary region is achieved, but transition time is delayed

Engineering Contradiction:
Improveservice availabilityVSAvoidtransition time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary replication of processed files to the standby deployment before disaster occurs, so that when failover is needed, the transition can happen immediately without waiting for file replication, thus reducing transition time while ensuring service availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating duplicate copies of processed files in the standby deployment. This allows the system to switch to the standby deployment quickly by simply pointing to the copied files, rather than transferring them during disaster recovery, thereby reducing transition time.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If all generated data is stored for later analysis, then analytical flexibility is improved, but storage and processing complexity increases

Engineering Contradiction:
Improveanalytical flexibilityVSAvoidstorage and processing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts only the files generated during data processing (rather than storing all raw data) and replicates these to the standby deployment. This selective extraction maintains analytical flexibility for processed data while reducing storage and processing complexity compared to retaining all generated data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20250258741A1Replicating files generated during processing
Publication Date: 2025.08.14 CISCO TECHNOLOGY INC
  • US20250258741A1 patent drawing
  • US20250258741A1 patent drawing
  • US20250258741A1 patent drawing

AI summary

A computer-implemented method for performing cross regional disaster recovery includes receiving event data at an active deployment of a data intake and query system. The method further includes processing the event data in a plurality of stages of the data intake and query system to convert the event data into searchable buckets of indexed data, wherein files generated at each stage of the processing are uploaded to a first scalable storage module in the active deployment. Further, the method includes replicating the files generated at each stage of the processing to a second scalable storage module in a standby deployment of the data intake and query system. Responsive to an outage at the active deployment, the method includes transitioning control to the standby deployment and recovering the event data at the standby deployment using the files replicated to the second scalable storage module.