Split Backup Agent Model for Block Storage Data Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data backup mechanisms in information handling systems are resource-intensive due to the need to transform and revert data during the backup process, especially with external block storage devices, which complicates the backup and restore operations.
Innovation Solution
A split backup agent model using the Network Data Management Protocol (NDMP) allows block devices to directly transfer data for backup without converting it back to its original form, enabling efficient backup and restore operations by separating control and data connections and specifying data format between the host and backup device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data is transformed by external block storage devices (de-duplication and compression) prior to storing on media, then storage efficiency is improved, but the backup process becomes resource intensive as the data must be returned to its original form prior to being backed up
Solution Approach 1:
The patent inverts the traditional backup approach by backing up transformed data (de-duplicated and compressed) directly without reverting to original form. The backup system accepts and stores the transformed data as-is, eliminating the computationally expensive reverse transformation step while maintaining backup functionality.
Solution Approach 2:
The system changes the parameter state of data by accepting transformed data (different physical/chemical state) as the backup source. Instead of requiring data in its original state, the system adapts to work with data that has undergone de-duplication and compression transformations, thereby avoiding the resource-intensive reversal process.
2Reliability
If a traditional backup agent is used on the host to ensure data consistency and provide restore context, then backup reliability is improved, but device complexity and proprietary software requirements increase
Solution Approach 1:
The patent extracts the backup agent functionality from the host system and relocates it to the storage device side. The host simply provides data streams without running complex backup software, while the storage device or backup infrastructure handles consistency and restore context, eliminating proprietary host agents and reducing host system complexity.
Solution Approach 2:
The system introduces an intermediary layer (NDMP protocol and storage device software) that mediates between the host's data streams and the backup infrastructure. This intermediary handles the complex tasks of ensuring data consistency and providing restore context without requiring complex software on the host itself.
3Reliability
If proprietary backup software agents are required on the host, then backup compatibility with specific vendors is ensured, but adaptability to multiple software vendors is reduced
Solution Approach 1:
The patent implements a universal backup solution using the NDMP protocol that works across multiple vendors and platforms. By moving the agent functionality to the storage device side and using a standardized protocol for control and data streams, the system achieves multi-vendor compatibility while maintaining reliable backup and restore operations.
Data Source
AI summary
A spilt backup agent model where a component on a host and a component on the block storage device function together logically to provide a backup agent. In certain embodiments, the mechanism provides a split backup agent model using a NDMP protocol. The NDMP protocol is an industry standard protocol that allows for backup of hosts with a single backup agent that is compatible with multiple independent software vendor (ISV) backup software. Thus with the present invention, proprietary backup software dependent host agents are not required. The NDMP protocol provides for separation of control and data connections where the control path runs between the data server on the host that needs to be backed up and backup software (e.g., a Data Management Application (DMA)) and between the backup device and the backup software. The data path runs between the host and the backup device.