Cloud Volume Expansion During Backup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud backup technologies do not support volume expansion operations, requiring cloud backup to be stopped, snapshots deleted, and subsequent configuration recovery, which is cumbersome and disrupts incremental data backup.
Innovation Solution
A method and apparatus for expanding cloud volume by determining IO requests during cloud backup, expanding snapshot volumes and bitmaps, and setting preset values to enable seamless volume expansion within the backup process, ensuring data accuracy and continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Volume of stationary object
If cloud volume expansion is performed using existing technology, then the capacity of the cloud volume is increased, but the cloud backup operation must be stopped and snapshots must be deleted, resulting in cumbersome operations and disruption of incremental data backup
Solution Approach 1:
The patent applies preliminary action by creating a new snapshot before performing volume expansion. The method includes: determining whether to perform volume expansion based on expansion information; if expansion is needed, creating a new snapshot before the expansion operation; then performing the volume expansion. This ensures that snapshot data is preserved and can be used to restore backup continuity after expansion, avoiding the need to stop backup operations or delete existing snapshots.
Solution Approach 2:
The patent uses copying by creating a new snapshot that copies the state of the cloud volume at the time of expansion. This new snapshot serves as a reference point after expansion, allowing the backup system to continue incremental backups from this new baseline without losing data integrity or requiring operation interruption.
2Volume of stationary object
If cloud backup is stopped for volume expansion, then volume expansion can be performed, but incremental data backup cannot continue immediately and full backup must be performed first
Solution Approach 1:
By creating a new snapshot before volume expansion, the patent establishes a pre-expansion baseline that can be referenced after expansion. This allows the system to perform incremental backups from the new snapshot state immediately after expansion, rather than requiring a full backup, thus maintaining high backup efficiency while still achieving volume expansion.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining the snapshot chain intact through volume expansion. The new snapshot created before expansion serves as a continuous reference point, allowing incremental backup operations to continue uninterrupted after expansion, thereby preserving backup productivity without requiring full backup re-execution.
3Volume of stationary object
If snapshots are deleted for volume expansion, then expansion can proceed, but configuration recovery is required and incremental backup cannot resume
Solution Approach 1:
The patent applies preliminary action by creating a new snapshot before volume expansion instead of deleting existing snapshots. This new snapshot preserves the pre-expansion data state and serves as a reliable reference point after expansion, ensuring data backup integrity is maintained and incremental backup can resume without requiring configuration recovery or full backup re-execution.
Data Source
AI summary
A method and apparatus for expanding cloud volume, and a device and a readable medium are provided. The method includes: determining whether there is an request of a host in a cloud volume and confirming a snapshot started during cloud backup (S1); in response to there being no IO request, expanding a snapshot volume of the snapshot started during the cloud backup and the cloud volume (S2); expanding a bitmap of the snapshot started during the cloud backup, and setting a bitmap obtained by expanding as a first preset value (S3); after completion of a cloud backup task, expanding a snapshot volume of an another snapshot that is not started in the cloud backup (S4); and expanding a bitmap of the another snapshot that is not started in the the present cloud backup, and setting a bitmap obtained by expanding as a second preset value (S5).