Application Object Recovery via Metadata Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data recovery technologies are inefficient and costly, as they often require restoring entire systems to recover a small subset of data, and application data stored in underlying file or database systems can be difficult to restore due to format incompatibilities and changes in data structures.

Innovation Solution

The method involves obtaining application metadata to provide a user interface for selecting specific application objects to restore, using native application methods to ensure compatibility, and storing data files separately to facilitate granular restoration of application objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional backup strategies are used to restore a small subset of data, then data recovery is possible, but significant storage space, time, and cost are required due to restoration of the entire system

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidstorage space required
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent segments the backup system into two distinct components: metadata (which describes application objects and their locations) and actual data files. This segmentation allows users to restore only specific application objects by referencing metadata, rather than restoring entire systems or large portions of data, thereby significantly reducing storage space requirements while maintaining data recovery capability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and separates metadata from the bulk data storage system. The metadata contains essential information about application objects (names, types, locations, dependencies) that enables selective restoration. By taking out this critical information layer, the system allows precise recovery of only needed data subsets without requiring storage of entire system backups

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If traditional backup strategies are used to restore a small subset of data, then data recovery is possible, but significant time is required due to restoration of the entire system

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidrestoration time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

By segmenting backup operations into metadata management and data file storage, the system enables rapid restoration of specific application objects. Users can query metadata to locate desired objects and restore only those specific files, bypassing the time-consuming process of restoring entire systems while maintaining complete data recovery capability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by maintaining up-to-date metadata that pre-describes the location, structure, and dependencies of all application objects. This preliminary organization of information allows users to immediately identify and restore specific objects without time-consuming system-wide restoration processes

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If underlying files or database systems are restored to recover application data, then data can be recovered, but compatibility issues arise due to format changes and data structure updates in applications

Engineering Contradiction:
Improveapplication data recoveryVSAvoidapplication compatibility
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent introduces metadata as an intermediary layer between the application and underlying data storage systems. The metadata contains application-specific information about object formats, structures, and dependencies that enables compatibility verification during restoration. This intermediary allows the system to restore application objects while ensuring they remain compatible with current application versions, even when underlying file formats or database structures have changed

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If full point in time restoration is performed to recover application objects, then compatibility is ensured, but storage space and cost increase significantly

Engineering Contradiction:
Improveapplication compatibilityVSAvoidstorage space required
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the restoration process into selective object recovery based on metadata rather than full system restoration. Users can identify specific application objects needing restoration through metadata queries and restore only those objects with compatibility verification, avoiding the need to store and restore entire systems while maintaining reliability through metadata-guided selective restoration

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8266112B1Techniques for recovery of application level objects
Publication Date: 2012.09.11 COHESITY INC
  • US8266112B1 patent drawing
  • US8266112B1 patent drawing
  • US8266112B1 patent drawing

AI summary

Techniques for recovery of application level objects are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for restoration of one or more application level objects. The method may comprise obtaining application metadata of an application containing objects to be restored, storing one or more data files containing application data, utilizing the application metadata to provide a user interface for the restoration of one or more application objects, accepting input from a user via the user interface specifying one or more application objects to restore, and restoring the one or more specified application objects.