Application Restore Point Data Structure for Efficient System Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for backing up and restoring applications in computing systems are resource-intensive and often result in significant downtime, as they require users to manually create system images before upgrades, which can disrupt other applications and are not efficient in reversing unsuccessful installation processes.
Innovation Solution
A method for creating an application restore point by generating a data structure that stores unmodified copies of modified components and references to new components added during the installation process, allowing for efficient restoration to a previous state without disrupting other system applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a complete system image is created before installing or upgrading an application, then the system can be restored to a previous state, but significant storage resources are required and substantial downtime occurs during the backup and restoration processes
Solution Approach 1:
The patent segments the restoration process by creating separate restore points for different applications and their components. Instead of restoring a complete system image, the system creates targeted restore points that contain only the necessary components for restoring a specific application to its previous state, significantly reducing restoration time and resource requirements.
Solution Approach 2:
The patent implements preliminary action by creating restore points automatically during the installation process itself. The system captures the state of application components before modification and stores this information in a restore point data structure, enabling rapid restoration without requiring a separate backup phase that would cause downtime.
2Reliability
If a complete system image is created before installing or upgrading an application, then the system can be restored to a previous state, but significant storage resources are required
Solution Approach 1:
The patent extracts only the essential components needed for restoration from the complete system image concept. The restore point data structure stores only the application's executable files, dynamic link libraries, and other directly related components, excluding unrelated system files and applications, thereby minimizing storage resource requirements while maintaining restoration capability.
Solution Approach 2:
The system segments the storage requirements by creating application-specific restore points rather than system-wide images. Each restore point contains only the components necessary for that particular application, allowing selective restoration and efficient use of storage resources.
3Adaptability or versatility
If an application upgrade is installed, then the application functionality is improved, but other system applications may be affected or disrupted
Solution Approach 1:
The patent implements preliminary action by creating restore points for dependent applications before installing an upgrade. The system identifies applications that depend on the upgrading application and creates restore points for them as well, enabling rollback of dependent applications if the upgrade causes system instability.
Solution Approach 2:
The system implements feedback mechanisms to monitor system stability after application upgrades. If instability is detected, the restore point data structure enables automatic or manual rollback to a previous stable state, maintaining system reliability while allowing functional improvements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques are disclosed for creating an application restore point when an application is installed or updated and for restoring the application and other elements of a computing system modified by the installation and update processes to a state as they exist at the application restore point. The application restore point captures information about which files are modified, created, or deleted by the installation and update processes. In one embodiment, a user invokes an installer process to install or update the application. When the installer process modifies or creates a file, an original copy of the file, or a reference to the file is placed into the application restore point. To restore the application, files of the computing system having original copies in the application restore point are replaced with the original copies while all new files referred to in the application restore point are deleted.