Volume Snapshot Restore Rollback Prevents File Corruption

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing file restore operations often result in corruption when failures occur during the restoration process, especially when using block-level backups, as only partially restored files may be left in a corrupted state.

Innovation Solution

The implementation of a snapshot mechanism that creates a point-in-time representation of the target volume, allowing files to be reverted to their original state in case of restore operation failures, ensuring data integrity and consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If block-level backup is used to restore files, then backup efficiency is improved, but file corruption risk increases when restore operation fails

Engineering Contradiction:

Improvebackup efficiencyVSAvoidfile integrity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent creates a snapshot of the target volume before initiating the restore operation. This preliminary action captures the original state of files, enabling rollback if the restore fails. The snapshot is created using copy-on-write technology, which efficiently preserves the original data without immediately copying all data blocks.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent prepares a rollback mechanism by creating a snapshot before the restore operation begins. This cushioning measure ensures that if the restore operation fails partway through, the system can revert to the pre-restore state, preventing file corruption. The snapshot serves as a safety buffer against restore failures.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If file-by-file backup is used, then file integrity is maintained, but backup time increases

Engineering Contradiction:

Improvefile integrityVSAvoidbackup time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent uses copy-on-write snapshot technology to create a point-in-time representation of the target volume. This copying mechanism preserves the original file states without requiring time-consuming file-by-file copying during the restore process. The snapshot captures the entire volume state efficiently, enabling rapid rollback if needed.

Inventive Principle:

Principle #26Copying

3Device complexity

If restore operation is performed without snapshot, then device complexity is reduced, but data loss risk increases

Engineering Contradiction:

Improvesystem complexityVSAvoiddata safety

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent introduces a snapshot as an intermediary mechanism between the restore operation and the target volume. This snapshot acts as a mediator that preserves the original state without complicating the core restore process. The snapshot is created and managed transparently, allowing the restore operation to proceed normally while providing a safety net.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8112664B2Using volume snapshots to prevent file corruption in failed restore operations

Publication Date: 2012.02.07 COHESITY INC

AI summary

Restore software executing in a computer system may invoke a snapshot of a target volume before restoring a plurality of files from a backup image to the target volume. If the restore operation fails before all the files are restored to the target volume then the restore software may use the snapshot to return one or more of the files to their original states as they existed before the restore operation was initiated.