Automated Data Volume Cloning via Control Plane Snapshots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional approaches to managing data storage in cloud environments are inefficient, requiring manual intervention and resulting in downtime during data cloning or recovery processes, and are limited by the frequency of backups, which often only occur daily.
Innovation Solution
A separate control plane is introduced to manage data storage, enabling automated monitoring, cloning, and recovery through Web services, allowing for snapshot capture every 15 minutes and log data storage, which can be used to create copies of data instances without disrupting the source and recover data to a specific point in time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional approaches are used to create a copy of a data store, then a copy can be created, but the source data store must be taken offline and manual intervention is required, resulting in downtime and inefficiency
Solution Approach 1:
The patent uses snapshot technology to create point-in-time copies of data volumes without taking the source offline. The snapshot mechanism captures the state of the data volume at a specific moment and creates a readable copy that can be used for cloning operations while the original remains operational.
Solution Approach 2:
The patent introduces a control plane as an intermediary layer between the user and the data plane infrastructure. This control plane automates the cloning process by managing snapshot creation, copy operations, and resource allocation, eliminating the need for manual intervention and reducing downtime.
2Reliability
If conventional backup approaches are used, then data can be recovered, but backups occur only daily and require manual intervention, limiting recovery frequency and speed
Solution Approach 1:
The patent performs preliminary actions by continuously creating snapshots of data volumes at frequent intervals (e.g., every 15 minutes) and maintaining these snapshots in an accessible state. This preliminary snapshot creation ensures that recovery can be performed quickly by simply restoring from the most recent snapshot without needing to wait for daily backup cycles.
Solution Approach 2:
The system enables self-service recovery by automatically managing the backup and recovery processes through the control plane. Recovery operations can be initiated automatically or by users without requiring manual intervention from database administrators, and the system handles snapshot restoration, log replay, and data volume reconstruction autonomously.
3Reliability
If manual recovery processes are used, then data can be recovered from backup tapes, but the process is inefficient and requires physical presence at the data center
Solution Approach 1:
The patent replaces the mechanical process of physically handling backup tapes with an automated software-based system. The control plane manages snapshot creation, storage, and restoration through software interfaces, eliminating the need for physical tape handling, transport, and manual loading. Recovery operations can be performed remotely through web services or API calls without requiring physical presence at the data center.
4Productivity
If data volumes are cloned using conventional methods, then copies can be created, but the source data store becomes unavailable during the process
Solution Approach 1:
The patent uses snapshot-based copying that creates a point-in-time copy of the data volume without interrupting the source. The snapshot mechanism allows the source data volume to remain mounted and accessible while a separate copy is created from the snapshot, enabling cloning operations to proceed in parallel without affecting source availability.
Data Source
AI summary
Aspects of a data environment, such as the cloning, hibernation, and recovery of databases, are managed using a separate control environment. A monitoring component of the control environment can periodically communicate with the data environment to determine any necessary actions to be performed, such as to recover from faults or events for a data instance in the data environment. A workflow can be instantiated that includes tasks necessary to perform actions such as recovery, hibernation, resumption from hibernation, or backup or cloning. Tasks of the workflow can cause certain jobs to be performed by host managers in the data environment to affect calls made to the control environment.