Automated Replication Agents for Clustered Application File Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In clustered environments, existing technologies lack an efficient method for automating the replication of application files based on the state and configuration of applications, leading to potential downtime and management challenges due to the manual nature of file synchronization across multiple nodes.

Innovation Solution

A method and apparatus where a clustering engine notifies replication agents of changes in application state and configuration through a clustering API, allowing these agents to modify and enforce replication policies, thereby automating the replication of application files across cluster nodes, either immediately or periodically, based on received status information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual file synchronization is used across cluster nodes, then administrative control is maintained, but downtime increases and productivity decreases

Engineering Contradiction:
Improveapplication availabilityVSAvoidfile synchronization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The replication agent automatically monitors application state changes and triggers file replication without administrative intervention. The system self-manages the synchronization process by receiving status information from the clustering engine and autonomously executing replication based on configured policies, eliminating manual operations while maintaining reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a feedback loop where the replication agent continuously receives status information about application state and node configuration from the clustering engine. This feedback mechanism enables the agent to dynamically adjust replication actions, ensuring files are synchronized only when and where needed, thus improving productivity without compromising application availability.

Inventive Principle:
Principle #23Feedback

2Productivity

If automated replication is implemented, then productivity increases and downtime reduces, but device complexity increases

Engineering Contradiction:
Improvefile replication efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The replication agent serves as an intermediary component between the clustering engine and the file system. It receives status information from the clustering engine through a well-defined interface and manages file replication independently, thereby automating productivity-enhancing tasks without significantly increasing overall system complexity. The agent acts as a specialized mediator that handles replication logic separately from core clustering functions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If frequent replication is performed, then data consistency improves, but use of energy and network resources increases

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork and computational resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The replication frequency and timing are dynamically adjusted based on actual application state changes rather than following a fixed schedule. The replication agent monitors application activity and triggers replication only when state changes occur, ensuring data consistency is maintained while minimizing unnecessary network traffic and resource consumption during periods of no change.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7320088B1System and method to automate replication in a clustered environment
Publication Date: 2008.01.15 COHESITY INC
  • US7320088B1 patent drawing
  • US7320088B1 patent drawing
  • US7320088B1 patent drawing

AI summary

Replication of application files in a clustered environment may be automated based on the state and/or configuration of the application in the cluster. A clustering engine executing on one or more clustered computing nodes may notify one or more replication agents regarding changes in a clustered application's state and/or configuration. An application's status may include information indicating one or more cluster nodes on which the application is currently executing and also may include information indicating one or more cluster nodes on which the application is configured to execute. Replication agents executing on cluster nodes may, either individually or through collective coordination, modify a replication policy for replicating one or more application files based on the received status information. Subsequently, the replication agents may replicate the application files from one of the clustered computing nodes to one or more other nodes, according to the modified replication policy.