FSRP Protocol Translation for Load-Balanced Cluster File Restore

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing clustering technologies in enterprise environments face challenges in efficiently managing file system data storage and restoration, particularly in failover clusters, where load balancing and data node selection for restoration are not optimally addressed, leading to potential overloading during backup and recovery processes.

Innovation Solution

Implementing an enhanced file system redirector proxy (FSRP) node that translates NFS requests into a cluster-readable protocol, allowing dynamic selection of data nodes based on load and backup type, and incorporating deduplication services to optimize storage and restoration processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional clustering technologies are used for file system data storage, then basic failover functionality is provided, but load balancing and data node selection for restoration are not optimally addressed, leading to potential overloading during backup and recovery processes

Engineering Contradiction:
Improverestoration efficiencyVSAvoidnode overloading
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically selects data nodes for restoration based on real-time load conditions and backup type. The FSRP node evaluates multiple factors including node availability, current load, and backup characteristics to determine the optimal restoration target, rather than using static node assignment. This dynamic approach prevents overloading specific nodes while maintaining high restoration efficiency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the FSRP node continuously monitors cluster node status, load conditions, and restoration progress. Based on this feedback, the system adjusts node selection decisions in real-time, preventing overloading by redirecting restoration operations to more suitable nodes when load thresholds are approached.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If protocol translation is implemented to enable NFS clients to access cluster file systems, then compatibility is improved, but system complexity increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The FSRP node serves as an intermediary between NFS clients and the cluster file system. It translates NFS protocol requests into cluster-internal protocols and manages the communication between these two different protocol environments. This intermediary approach enables protocol compatibility without requiring changes to either the NFS client stack or the core cluster architecture, thereby limiting the increase in system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The FSRP node is designed with multi-functionality, handling not only protocol translation but also load balancing, node selection, and restoration management. By consolidating these functions into a single component, the system achieves protocol compatibility while minimizing the overall architectural complexity that would result from separate dedicated components for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12566735B2Network file system server proxy and protocol translation
Publication Date: 2026.03.03 DELL PROD LP
  • US12566735B2 patent drawing
  • US12566735B2 patent drawing
  • US12566735B2 patent drawing

AI summary

One or more embodiments of the invention relates to a method of managing a file system, by using a cluster that includes an enhanced file system redirector proxy (FSRP) node and at least one namespace access node. The method may include obtaining, by the enhanced FSRP node, a request from a client, and in response to the request: performing a translation of the request to a cluster-readable format to obtain a cluster-readable request, determining a namespace access node of the cluster to service the cluster-readable request, sending the cluster-readable request to the namespace access node, obtaining confirmation of servicing of the cluster-readable request from the namespace access node, and providing a file handle to the client based on the confirmation of the servicing.