Network Restore Points for Selective Data Restoration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional backup systems for structured data are inefficient, as they typically back up entire databases manually and time-critically, making it difficult to restore only specific lost data, and the process is labor-intensive and time-consuming.

Innovation Solution

The creation and utilization of network restore points through periodic snapshots of structured data, which can be stored on either an Internet-based or client-resident storage medium, allowing for efficient backup and restoration of specific data sets by establishing a series of snapshots that can be used when primary data is lost or corrupted, with retention policies and change thresholds managing snapshot frequency and retention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional backup systems back up entire databases manually, then data can be restored, but the process is labor-intensive and time-consuming

Engineering Contradiction:
Improvedata restoration capabilityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the database backup process by creating separate restore points for different schemas (e.g., schema1, schema2, schema3) rather than backing up the entire database as a single unit. This allows selective restoration of only the required schema, significantly reducing restoration time and manual effort while maintaining data reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and isolates specific schemas from the larger database structure for individual backup and restoration. By using schema-level restore points, the system can restore only the necessary portion of the database without requiring manual extraction from a full database backup, thus reducing both time and labor intensity.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If snapshots are taken frequently to ensure data availability, then restoration reliability improves, but storage space increases

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by maintaining different retention policies for different restore points based on their age and importance. Newer restore points are retained longer with higher redundancy, while older restore points are retained shorter periods with reduced redundancy. This differential approach ensures data availability for recent changes while conserving storage space for historical data.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements periodic snapshot creation with configurable intervals, taking snapshots at regular time intervals rather than continuously. This periodic approach balances data availability requirements with storage conservation by creating restore points only when necessary based on the defined time periods.

Inventive Principle:
Principle #19Periodic action

3Adaptability or versatility

If manual backup processes are used, then flexibility in restoration decisions is maintained, but productivity decreases

Engineering Contradiction:
Improverestoration decision flexibilityVSAvoidbackup and restoration efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements automated restore point management where the system automatically creates, manages, and maintains restore points based on predefined policies without requiring manual intervention. The automated processes include snapshot creation, retention policy enforcement, and restore point maintenance, significantly improving productivity while preserving flexibility through configurable policy options.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system incorporates feedback mechanisms where the automated backup process monitors database changes, storage capacity, and restore point age, automatically adjusting snapshot creation and retention based on these feedback signals. This maintains flexibility in response to actual system conditions while improving productivity through automation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8612391B2Creating and utilizing network restore points
Publication Date: 2013.12.17 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8612391B2 patent drawing
  • US8612391B2 patent drawing
  • US8612391B2 patent drawing

AI summary

The creation and utilization of network restore points is provided by a schema associated with a structured data set that can be conveniently backed up by periodically taking snapshots of the structured data to establish a series of restore points that can be used in the event that the primary structured data becomes lost or corrupted. In general, the snapshots are only taken after the structured data set has undergone a change in content, although they may be taken at other times as well. The snapshot may be taken by a network restore point engine that can be accessed by a user over the Internet. In addition, the snapshot may be stored on an Internet-based storage medium or it may be pushed to or pulled by the client so that the snapshot resides on a client-resident storage medium.