Server Data Migration Without Service Interruption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data migration methods between servers either risk data inconsistency or service interruption, as they either occur without interrupting the service and lead to data loss or require shutting down the service, causing inconvenience to users.
Innovation Solution
A data transmission method and server device configuration that temporarily blocks user requests during data migration, allowing seamless transfer of user data from one server to another without shutting down the service, ensuring data consistency and continuous service availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If data migration is performed without interrupting service, then service continuity is maintained, but data consistency and reliability deteriorate due to potential data loss or inconsistency
Solution Approach 1:
The system performs preliminary actions by creating a copy of the data migration task and blocking service requests before actual data migration begins. The authentication server receives a service blocking request, identifies the user terminal, and blocks its requests to prevent data changes during migration, ensuring data consistency while maintaining overall service continuity for other users.
Solution Approach 2:
The data migration process is segmented into multiple independent tasks. When a data migration task is being executed, the system creates a copy of the task and selectively blocks only the specific user terminal undergoing migration, while allowing other user terminals to continue accessing services. This segmentation isolates the impact to individual users rather than affecting the entire system.
2Reliability
If service is interrupted during data migration, then data consistency is ensured, but service availability deteriorates causing user inconvenience
Solution Approach 1:
The service blocking is applied locally and selectively only to the specific user terminal whose data is being migrated, rather than globally to all users. The authentication server identifies the target user terminal and blocks requests only from that terminal, while other user terminals continue to access services normally. This local application of the blocking mechanism maintains data consistency for the migrating user without affecting service availability for others.
3Loss of information
If service blocking is implemented during data migration, then data loss is prevented, but migration time increases due to service interruption
Solution Approach 1:
The service blocking is implemented as a preliminary action before data migration begins, rather than during or after the migration process. By blocking service requests in advance, the system prevents any data changes that could lead to inconsistency or loss during migration, eliminating the need for repeated migration attempts or validation retries that would extend migration time.
Solution Approach 2:
The system creates a copy of the data migration task to manage the migration process efficiently. When a data migration task is being executed, a copy of the task is created and used to selectively block service requests for the specific user terminal, allowing the migration to proceed without interruption while preventing data changes that could cause loss.
Data Source
AI summary
According to various embodiments of the disclosure, a server device may include a memory, a communication interface, and a processor. The processor may be configured to transmit a service blocking request for a specified user, to an authentication server processing a request of a user terminal, to receive user data for the user from a first server, to transmit the user data to a second server, and to notify the authentication server that the transmission is completed, when the transmission of the user data is completed.