Garbage Collection Notification for Backup Data Replication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Reference counting mechanisms face inefficiencies due to frequent updates and require additional mechanisms to manage memory and resources effectively, especially in systems with limited memory and real-time applications.

Innovation Solution

Implementing a method that utilizes garbage collection notifications to replicate and delete data objects from a primary source to a backup device, eliminating the need for frequent reference count updates and improving performance by synchronizing data between primary and backup servers through notifications from the garbage collection process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If reference counting is used to manage memory, then objects can be reclaimed as soon as they are no longer referenced, but frequent updates to reference counts degrade system performance

Engineering Contradiction:

Improvetimely reclamation of unreferenced objectsVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by replicating data objects to a backup device before the primary source needs them. Garbage collection notifications trigger advance replication, so when objects are actually needed, they are already available on the backup device, eliminating the need for frequent reference count updates and improving system performance

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces garbage collection notifications as an intermediary mechanism between the primary source and backup device. Instead of directly monitoring reference counts, the system uses GC notifications to trigger replication only when necessary, reducing the overhead of reference counting while ensuring timely object reclamation

Inventive Principle:

Principle #24Intermediary (Mediator)

2Extent of automation

If reference counting is implemented, then memory management becomes automated, but additional mechanisms are required to manage resources effectively in systems with limited memory

Engineering Contradiction:

Improveautomated memory managementVSAvoidresource management mechanisms

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

The patent extracts the resource management complexity from the reference counting mechanism by using garbage collection notifications to trigger replication. This separates the automated memory management function from the replication control logic, reducing the overall device complexity while maintaining effective resource management in systems with limited memory

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The garbage collection notification mechanism serves multiple functions: it triggers replication on the backup device, manages memory reclamation, and coordinates resource allocation between primary and backup sources. This multi-functionality reduces the need for separate resource management mechanisms, simplifying the overall system

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If data objects are replicated to a backup device, then data consistency is maintained, but synchronization overhead increases

Engineering Contradiction:

Improvedata consistency between primary and backupVSAvoidsynchronization time

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

Instead of continuous synchronization, the system uses periodic action triggered by garbage collection notifications. Replication occurs periodically when GC notifications are received, rather than continuously monitoring and synchronizing all changes. This reduces synchronization overhead while maintaining data consistency between primary and backup devices

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The system discards the approach of continuous synchronization and recovers efficiency by using event-driven replication. When garbage collection occurs on the primary source, this triggers a notification to replicate necessary objects to the backup device, reducing synchronization time while maintaining data consistency

Inventive Principle:

Principle #34Discarding and recovering

Data Source

PatentUS8301671B1Method and apparatus providing removal of replicated objects based on garbage collection

Publication Date: 2012.10.30 AVAYA INC

AI summary

A method, apparatus and computer program product for providing removal of replicated objects based on garbage collection is presented. Data objects are replicated from a primary source to a backup device. A notification is received from a garbage collection process for at least one data object replicated from the primary source to the backup device, the notification indicating that the data object should be deleted. The data object having the notification is deleted from the backup destination.