Incremental Cache Backup and Restore via Snapshot Quiescence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack efficient methods for managing incremental cache backup and restore, particularly in SSD-based storage systems, leading to performance degradation during cache restoration due to the absence of a coordinated cache module with backup and restore processes.

Innovation Solution

A method is introduced that quiesces I/O operations, takes snapshots of both storage and SSD cache objects, and creates a single backup image, enabling efficient incremental cache backup and restore by maintaining cache consistency and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional cache restoration methods are used, then cache can be restored from backup, but performance degradation occurs due to cache rebuild time

Engineering Contradiction:
Improvecache restoration capabilityVSAvoidI/O performance during restoration
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by quiescing I/O operations before taking snapshots and performing the backup restore process. This ensures that the cache is in a consistent state during restoration, allowing the cache to be recovered without performance degradation while maintaining data integrity. The I/O quiescence is temporarily applied only during the critical backup/restore window.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses snapshot copying technology to create point-in-time copies of the storage object and SSD cache object. Instead of traditional block-level copying, it leverages snapshot capabilities to efficiently capture the cache state, enabling rapid restoration without rebuilding the cache from scratch.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If I/O operations are quiesced during backup, then cache consistency is ensured, but system availability is reduced

Engineering Contradiction:
Improvecache consistencyVSAvoidsystem availability
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system performs preliminary I/O quiescence only for the brief duration needed to capture consistent snapshots of the storage and cache objects. This minimal interruption ensures cache consistency while maintaining high system availability, as the quiesced state is temporary and only applies during the actual backup/restore operation window.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts I/O operation state, transitioning from normal operation to quiesced state during backup, and back to normal operation afterward. This dynamic state management allows the system to maintain consistency when needed while preserving availability for the majority of operational time.

Inventive Principle:
Principle #15Dynamics

3Loss of time

If incremental backup is implemented, then backup time is reduced, but complexity of managing snapshots increases

Engineering Contradiction:
Improvebackup timeVSAvoidsnapshot management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system performs preliminary quiescence of I/O operations before capturing snapshots, ensuring that incremental backups capture only the changes made since the last backup. This approach reduces backup time by focusing only on modified data while maintaining consistency through the preliminary quiesced state.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9021222B1Managing incremental cache backup and restore
Publication Date: 2015.04.28 IOMEGA
  • US9021222B1 patent drawing
  • US9021222B1 patent drawing
  • US9021222B1 patent drawing

AI summary

A method is used for managing incremental cache backup and restore. I/O operations are quiesced at a cache module. A first snapshot of a storage object and a second snapshot of an SSD cache object are taken. The I/O operations at the cache module are unquiesced. A single backup image comprising the first snapshot and the second snapshot is created.