Volume Copying via Selective Copy-on-Write

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for copying a source logical volume to a target volume, especially for large volumes, face performance issues due to the need to suspend writes or enter copy-on-write mode, which can impact system responsiveness and require significant storage for a CoW file, leading to potential failures and resource constraints, especially when copying over slow networks like the Internet.

Innovation Solution

A method that designates blocks to be copied from a source volume to a target volume while the operating system is writing, identifies and compares the size of written blocks to a threshold, and only enters copy-on-write mode when necessary, allowing for a crash-consistent snapshot without the need for continuous copy-on-write mode, thus reducing resource usage and storage requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the operating system enters copy-on-write mode to create a crash-consistent copy, then the copy consistency is improved, but the system performance and responsiveness deteriorate due to intercepting and processing every write instruction

Engineering Contradiction:
Improvecopy consistencyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements periodic copy-on-write mode entry rather than continuous mode. The system enters copy-on-write mode only when needed to capture a crash-consistent state, performs the necessary block copying, then exits the mode. This periodic activation reduces the overhead on system performance while maintaining copy consistency when required.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system dynamically adjusts between copy-on-write mode and normal operation mode based on the copying progress and consistency requirements. The copy-on-write mode is activated only when blocks need to be captured in their original state, and deactivated when copying is complete or consistency is no longer required, making the system adaptive rather than static.

Inventive Principle:
Principle #15Dynamics

2Reliability

If copy-on-write mode is maintained throughout the entire copying process, then crash consistency is ensured, but the storage space required for the CoW file increases significantly

Engineering Contradiction:
Improvecrash consistencyVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the copying process into multiple phases, entering copy-on-write mode only for specific blocks that require consistency preservation rather than maintaining it for the entire volume. This segmentation allows the system to reduce the amount of storage space needed in the CoW file while still ensuring crash consistency for critical blocks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of applying copy-on-write protection to all blocks throughout the entire copying process, the system applies it partially only to blocks that are currently being copied or need consistency assurance. This partial action reduces the storage requirements for the CoW file while maintaining sufficient crash consistency.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the copying process is performed on large logical volumes, then complete backup is achieved, but the copying time becomes excessively long and impacts system availability

Engineering Contradiction:
Improvebackup completenessVSAvoidcopying time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary identification of blocks that require copying before actually copying them. By using copy-on-write mode selectively during this process, the system can prepare the copying operation in advance and execute it more efficiently, reducing the overall copying time for large volumes while maintaining backup completeness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables the copying process to continue without requiring the source volume to be taken offline. The copy-on-write mode allows the operating system to continue normal write operations while the copying process proceeds in the background, ensuring continuous useful action on both the source and target volumes simultaneously.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10884871B2Systems and methods for copying an operating source volume
Publication Date: 2021.01.05 DATTO LLC
  • US10884871B2 patent drawing
  • US10884871B2 patent drawing
  • US10884871B2 patent drawing

AI summary

The present disclosure is directed at systems and methods for copying a source volume to a target volume. The disclosed systems/methods facilitate copying the source volume to the target volume while an operating system is configured to write to the source volume, while ensuring that the resulting copy in the target volume represents a crash-consistent state of the source volume at a single point in time. According to some embodiments, the disclosed systems and methods reduce the amount of time that the operating system writing to the source volume spends in copy-on-write mode. The disclosed systems/methods can decrease the performance burden on the operating system (e.g., free up processing resources at the operating system for other tasks), while also decreasing the amount of memory required for the copying process.