Cluster Shared Volume Backup via Snapshot Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current snapshot techniques are unable to accommodate the scaling of large-scale cluster environments with increasing numbers of nodes, virtual machines, and volumes, leading to challenges in data backup without disrupting mission-critical production tasks.

Innovation Solution

Implementing a system that uses multiple snapshots to backup large distributed environments, where virtual machines are grouped by cluster shared volumes, and each group is assigned to backup proxy nodes for parallel snapshot creation and rollover, allowing for efficient data backup across multiple snapshots.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current snapshot techniques are used for data backup, then backup can be performed with minimal disruption to production tasks, but the technique cannot accommodate the scaling of large-scale cluster environments with increasing numbers of nodes, virtual machines, and volumes

Engineering Contradiction:
Improvescalability to large-scale cluster environmentsVSAvoidbackup capability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent divides the large-scale cluster backup task into multiple segments by creating multiple snapshots instead of relying on a single snapshot. Each snapshot captures a portion of the cluster data, allowing the system to scale to accommodate increasing numbers of nodes, virtual machines, and volumes while maintaining reliable backup capability through distributed snapshot management

Inventive Principle:
Principle #1Segmentation

2Productivity

If the cluster size is increased to handle increased processing workloads, then performance and availability improve, but the complexity of performing backups without downtime increases

Engineering Contradiction:
Improveprocessing workload capacityVSAvoidbackup process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The backup process is segmented into multiple independent snapshot operations that can be managed separately. This segmentation reduces the overall complexity of backing up large clusters by breaking down the monolithic backup task into manageable units, each handling a specific portion of the cluster data

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple snapshots are created in advance before the backup process begins, capturing the state of cluster data at different points in time. This preliminary action allows the backup system to prepare backup copies without interrupting production workloads, thereby managing complexity while maintaining high productivity

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If a single snapshot is used for backup, then the backup process is simple, but it cannot handle large-scale cluster environments effectively

Engineering Contradiction:
Improvebackup process simplicityVSAvoidcapability to handle large-scale clusters
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent merges multiple snapshot operations into a coordinated backup process. By combining several snapshots that each capture portions of the cluster data, the system achieves the adaptability needed for large-scale environments while managing complexity through the unified coordination of these merged snapshot operations

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10860427B1Data protection in a large-scale cluster environment
Publication Date: 2020.12.08 EMC IP HLDG CO LLC
  • US10860427B1 patent drawing
  • US10860427B1 patent drawing
  • US10860427B1 patent drawing

AI summary

A cluster includes cluster shared volumes and nodes. A subset of the nodes are designated as being backup proxy nodes responsible for backing up the cluster shared volumes. The cluster shared volumes are divided into groups, each group having a number of cluster shared volumes that is less than a total number of cluster shared volumes in the cluster. Generation is initiated for a particular snapshot for a number of cluster shared volumes belonging to a particular group. The backup proxy nodes backup data from the particular cluster shared volumes belong to the particular group using the particular snapshot. After the backup, the steps initiating snapshot generation and backing up are repeated until each group of cluster shared volumes has been backed up.