OS Restore Interceptor for Simultaneous Loading and Archival Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for loading an operating system (OS) are slow because data is restored from an image and an archive simultaneously, leading to inefficiencies in read and write operations during the restoration process.

Innovation Solution

A method and system that intercepts read and write requests during OS loading, checks if data is already restored, and if not, retrieves it from a cache or archive, optimizing data access and reducing the need for simultaneous restoration and loading.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is restored from an image and archive simultaneously during OS loading, then the restoration process can be completed, but the OS loading speed becomes slow due to lost time in read and write operations

Engineering Contradiction:
Improverestoration completionVSAvoidOS loading speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system performs preliminary actions by checking whether data has already been restored before attempting to read it during OS loading. This prevents redundant restoration operations and allows the OS to be launched faster while restoration continues in the background

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An interceptor module is introduced as an intermediary between the OS loading process and the data volume. This interceptor checks restoration status and manages read requests, coordinating between the loading OS and restoration process to avoid conflicts and improve speed

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is read from archive and written to volume simultaneously for each read request, then data restoration is performed, but time is lost for both network download and write operations

Engineering Contradiction:
Improvedata restorationVSAvoidtime for read and write operations
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system checks in advance whether data has already been restored to the volume before initiating read operations. This preliminary check prevents redundant restoration and write operations, eliminating lost time for both network download and write operations

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system serves itself by maintaining knowledge of restoration status through the interceptor's tracking. When the OS needs data, the interceptor can determine whether restoration has already occurred, allowing the system to avoid unnecessary restoration operations and proceed directly to reading existing data

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10095589B2System and method for optimization of operating system restore
Publication Date: 2018.10.09 ACRONIS INT
  • US10095589B2 patent drawing
  • US10095589B2 patent drawing
  • US10095589B2 patent drawing

AI summary

A method and system is provided for optimization of restoration and loading of an operating system of a computer. An exemplary method includes initiating a loading of the operating system of the computer and intercepting a read request of data of a data volume from the operating system. Furthermore, the method includes determining whether the data has previously been restored during the loading of the operating system, and, if the data has previously been restored, performing the read request and returning to the loading of the operating system of the computer. Alternatively, if the data has not previously been restored, determining whether the data is stored in cache of the computer. If the data is not be stored in the cache, the method includes reading the data from a data archive and storing the data read from the data archive to the cache.