Snapshot-Based Boot Volume Rollback for Reliable Server Reboots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The setup and maintenance of boot volumes in storage systems are complex and time-consuming, often requiring expert intervention due to enterprise-specific hardware and software configurations, and are prone to incompatibility issues and unintended corruption.
Innovation Solution
A storage system that takes and retains snapshots of boot volumes at specific milestones during the booting process, allowing rollback to a stable state using point A, B, and C snapshots to ensure reliable configuration and recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If boot volumes are frequently updated or customized for hardware/software components, then the boot volume can be adapted to specific enterprise needs, but the risk of incompatibility and corruption increases
Solution Approach 1:
The system creates snapshots of the boot volume at specific milestones (point A before OS installation, point B after OS installation, point C after component installation) before performing updates or customizations. This preliminary action preserves known good states, allowing the system to rollback if incompatibility or corruption occurs, thus enabling safe customization while maintaining reliability.
Solution Approach 2:
The patent implements a cushioning mechanism by maintaining multiple snapshot versions (point A, B, and C snapshots) that serve as safety buffers. These snapshots act as pre-prepared recovery points that protect against potential failures during boot volume updates, allowing enterprise-specific customization without compromising system stability.
2Reliability
If boot volumes are manually configured and maintained, then expert control over configuration is achieved, but the process becomes complex and time-consuming
Solution Approach 1:
The system automates the boot volume configuration process by automatically creating snapshots at defined milestones (point A, B, and C) during OS and component installation. This self-service mechanism eliminates the need for manual expert intervention while maintaining reliable configuration control, reducing both complexity and time requirements.
Solution Approach 2:
The patent implements feedback mechanisms where the system monitors the boot process and automatically creates snapshots at specific milestones. This automated feedback loop ensures proper configuration without manual intervention, reducing complexity while maintaining reliability through systematic tracking of configuration states.
3Productivity
If boot volumes are updated without rollback capability, then update speed is maintained, but the risk of unintended corruption increases
Solution Approach 1:
The system performs preliminary actions by creating snapshots at point A (before OS installation), point B (after OS installation), and point C (after component installation) before executing updates. This preliminary snapshot creation enables rapid rollback to any milestone if corruption occurs, maintaining update speed while reducing corruption risk through pre-prepared recovery points.
Solution Approach 2:
The patent changes the state parameter of the boot volume by creating discrete snapshot versions at different milestones. This parameter change approach allows the system to quickly switch between different boot volume states (A, B, or C snapshots) without time-consuming reconstruction, maintaining productivity while enabling reliable recovery from corruption.
Data Source
AI summary
A storage processing unit (SPU), which may be resident in a server in a storage system, provides a boot volume to the server and provides storage services. The SPU may execute a process including taking three snapshots of the boot volume respectively after writing an operating system image into the boot volume, after writing component images or otherwise customizing contents of the boot volume, and after the server boots from the boot volume. For updates, stability, or recovery of the storage system, the SPU may promote any of the snapshots to be the boot volume before the server reboots.