Child Backup Applications via API for Independent Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing backup applications have inefficient dependencies, where child backup applications rely on parent backup applications for storage, leading to additional time and resource consumption in sending backup copies for storage.
Innovation Solution
Children backup applications communicate directly with parent backup applications via application program interfaces, enabling them to create and store backup copies independently on external destination nodes, with the parent backup application leveraging its own functionalities for clone creation and storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If child backup applications rely on parent backup applications for storage, then centralized control and management are achieved, but additional time and resources are consumed in sending backup copies for storage
Solution Approach 1:
The patent divides the backup system into independent child backup applications that can autonomously perform backup operations and store data directly to external destinations, rather than funneling all operations through a single parent application. This segmentation eliminates the bottleneck where child applications must send backup copies to the parent application for storage.
Solution Approach 2:
The patent introduces an intermediary communication mechanism where child backup applications communicate backup information (metadata, status, location) to the parent backup application via application program interfaces. This allows the parent application to maintain centralized control and visibility without being the sole storage destination, resolving the contradiction between centralized management and efficient storage.
2Adaptability or versatility
If child backup applications rely on parent backup applications for storage, then unified backup management is achieved, but resource consumption increases due to additional transfer operations
Solution Approach 1:
The system segments storage operations by allowing each child backup application to independently store backup copies to its own external destination nodes. This eliminates redundant data transfer operations where backup copies would be sent from child applications to the parent application and then forwarded to storage, thereby reducing resource consumption.
Solution Approach 2:
The parent backup application serves as an intermediary for management and coordination rather than as a mandatory storage intermediary. Child applications communicate backup information (metadata, status, location) to the parent application, which maintains unified backup management capabilities without requiring physical data transfer through the parent application.
3Productivity
If child backup applications store backup copies independently, then storage efficiency and speed are improved, but coordination and management complexity increases
Solution Approach 1:
The patent implements universal application program interfaces that enable standardized communication between child backup applications and the parent backup application. These interfaces handle multiple functions including status reporting, metadata exchange, and coordination tasks, allowing independent storage operations while maintaining manageable coordination through standardized protocols.
Solution Approach 2:
The system implements feedback mechanisms where child backup applications report backup information (status, location, metadata) to the parent backup application via the standardized interfaces. This feedback loop enables the parent application to track and coordinate backup operations across multiple child applications without requiring complex direct coordination between them, balancing independence with manageability.
Data Source
AI summary
Children backup applications communicating to parent backup applications via application program interfaces are described. A child backup task is executed by a child backup application. Backup information associated with an execution of the child backup task by the child backup application is communicated from the child backup application via an application program interface to a parent backup application. A parent backup task is executed by the parent backup application based on the backup information. The child backup application inherently lacks a functionality to execute the parent backup task as the parent backup application executes the parent backup task.