Coherency Group Backup via ISB Clone Volumes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data backup and recovery systems, particularly in healthcare industries using the Integrated Serverless Backup (ISB) protocol, lack the ability to perform scheduled backups, recover data at specific points in time, and conduct other replication operations efficiently, making it challenging to ensure full data recovery without corrupting other data or processes.

Innovation Solution

The system employs a network of host computers into coherency groups, utilizing production and clone volumes to create snapshots at various points in time, allowing for remote backup and recovery, mirroring, and replication operations through the ISB protocol, enabling efficient data management and disaster recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If basic backup operations are performed using ISB protocol, then data backup capability is provided, but the ability to perform scheduled backups, recover data at specific points in time, and conduct replication operations is lacking

Engineering Contradiction:
Improvebackup operation flexibilityVSAvoiddata recovery completeness
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments backup operations into distinct types (scheduled backups, on-demand backups, replication operations) and organizes data into coherency groups that can be independently managed. This allows different backup strategies to be applied to different data segments, providing both flexibility in operation types and reliability through targeted recovery of specific coherency groups.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates snapshots at predetermined intervals and stores them in advance before they are needed for recovery. These pre-created snapshots enable rapid restoration to specific points in time without requiring complex calculations during disaster recovery, thus providing both scheduling flexibility and reliable recovery capability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If data is restored from backup copies, then data recovery is achieved, but full recovery without corrupting other data or processes is challenging

Engineering Contradiction:
Improvedata recovery safetyVSAvoidrecovery operation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts and isolates specific coherency groups from the overall data set, allowing individual groups to be restored independently without affecting other data. This extraction approach enables safe recovery of only the necessary data portions, preventing corruption of unrelated data and processes while simplifying recovery operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates and maintains multiple copy versions of data through snapshots and replication operations. These copies serve as isolated restoration points that can be tested and verified before actual recovery, ensuring data safety without requiring complex in-situ recovery procedures that might corrupt existing data.

Inventive Principle:
Principle #26Copying

3Reliability

If snapshots are stored on separate storage devices, then data integrity is ensured and quick restoration is facilitated, but storage infrastructure complexity increases

Engineering Contradiction:
Improvedata restoration reliabilityVSAvoidstorage system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces storage devices as intermediary components between the primary data storage and the backup/recovery operations. These intermediary storage devices hold snapshots and backup copies, isolating the recovery process from the production system and ensuring data integrity. The mediator approach simplifies restoration by providing dedicated storage pathways while managing infrastructure complexity through standardized storage interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7725669B1Backup and restore operations using coherency groups for ISB protocol systems
Publication Date: 2010.05.25 EMC IP HLDG CO LLC
  • US7725669B1 patent drawing
  • US7725669B1 patent drawing
  • US7725669B1 patent drawing

AI summary

Systems and methods for performing scheduled backups and recovery of data generated by one or more production applications operating on a MAGIC platform located on two or more host computers in a coherency group. The data for a coherency group is stored in a primary storage in the form of one or more production volumes and ISB protocol is used to create one or more clone volumes. Exemplary methods for backing up one or more clone volumes for a coherency group to a backup storage include copying the one or more clone volumes to a backup storage or creating a snapshot of the one or more clone volumes. The ISB functions of splitting and/or reconnecting the one or more production volumes and one or more clone volumes occur at substantially the same time for all the two or more host computers in the coherency group.