Local Data Copy via Single API Call

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for creating local secondary copies of data stored in online repositories are time-consuming, inefficient, and error-prone, especially when dealing with large and ever-changing data sets, and they lack the capability for frequent backups.

Innovation Solution

The system employs a single API call to an online data management system to obtain a full or incremental copy of data, parses the received data to configure data files and metadata files, and transfers them to local secondary storage devices, allowing for object-level granularity and restoration of current and previous versions of documents and files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional systems are used to create local secondary copies of data from online repositories, then data backup and protection are achieved, but the process is time-consuming and inefficient

Engineering Contradiction:
Improvedata protectionVSAvoidbackup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing continuous data synchronization between online repositories and local storage devices. Data is pre-cached and prepared for rapid restoration, so when restoration is needed, the process is already substantially complete, eliminating time delays during actual restoration operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates secondary copies of data objects from online repositories and stores them locally. These copies can be restored quickly to primary storage devices, enabling rapid data recovery without needing to retrieve from slow online storage, thus resolving the time-consuming restoration problem while maintaining data protection.

Inventive Principle:
Principle #26Copying

2Reliability

If traditional systems are used to create local secondary copies of data, then data protection is achieved, but the systems are error-prone and lack efficiency

Engineering Contradiction:
Improvedata protectionVSAvoidbackup efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system employs self-healing mechanisms that automatically detect and correct errors during data synchronization and restoration processes. The storage system monitors its own operations, identifies anomalies, and performs corrective actions without external intervention, thereby maintaining high reliability and efficiency while protecting data.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements feedback mechanisms where the system continuously monitors data synchronization status, error rates, and system performance. This feedback is used to dynamically adjust synchronization parameters, retry failed operations, and optimize resource allocation, resulting in improved backup efficiency and reduced errors while maintaining robust data protection.

Inventive Principle:
Principle #23Feedback

3Reliability

If frequent backups are implemented to improve data protection, then reliability increases, but system complexity and resource consumption increase

Engineering Contradiction:
Improvedata protectionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs partial synchronization by caching only the most recently modified data objects locally rather than synchronizing entire datasets. This selective approach enables frequent backups with reduced complexity and resource consumption, as only critical or recently changed data is maintained in fast local storage, providing adequate protection without overwhelming system resources.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent segments data into different categories (frequently accessed, recently modified, archival) and applies different synchronization frequencies and storage locations to each segment. This segmentation allows frequent backups of critical data while using less frequent or lighter-weight backup strategies for less critical data, reducing overall system complexity while maintaining comprehensive data protection.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12039183B2Creating local copies of data stored in cloud-based data repositories
Publication Date: 2024.07.16 COMMVAULT SYSTEMS INC
  • US12039183B2 patent drawing
  • US12039183B2 patent drawing
  • US12039183B2 patent drawing

AI summary

Systems and methods for creating local, or on-premises, secondary copies of data managed and/or stored in online repositories are described. In some embodiments, the systems and methods perform a single application programming interface (API) call to a web application level of an online repository to transfer a copy of the data stored in the online repository from the online repository to a local site of a local information management system. Via the local site, the systems and methods access the copy of the data at the site of the local information management system, generate a metadata manifest file that associates metadata files and data files within the copy of the data of the site of the local information management system, and transfer the data files and the metadata manifest file to a media agent for storage to a secondary storage device of the local information management system.