Distributed File Server Failover and Failback via Continuous Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Disaster recovery for distributed file servers often involves lengthy failover processes from snapshots, taking hours to configure backup sites, which disrupts service continuity.
Innovation Solution
Implementing a file server manager that enables rapid failover by updating a destination distributed file server based on a snapshot while the source server continues serving requests, and configuring the destination server to handle read and write requests, with client requests redirected through active directory updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional snapshot-based failover is used for distributed file servers, then data backup is achieved, but failover time becomes excessively long (hours or more)
Solution Approach 1:
The patent applies preliminary action by continuously replicating data from the source file server to the destination file server before any disaster occurs. This ongoing replication ensures that the destination server is always ready with up-to-date data, eliminating the need for time-consuming snapshot restoration during failover. The replication process runs in the background, so when failover is needed, the destination server can immediately take over.
Solution Approach 2:
The patent uses copying by maintaining a continuous replica of the file server data on a separate destination server. Instead of creating snapshots periodically, the system continuously copies data changes from the source to the destination, creating an always-updated copy that can immediately serve clients when the source fails.
2Productivity
If continuous data replication is implemented to reduce failover time, then service continuity is improved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary file server manager that coordinates the replication process between source and destination servers. This manager handles the complexity of continuous replication, data synchronization, and failover orchestration, allowing the actual file servers to focus on their primary function of serving client requests. The intermediary absorbs the system complexity while enabling service continuity.
Solution Approach 2:
The patent merges the replication function with the existing file server infrastructure by having the file server manager oversee both the source and destination servers. Instead of adding completely separate replication systems, the solution integrates data copying into the existing file server operations, combining backup and primary functions into a unified system.
3Reliability
If the destination file server is configured to handle requests during replication, then failover readiness is achieved, but the source server performance may be impacted
Solution Approach 1:
The patent segments the file server functionality by separating the primary data serving role (source server) from the backup readiness role (destination server). The source server focuses exclusively on handling client requests and maintaining current data, while the destination server handles replication and failover preparation. This segmentation prevents performance impact on the source server.
Solution Approach 2:
The patent maintains continuity of useful action by having the source server continuously serve client requests without interruption while simultaneously undergoing data replication. The replication process occurs in the background without stopping or degrading the source server's primary function of handling client file operations.
Data Source
AI summary
An example file server manager updates a selected share of a destination distributed file server based on a snapshot of at least a portion of a selected share of a source distributed file server. The selected share of the destination distributed file server is updated while the source distributed file server serves client requests for storage items of the selected share of the source distributed file server. The file server manager receives a request to failover from the source distributed file server to the destination distributed file server and configures the destination distributed file server to service read and write requests for storage items of the selected share of the destination distributed file server. The file server manager further redirects client requests for storage items of the selected share of the source distributed file server to the destination distributed file server by updating active directory information.