Virtualized Application Snapshot via Layer Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup and snapshot technologies are not optimized for returning virtualized applications to a previous state, particularly in scenarios where software updates cause performance degradation or compatibility issues, and they often fail to efficiently manage read-only and read-write virtualization layers.

Innovation Solution

A snapshot module determines the difference between the read-only and read-write virtualization layers of a virtualized application to create snapshots, which can be stored and deployed to other devices, allowing users to revert the application to a previous state by activating a virtualization layer representing that snapshot.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional backup technologies are used to take snapshots of a system, then a user can return the system to a previous state, but the technology is not optimized to return a specific application to a previous state and does not efficiently manage virtualization layers

Engineering Contradiction:
Improveability to return specific application to previous stateVSAvoidcomplexity of managing virtualization layers
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the virtualization file system into distinct read-only and read-write layers. The read-only layer contains the base application state, while the read-write layer captures modifications. This segmentation enables targeted snapshots of specific applications without affecting the entire system, improving adaptability while managing complexity through clear layer separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a snapshot module as an intermediary that manages the virtualization layers and creates snapshots by capturing the state of read-write layers. This intermediary abstracts the complexity of virtualization layer management, allowing users to return specific applications to previous states without directly managing the underlying layer structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If software updates are applied to improve application functionality, then new features are added, but performance degradation or compatibility issues may occur

Engineering Contradiction:
Improveapplication functionalityVSAvoidapplication performance and compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates snapshots of the read-write layer before software updates are applied. These snapshots serve as preparatory backup states, allowing users to quickly revert if the update causes performance degradation or compatibility issues. This preliminary action preserves reliability while enabling functional updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables users to discard problematic updates by restoring from snapshots of the read-write layer. When an update causes issues, the snapshot module recovers the previous stable state by reverting the read-write layer to its snapshot state, effectively discarding the problematic changes while preserving application functionality.

Inventive Principle:
Principle #34Discarding and recovering

3Reliability

If snapshots are created frequently to ensure backup availability, then restoration capability is improved, but storage space consumption increases

Engineering Contradiction:
Improverestoration capabilityVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments snapshots into read-only and read-write components, where only the read-write layer changes are captured in each snapshot. This segmentation reduces storage requirements compared to capturing entire application states, as only the modified portions need to be stored for each snapshot while maintaining full restoration capability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8112392B1Methods and systems for creating snapshots of virtualized applications
Publication Date: 2012.02.07 CA TECH INC
  • US8112392B1 patent drawing
  • US8112392B1 patent drawing
  • US8112392B1 patent drawing

AI summary

A method may include identifying a virtualized application that has a read-only virtualization sublayer and a read-write virtualization sublayer. The read-only virtualization sublayer may represent a base state of the virtualized application and the read-write virtualization sublayer may be configured to store changes to the base state of the virtualized application. The method may also include determining a first difference between the read-only virtualization sublayer and the read-write virtualization sublayer at a first point in time and using the first difference between the read-only virtualization sublayer and the read-write virtualization sublayer to create a first snapshot that represents a state of the virtualized application at the first point in time. Various other methods, systems, and computer-readable media are also disclosed.