On-the-fly Server Migration via Partial OS Image Restoration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional server restoration methods are time-consuming and result in significant downtime, as they require transferring large amounts of data from backup storage to the server, which can take hours and disrupt mission-critical applications, especially in e-commerce environments where customer attention span is short.
Innovation Solution
A system and method for on-the-fly server restoration using a data block-level backup approach, where an image of the server's storage device is created and used to partially restore the operating system on a secondary server, allowing the server to function while the rest of the data is transferred incrementally, utilizing a dedicated driver to manage disk access and prioritize sector restoration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is copied from backup storage to server storage before server restart, then data integrity is ensured, but server downtime increases significantly
Solution Approach 1:
The system creates and stores a complete image of the storage device in backup storage before any failure occurs. This preliminary action ensures that when restoration is needed, the data is already prepared and can be transferred immediately, reducing server downtime while maintaining data integrity through the pre-prepared bootable image.
Solution Approach 2:
The restoration process is segmented into two phases: first, transfer and execute only the critical boot loader and operating system kernel from the backup image to enable immediate server startup; second, continue transferring the remaining data in the background. This segmentation allows the server to become operational with minimal downtime while ensuring complete data restoration.
2Reliability
If entire storage device image is transferred from backup before server startup, then complete system restoration is achieved, but network bandwidth is overloaded and transfer time increases
Solution Approach 1:
The system performs partial action by transferring only the essential portions of the storage device image (boot loader and operating system kernel) required for server startup before the server begins operation. The remaining data transfer continues in the background, allowing the server to become functional without waiting for complete data restoration, thus reducing transfer time while maintaining restoration completeness.
Solution Approach 2:
The data transfer process continues uninterrupted in the background after the server has started up. This continuity ensures that all remaining data is eventually restored without halting server operations, achieving complete system restoration while minimizing the impact on network bandwidth and transfer time.
3Reliability
If server is shut down for restoration, then data consistency is maintained, but service availability is lost
Solution Approach 1:
The system prepares a complete and consistent image of the storage device in backup storage before any failure occurs. This preliminary action ensures data consistency is already established in the backup image, allowing the server to be restored without shutting down, thereby maintaining service availability while preserving data consistency through the pre-prepared image.
Solution Approach 2:
The restoration process transitions from a static, shutdown-based approach to a dynamic, runtime approach where the server remains operational. The system dynamically transfers and executes critical boot components during server operation, allowing continuous service availability while maintaining data consistency through controlled background restoration processes.
Data Source
AI summary
A system, method and computer program product for migrating a server include creating an image of a storage device of a first server; during execution of a boot loader on a second server, starting an initialization application that at least partially restores, to a storage device of the second server, operating system data from the image; analyzing a hardware configuration of the second server; modifying at least one driver of an operating system based on the analyzed hardware to enable the operating system of the second server to interface to the storage device of the second server; rebooting the second server using the at least partially restored operating system data; and restoring unaltered portions of remaining data from the image. The second server identification and/or authentication data stored on the image is updated before the rebooting. Identification data of the second server is at least partially replaced with corresponding data stored on the image. The image is unchanged until completion of the restoring step. The restoring is performed over a network. The image is created on the computing system connected to the server over a network. More than one storage device is restored from the image. The restoration step uses an incremental image of the storage device. A boot loader is started in case of failure of the first server.