Multi-Channel Backup With Reduced Active Volumes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data backup systems are complex, costly, and require significant maintenance, with service level agreements (SLAs) being difficult to implement, especially for cloud-based implementations.
Innovation Solution
A Cloud Data Management (CDM) system with Managed Volumes (MV) and a backup agent that simplifies backup operations, supports multiple server types, and reduces active volumes to improve throughput, while providing flexible backup solutions across various environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional backup systems are implemented with multiple active volumes, then backup capacity is increased, but writing throughput decreases and system complexity increases
Solution Approach 1:
The backup system is segmented into distinct functional components: a backup agent on the host that mounts endpoints and executes backup scripts, and a CDM system that manages file system stacks and data storage. This segmentation allows the writing throughput to be optimized in the backup agent while the CDM system handles complexity management independently.
Solution Approach 2:
The patent extracts the file system stack management from the traditional backup system architecture and places it within the CDM system. This extraction allows the backup operations to proceed with simplified volume management while the CDM system independently manages the file system stack creation and termination, thereby improving writing throughput without losing necessary functionality.
2Ease of operation
If cloud-based backup implementations are used, then backup accessibility is improved, but implementation complexity and maintenance costs increase
Solution Approach 1:
The backup agent is designed to autonomously mount endpoints, execute backup scripts, and manage the backup process without requiring manual intervention or complex configuration by users. The CDM system similarly self-manages file system stack creation and termination based on backup job requirements, thereby improving ease of operation while containing implementation complexity within the system itself.
Solution Approach 2:
The CDM system is designed as a universal platform that can handle multiple backup scenarios, different file system types, and various storage configurations through a single unified interface. This multi-functionality allows cloud-based implementations to serve diverse backup needs without requiring separate complex implementations for each scenario, thereby improving ease of operation.
3Reliability
If service level agreements are implemented for backup operations, then backup reliability is improved, but system complexity and maintenance costs increase
Solution Approach 1:
The backup system incorporates feedback mechanisms where the backup agent reports backup status, completion, and errors to the CDM system, which then adjusts file system stack management accordingly. This feedback loop ensures that backup reliability is maintained through automated monitoring and response, while maintenance complexity is reduced compared to manual SLA management.
Solution Approach 2:
The system performs preliminary actions by pre-configuring file system stacks and backup endpoints before backup operations begin. The CDM system proactively manages the lifecycle of file system stacks, creating them before backup jobs start and terminating them after completion, thereby ensuring backup reliability is built-in rather than managed through complex ongoing maintenance.
Data Source
AI summary
Methods, systems, and computer programs are presented for backing up data to a distributed multichannel storage system. One method includes an operation for detecting, by a distributed backup system (DBS), a request for backing up data from a host to the distributed backup system. The DBS sends a request to a backup agent executing at the host to initiate the backup. The backup agent mounts an endpoint for writing to the DBS and executes a script that writes the data for the backup to the endpoint. Further, the method includes operations for creating a file system stack at the DBS associated with the endpoint, storing data received by the file system stack at the DBS, and detecting, by the DBS, an end of the backup. The DBS sends a command to the backup agent to end the backup and terminates the file system stack at the DBS.