NAS File System Failover for Autonomous Corruption Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional storage systems fail to automatically detect and recover from file system unavailability or corruption, requiring manual intervention which can significantly impact system availability and violate availability goals.

Innovation Solution

Implementing an auto-recovery manager that monitors file system health and automatically performs failover to a replicated NAS server when a failure is detected, ensuring seamless routing of I/O requests to a standby server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual intervention is used to detect and recover from file system failures, then system complexity is reduced, but system availability and recovery time deteriorate

Engineering Contradiction:
Improvesystem availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service through automated failure detection and recovery mechanisms. The file system monitoring component continuously checks file system health status, and when failures are detected, the system automatically performs recovery operations including switching to backup file systems and restoring data, eliminating the need for manual intervention while maintaining high availability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system prepares recovery resources in advance by maintaining backup file systems and pre-configuring recovery procedures. When a file system failure occurs, the pre-prepared backup systems can immediately take over, and the recovery process follows predetermined steps, enabling rapid recovery without complex real-time decision-making

Inventive Principle:
Principle #10Preliminary action

2Productivity

If manual recovery procedures are implemented, then automation level is reduced, but recovery time increases from seconds to minutes

Engineering Contradiction:
Improverecovery speedVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The system performs self-diagnosis and self-recovery through automated monitoring and execution of recovery procedures. The file system monitoring component detects failures automatically, and the system executes pre-configured recovery actions including switching to backup systems and restoring data without human intervention, achieving rapid recovery in seconds

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback loops where the file system monitoring component constantly checks the health status of file systems, and when failures are detected, the feedback triggers automatic recovery actions. This closed-loop control enables rapid detection and response to failures, significantly improving recovery speed

Inventive Principle:
Principle #23Feedback

3Reliability

If replicated NAS servers are maintained for failover capability, then system reliability is improved, but device complexity and resource requirements increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidsystem configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system creates replicated copies of NAS servers and file systems that can serve as backups for failover. These replicas are maintained in a simplified manner using automated replication processes, reducing the complexity of managing redundant systems while ensuring availability for rapid failover when primary systems fail

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12493536B2Autonomous system to detect and address file system unavailability or corruption
Publication Date: 2025.12.09 DELL PROD LP
  • US12493536B2 patent drawing
  • US12493536B2 patent drawing
  • US12493536B2 patent drawing

AI summary

A method for use in a storage system, comprising: generating a replication configuration list for a first guest operating system, the replication configuration list identifying each of a plurality of Network Attached Storage (NAS) servers that are executed in the first guest operating system; detecting a file system failure event that is associated with a failed file system, the failed file system being associated with a data volume, the failed file system being provided by a first NAS server; identifying a file system identifier that is associated with the failed file system; detecting whether the first NAS server is replicated based on the replication configuration list; and in response to detecting that the first NAS server is replicated, performing a failover for the data volume to a second NAS server that is arranged to provide a file system for a replica of the data volume.