Boot Volume Snapshots for Reliable Server Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise storage systems require complex and time-consuming configuration and maintenance of boot volumes due to enterprise-dependent hardware and software requirements, with frequent updates leading to incompatibilities and unreliability, and there is a need for systems that can easily and reliably set up, configure, and maintain boot volumes for servers in storage systems.
Innovation Solution
A storage system that takes, retains, and uses snapshots of boot volumes at specific milestones during the booting process, including a pristine copy after downloading the base boot image (point A), customizations (point B), and post-reboot changes (point C), allowing rollback to a stable state upon detection of issues.
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 requirements, but incompatibilities and corruption risks increase making servers inoperable
Solution Approach 1:
The patent applies preliminary action by creating snapshots of the boot volume at specific milestones (point A after base image download, point B after customizations, point C after reboot) before potential corruption can occur. These snapshots serve as pre-prepared recovery states that allow the system to rollback if customization or update processes fail, thus maintaining reliability while enabling adaptability.
Solution Approach 2:
The patent uses copying by creating duplicate copies of the boot volume at different stages (snapshots at points A, B, and C). These copies preserve the boot volume state at each milestone, allowing the system to revert to any previous state if corruption occurs during updates or customizations, thereby resolving the contradiction between adaptability and reliability.
2Reliability
If boot volumes are manually configured and maintained by experts, then proper setup and maintenance can be achieved, but configuration and maintenance become complex and time-consuming
Solution Approach 1:
The patent implements self-service by automating the boot volume management process. The system automatically captures snapshots at predefined milestones during the boot process without requiring expert intervention. This automation reduces configuration complexity while maintaining reliability, as the system performs self-monitoring and self-recovery through the snapshot mechanism.
Solution Approach 2:
The patent applies feedback by monitoring the boot process and automatically triggering snapshot creation at specific milestones. The system receives feedback from the boot process state and responds by creating appropriate snapshots, enabling automated management that reduces complexity while ensuring proper configuration and maintenance.
3Reliability
If automated snapshot management is implemented at multiple boot milestones, then boot volume corruption risk is reduced, but system complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the boot process into distinct milestones (point A, point B, point C) and creating snapshots at each segment boundary. This segmentation approach manages complexity by organizing snapshot creation into discrete, predefined events rather than continuous monitoring, reducing the overall system complexity while maintaining high reliability through comprehensive coverage of critical boot stages.
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.