Snapshot Series Scheduling for Virtual Instance Data Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtual computing environments, existing technologies lack effective methods to limit data loss in the event of a virtual computing instance (VCI) failure, which is a concern for both service providers and customers.

Innovation Solution

The solution involves scheduling and managing series of snapshots for VCIs, where snapshots include metadata and incremental changes, allowing for recovery of a VCI to a specific point in time, with a recovery point objective (RPO) governing the copying of snapshots to ensure data consistency and minimize data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If snapshots are copied and stored to maintain data integrity and consistency, then data loss is limited and recovery capability is improved, but storage resources are consumed and system complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsnapshot management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the snapshot management process into distinct components: snapshot creation, snapshot copying, and snapshot storage. Each component is managed independently with specific scheduling rules, allowing complex snapshot series management to be broken down into manageable segments that can be controlled individually while maintaining overall data integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by scheduling snapshot copying operations in advance based on recovery point objectives (RPO). The system determines ahead of time when snapshots need to be copied to secondary locations to ensure data consistency, performing the copying action before potential data loss scenarios occur, thereby maintaining reliability without requiring complex real-time management.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If snapshots are copied frequently to minimize data loss, then recovery point objective is met and data protection is improved, but storage resources are consumed and operational overhead increases

Engineering Contradiction:
Improvedata protectionVSAvoidstorage resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by implementing different snapshot copying strategies for different data locations and priorities. Primary snapshots are copied to secondary locations with frequencies determined by RPO requirements, while incremental snapshots are managed differently. This localized approach ensures data protection where needed without uniformly consuming storage resources across all snapshot operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements discarding and recovering by managing snapshot retention policies that allow older or less critical snapshots to be discarded when recovery objectives are met. The system recovers only the necessary snapshot data required to meet RPO requirements, discarding redundant snapshots to optimize storage resource usage while maintaining adequate data protection.

Inventive Principle:
Principle #34Discarding and recovering

3Adaptability or versatility

If multiple series of snapshots are maintained for different recovery scenarios, then recovery flexibility is improved and various RPO requirements are met, but management complexity and storage overhead increase

Engineering Contradiction:
Improverecovery flexibilityVSAvoidsnapshot series management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by creating a multi-functional snapshot management system where a single snapshot series can serve multiple recovery scenarios. The same snapshot infrastructure supports different RPO requirements and recovery objectives through configurable scheduling parameters, rather than requiring entirely separate snapshot series for each scenario. This reduces management complexity while maintaining recovery flexibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies dynamics by making snapshot series configuration adjustable and adaptable. The system allows dynamic modification of snapshot copying schedules, retention policies, and RPO parameters based on changing recovery requirements. This dynamic approach enables the system to adapt to different recovery scenarios without requiring rigid, pre-configured separate snapshot series for each possibility.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10365976B2Scheduling and managing series of snapshots
Publication Date: 2019.07.30 VMWARE INC
  • US10365976B2 patent drawing
  • US10365976B2 patent drawing
  • US10365976B2 patent drawing

AI summary

The present disclosure is related to systems and methods for scheduling and managing series of snapshots. An example method can include estimating a transfer time to transfer a first snapshot of a virtual computing instance (VCI) to a first snapshot series, and estimating a transfer time to transfer a second snapshot of the VCI to a second snapshot series. The method can further include determining a first schedule time to start a transfer of a first series of snapshots and determining a second schedule time to start a transfer of a second series of snapshots, wherein the first schedule time and the second schedule time are based at least in part on a respective recovery point objective (RPO). In some embodiments, the method can further include scheduling a point in time to record a next snapshot based at least in part on the shorter schedule time of the first schedule time and the second schedule time.