Replicated Data Backup Coordination via Secondary Node Assessment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data backup technologies face challenges in coordinating backups between multiple nodes using replicated data, often resulting in incomplete or inconsistent backups, especially when performed on secondary or passive nodes, and can fail if the secondary node is unavailable, leading to increased burden on primary nodes and resource requirements.

Innovation Solution

A method and system that identify replicated data on primary and secondary nodes, determining if a backup can be performed on the secondary node, and creating a backup copy on the secondary node if possible, or on the primary node if not, thereby ensuring complete and consistent backups while reducing the load on primary nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If backup is performed on secondary node, then backup efficiency is improved and primary node burden is reduced, but backup consistency may be compromised due to replication status uncertainty

Engineering Contradiction:
Improvebackup efficiencyVSAvoidbackup consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by checking replication status and determining backup capability on the secondary node before executing the backup. This preliminary assessment ensures that the secondary node has the necessary data and capability to perform a consistent backup, thereby resolving the contradiction between improving backup efficiency and maintaining backup consistency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring replication status and using this information to determine whether the secondary node can perform a backup. This feedback loop ensures that backup decisions are based on current system state, maintaining consistency while enabling secondary nodes to perform backups when appropriate.

Inventive Principle:
Principle #23Feedback

2Reliability

If full backup includes both replicated and non-replicated storage, then comprehensive backup is achieved, but backup complexity increases

Engineering Contradiction:
Improvebackup completenessVSAvoidbackup coordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the backup process by separately handling replicated and non-replicated storage. It identifies which storage is replicated and which is not, then performs appropriate backup operations for each type. This segmentation reduces complexity by breaking down the comprehensive backup task into manageable, distinct operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts and identifies replicated storage from the total storage set, separating it from non-replicated storage. This extraction allows the backup process to treat different storage types differently, simplifying the overall backup coordination while ensuring comprehensive coverage of both replicated and non-replicated data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9355117B1Techniques for backing up replicated data
Publication Date: 2016.05.31 COHESITY INC
  • US9355117B1 patent drawing
  • US9355117B1 patent drawing
  • US9355117B1 patent drawing

AI summary

Techniques for backing up replicated data are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for backing up replicated data comprising identifying replicated data on a primary node and a secondary node, and determining whether a backup is capable of being performed on the secondary node. In the event a backup is capable of being performed on the secondary node, the method may create a backup copy of the identified replicated data on the secondary node, and in the event a backup is not capable of being performed on the secondary node, the method may create a backup copy of the identified replicated data on the primary node.