High-Availability File Server Witness for Automated Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file server systems face challenges in maintaining lossless data availability during failures, particularly in mission-critical environments, due to manual administrator intervention and potential data loss during failovers between redundant servers.

Innovation Solution

Implementing a high-availability file server capability that automatically directs file I/O requests to one of two or more synchronized servers based on their current status, using a high-availability file server witness to monitor health and synchronize data across servers, ensuring uninterrupted access and minimizing manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual administrator intervention is used for failover between redundant file servers, then system reliability is maintained through human oversight, but downtime increases and automation level decreases

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements automatic failover capability where the file server system autonomously detects failures and transitions to standby servers without requiring administrator intervention. The health monitoring component continuously checks server status and automatically initiates failover when failures are detected, eliminating manual response time while maintaining system reliability through automated oversight.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system maintains standby file servers that are pre-configured and synchronized in advance. When a primary server fails, the pre-prepared standby servers can immediately take over, reducing downtime. The synchronization mechanism continuously updates standby servers with latest data before failover is needed, ensuring data availability without manual intervention.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If synchronous replication is implemented between file servers, then data consistency is maintained across servers, but resource consumption increases

Engineering Contradiction:
Improvedata consistencyVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system implements selective synchronous replication where only critical data blocks are replicated synchronously between servers, while less critical data uses asynchronous replication. This approach maintains data consistency for essential file system operations while reducing the overall resource consumption associated with replicating all data blocks across all servers.

Inventive Principle:
Principle #3Local quality

3Productivity

If automated failover is implemented, then downtime is reduced and productivity increases, but system complexity increases

Engineering Contradiction:
ImproveavailabilityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a health monitoring component as an intermediary that centralizes the complexity of failure detection and failover coordination. This mediator component communicates with all file servers, monitors their health status, and orchestrates failover decisions, thereby automating the process while managing system complexity through a dedicated control entity rather than distributed complex logic across all servers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260089210A1Managing high-availability file servers
Publication Date: 2026.03.26 NUTANIX INC
  • US20260089210A1 patent drawing
  • US20260089210A1 patent drawing
  • US20260089210A1 patent drawing

AI summary

Methods, systems and computer program products for implementing high-availability file services in a clustered computing environment. Two or more clusters are interconnected to carry out operations for replication of file content between file servers. The file servers and their respective network links are registered with a file server witness. The file servers operate in synchrony, where each file I/O is replicated from one file server to another file server over a first set of network paths. A file server witness communicates with each file server using a second set of two or more network paths interfaced with respective file servers. The file server witness monitors the file servers to determine operational health of the file servers. Upon receipt of a file I/O request, the file I/O request is directed to one of the two file servers based at least in part on the determined operational health.