Snapshot Chain Malware Status for Safe VM Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems struggle with efficiently identifying and managing infected snapshots in a snapshot chain, particularly in complex virtualized environments, leading to challenges in data access, storage, and recovery.

Innovation Solution

A system and method for indicating infected snapshots in a snapshot chain using a distributed metadata store and job scheduler, which includes a distributed file system and metadata management to track and manage snapshot versions, enabling efficient identification and recovery of non-infected data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If snapshots are scanned for malware using traditional methods, then malware detection is performed, but the process is time-consuming and does not provide rapid identification of infected snapshots

Engineering Contradiction:
Improvemalware detection accuracyVSAvoidsnapshot scanning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by scanning snapshots for malware indicators during the backup process rather than after infection is suspected. The scanner identifies malware indicators in snapshots proactively, allowing the system to mark infected snapshots before they cause harm, thereby reducing detection time and improving response speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the scanner continuously monitors snapshots for malware indicators and provides real-time feedback to the metadata store. This feedback loop enables rapid identification of infected snapshots, allowing the system to update metadata about infection status dynamically without requiring time-consuming manual analysis.

Inventive Principle:
Principle #23Feedback

2Reliability

If all snapshots are scanned thoroughly for malware, then detection reliability improves, but the complexity of managing and accessing snapshot data increases

Engineering Contradiction:
Improveinfection detection reliabilityVSAvoidsnapshot chain management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts the complexity of malware scanning from the snapshot management process by using a dedicated scanner component that operates independently. The scanner analyzes snapshots for malware indicators while the metadata store manages the snapshot chains, separating the detection function from the management function and reducing overall system complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The metadata store acts as an intermediary between the scanner and the snapshot data. It maintains a structured representation of snapshot chains and stores malware indicator information, mediating between the scanning process and the actual snapshot files. This intermediary layer simplifies management by providing a centralized interface for tracking infection status without requiring direct manipulation of the snapshot chain structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If infected snapshots are not properly indicated, then data recovery options remain available, but the risk of restoring malware increases

Engineering Contradiction:
Improvedata recovery flexibilityVSAvoidmalware restoration risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system uses visual indicators (analogous to color changes) in the user interface to mark snapshots that contain malware indicators. Infected snapshots are visually distinguished from clean snapshots, allowing users to immediately identify and avoid restoring infected data while maintaining the ability to recover from unaffected snapshots in the same chain.

Inventive Principle:
Principle #32Color changes

Solution Approach 2:

The system applies preliminary anti-action by proactively identifying and marking infected snapshots before restoration operations are attempted. The scanner detects malware indicators and the metadata store records this information, preventing users from accidentally restoring malware while preserving the option to recover from clean snapshots in the same chain.

Inventive Principle:
Principle #9Preliminary anti-action

4Reliability

If comprehensive malware scanning is implemented across all snapshots, then security improves, but the speed of data recovery operations decreases

Engineering Contradiction:
Improvedata securityVSAvoiddata recovery speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs comprehensive malware scanning as a preliminary action during the backup process, so that when data recovery is needed, the infection status of snapshots is already known. This pre-scanning approach ensures security is maintained while enabling rapid recovery operations, as the system can immediately identify safe snapshots to restore without requiring time-consuming re-scanning.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250356009A1Indicating infected snapshots in a snapshot chain
Publication Date: 2025.11.20 RUBRIK INC
  • US20250356009A1 patent drawing
  • US20250356009A1 patent drawing
  • US20250356009A1 patent drawing

AI summary

Subject matter related to data management is discussed. A most recent snapshot in a snapshot chain that is not infected by malware may be identified based on mounting snapshots in the snapshot chain and determining whether the snapshots are infected. A graphical user interface showing individual snapshots in the snapshot change and indicating whether the snapshot is infected with malware may be displayed. The graphical user interface may provide a recover function for non-infected snapshots and may not enable the recover function for infected snapshots. A command to recover a non-infected snapshot in the snapshot chain may be received. Based on receiving the command, the non-infected snapshot may be recovered.