User-Initiated Snapshot Replication for Synchronized Data Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication systems face challenges in efficiently replicating unsynchronized objects in synchronized replication systems without disrupting object creation and manipulation at the source repository, while maintaining the normal order of replication and detecting only the objects that require replication.

Innovation Solution

A user-initiated replication method that creates a snapshot of selected objects, compares their state with the target destination, and initiates replication tasks only for unsynchronized objects, ensuring that replication occurs in the exact order of operations and does not disrupt local object operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If replication is initiated for all objects in a synchronized replication system, then data consistency is improved, but system performance deteriorates due to unnecessary replication of already synchronized objects

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system automatically tracks and identifies unsynchronized objects through change detection mechanisms, eliminating the need for manual assessment. The replication process serves itself by using metadata and change logs to determine which objects require replication, reducing overhead and improving efficiency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces traditional mechanical comparison methods (full object comparison) with metadata-based change detection. By using change logs, version identifiers, and metadata tracking, the system efficiently identifies unsynchronized objects without performing heavy mechanical comparisons of entire objects.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If replication processes are initiated frequently to ensure data consistency, then data availability is improved, but loss of time increases due to repeated replication operations

Engineering Contradiction:
Improvedata availabilityVSAvoidreplication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements periodic change detection and replication triggering based on object modification events. Instead of continuous or frequent periodic replication, the system activates replication only when changes are detected, using event-driven periodic action to minimize unnecessary replication operations and reduce time loss.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs preliminary change detection and object state assessment before initiating replication. By pre-identifying unsynchronized objects through metadata comparison and change log analysis, the system prepares replication tasks in advance, reducing actual replication time and avoiding unnecessary operations.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the system replicates all objects regardless of synchronization state, then completeness is improved, but device complexity increases due to overhead in tracking and managing replication states

Engineering Contradiction:
Improvereplication completenessVSAvoidsystem overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts only the essential synchronization state information (metadata, change logs, version identifiers) from full objects, separating the tracking mechanism from the actual data. This extraction approach maintains replication completeness while significantly reducing the complexity of tracking and managing replication states.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the parameters used for tracking replication state from full object copies to lightweight metadata attributes (version numbers, timestamps, change identifiers). This parameter transformation maintains the ability to detect unsynchronized objects while reducing system overhead and complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10657153B2User initiated replication in a synchronized object replication system
Publication Date: 2020.05.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10657153B2 patent drawing
  • US10657153B2 patent drawing
  • US10657153B2 patent drawing

AI summary

A snapshot of selected objects in a source repository is created in response to the user-initiated replication. The snapshot is designated as a snapshot replication job. Unsynchronized objects in a target destination are detected by comparing a state of the selected objects in the snapshot with a current state of the target destination at the time of execution of the snapshot replication job. An object identification (ID) and a state ID are sent to the target destination and used to locate and compare the selected object with a current state of the selected object in the target destination.