SharePoint Server Configuration Synchronization for High Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Microsoft SharePoint configurations face challenges in achieving high availability due to slow and inefficient queries for updated configuration parameters, which can hinder server performance and make failover or switchover processes unsuccessful.
Innovation Solution
A system comprising a first server and a second server that cooperate to provide network-based services, where the query module dynamically determines and synchronizes the current configuration parameters of the first server with the second server, ensuring that the second server is updated with the latest parameters for seamless failover or switchover, using a query module that runs as a background process to reduce resource usage and enhance performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional SharePoint configurations are used with standard query mechanisms, then system simplicity is maintained, but query performance deteriorates and server availability is compromised
Solution Approach 1:
The system performs preliminary actions by continuously synchronizing configuration parameters from the primary server to the secondary server in advance. The secondary server maintains updated configuration parameters before failover is needed, ensuring that when switching occurs, the secondary server is already prepared with current parameters, eliminating query performance degradation during failover.
Solution Approach 2:
The patent introduces an intermediary mechanism - a configuration synchronization process that acts as a mediator between the primary and secondary servers. This intermediary continuously transfers and updates configuration parameters, allowing the secondary server to maintain current parameters without directly querying the primary server during normal operation, thus improving both reliability and query performance.
2Reliability
If the second server continuously queries the first server for updated configuration parameters, then configuration synchronization is improved, but server performance deteriorates due to resource consumption
Solution Approach 1:
Instead of continuous querying, the system implements periodic action by using event-driven notifications. The primary server notifies the secondary server only when configuration parameters change, rather than the secondary server continuously polling. This periodic notification approach maintains configuration synchronization while minimizing processor resource usage on both servers.
Solution Approach 2:
The primary server performs self-service by actively notifying the secondary server of configuration changes. Instead of the secondary server continuously querying (consuming resources), the primary server takes initiative to push updates when changes occur, reducing the resource burden on the secondary server while maintaining synchronization reliability.
Data Source
AI summary
A suite of network-based services, such as the services corresponding to Microsoft® SharePoint™, are provided to users with high availability. To maintain the availability of the services, the configuration parameters of a first server are updated on an ongoing basis, and the updated configuration parameters are used to configure a second, backup server. In the event of switchover or failover, the backup server is prepared to provide the serving functionality of the first server.