Universal Connector for NAS Backup Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing backups of large datasets stored in Network Attached Storage (NAS) face inefficiencies in bandwidth management, resource utilization, and handling of incremental backups, leading to suboptimal performance and increased costs.

Innovation Solution

The implementation of a universal connector that provides a protocol-agnostic, multi-threaded connection for managing various workloads, including large file backups, incremental backups, and bandwidth management. This connector employs batching, feedback-based operations, and parallel processing to optimize backup operations based on resource availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional backup systems are used for large datasets in NAS, then backup operations can be performed, but bandwidth management is inefficient and resource utilization is suboptimal

Engineering Contradiction:
Improvebackup operation efficiencyVSAvoidbandwidth utilization
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The backup system segments the large dataset into multiple smaller batches, processing them in parallel through multiple threads. This segmentation allows efficient utilization of network bandwidth by distributing data transfer across multiple concurrent connections, preventing any single connection from becoming a bottleneck while maintaining high overall backup productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback-based operations where backup progress, resource availability, and performance metrics are continuously monitored. Based on this feedback, the system dynamically adjusts bandwidth allocation, thread prioritization, and batch processing rates to optimize both backup efficiency and resource utilization, preventing waste while maintaining productivity.

Inventive Principle:
Principle #23Feedback

2Reliability

If incremental backups are performed without optimization, then data changes can be captured, but data generation and processing overhead increase

Engineering Contradiction:
Improvedata backup completenessVSAvoiddata volume in incremental backups
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts only the essential change information from incremental backups by analyzing file system metadata and identifying actual data modifications. By separating and processing only the changed portions rather than entire files, the system maintains complete backup reliability while significantly reducing the volume of data that needs to be processed and stored in incremental backups.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the parameter representation of backup data by using metadata-based change detection and differential encoding. Instead of backing up complete files, the system tracks and transmits only modification parameters such as file timestamps, size changes, and checksum differences, thereby maintaining data integrity while minimizing the quantity of backup data generated.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple protocols are supported for backup operations, then compatibility with diverse systems is improved, but system complexity increases

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

Solution Approach 1:

The system implements a universal connector architecture that provides multi-functional support for multiple backup protocols (NFS, SMB, CIFS, etc.) through a single unified interface. This universal connector handles protocol-specific operations internally while presenting a consistent API to users, thereby achieving broad protocol compatibility without proportionally increasing system complexity.

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

Solution Approach 2:

The universal connector acts as an intermediary layer between the backup application and various network storage protocols. It mediates protocol-specific complexities by translating diverse protocol requirements into a unified internal processing model, allowing the system to support multiple protocols while maintaining manageable complexity through abstraction and standardization.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If file system analysis is performed on large datasets, then backup ordering can be optimized, but processing time and resource usage increase

Engineering Contradiction:
Improvebackup speedVSAvoidfile system analysis time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary file system analysis during initial backup operations to establish an optimized access order and identify data patterns. By conducting this analysis upfront and caching the results, subsequent backup operations can proceed more efficiently without repeating the full analysis, thereby reducing the time penalty while maintaining high backup productivity through informed data access strategies.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12287709B2System and method for managing a backup of a large set of files using a file system analysis for data stored in a network attached storage
Publication Date: 2025.04.29 DELL PROD LP
  • US12287709B2 patent drawing
  • US12287709B2 patent drawing
  • US12287709B2 patent drawing

AI summary

A method for managing data includes obtaining, by a universal connector, a backup request for a backup of a set of files, in response to the backup request: performing a file system analysis on the set of files to determine an ordering of files to be accessed for the backup, generating a set of file read requests based on the ordering of files, sending a data access request based on the set of file read requests, obtaining a response from the NAS server, wherein the response comprises data associated with the set of files, and generating the backup using the data associated with the set of files.