Dual Storage OS Upgrade with Automatic Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for upgrading an operating system, such as using USB memory, lack robustness in system failure recovery and do not automatically maintain a stable upgrading procedure, leading to weak protection for the operating system after upgrades.
Innovation Solution
Implementing a dual storage system where both storage devices store system images of different versions, allowing for selective restoration in case of system abnormalities, ensuring stability by monitoring operation conditions and switching between versions as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single storage device is used to store the latest system image, then the upgrading process is simple, but the system lacks protection against failures and cannot automatically rollback to previous versions
Solution Approach 1:
The system performs preliminary actions by maintaining historical system images in the second storage device before upgrades occur. This allows the system to have backup versions ready in advance, enabling automatic rollback if needed without requiring complex real-time decision-making during failure recovery
Solution Approach 2:
The invention creates copies of system images across two different storage devices. The first storage device holds the latest system image while the second storage device maintains historical versions. This copying approach provides redundancy and protection against failures without requiring complex active monitoring systems
2Reliability
If the system automatically updates to the latest version, then the system remains current, but there is no mechanism to protect against unstable versions or automatic rollback
Solution Approach 1:
The system implements feedback mechanisms by monitoring system operation status after upgrades. The management device receives operation information from the upgraded system and can determine whether the upgrade was successful. This feedback loop enables automatic rollback to historical versions if the new version proves unstable, while maintaining automated version management
Solution Approach 2:
The system changes the parameter of version stability by maintaining multiple version states (current and historical) rather than a single state. This allows the system to switch between versions based on operational parameters, ensuring stability while maintaining automated management capabilities
3Quantity of substance
If historical system images are deleted after successful upgrade, then storage space is optimized, but the system cannot perform rollback or restoration operations
Solution Approach 1:
The invention segments the storage function into two distinct storage devices: the first storage device for the current system image and the second storage device for historical system images. This segmentation allows each storage device to be optimized for its specific purpose while maintaining the capability to restore from historical versions without compromising overall storage efficiency
Data Source
AI summary
Embodiments of the present disclosure provide a method, an electronic device, and a computer program product for managing an operating system. The method includes receiving a version upgrade request for the system. The method further includes using a target system image to upgrade the system from a first version to a second version corresponding to the target system image. The method further includes storing, in response to determining that the system operates normally within a first time period, the target system image to a first storage device for the system without updating a historical system image stored in a second storage device for the system, wherein the historical system image corresponds to the first version. In this way, by storing image files of different versions for selectively resetting the operating system in case of a failure, stability of the system after an upgrade is improved.