Web Site Restore Preserving User Customizations via GUID Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for restoring database backup copies often lose user customizations due to the use of template architectures and globally unique identifiers (GUIDs), resulting in broken links and a loss of the original look and feel of web pages during the restoration process.

Innovation Solution

A method that involves receiving a request to restore a web site from an archived database file, processing the data using a template architecture, and generating new GUID values while maintaining the original identifiers to ensure that the rebuilt database conforms to the backup copy, thereby preserving user customizations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If the intranet portal application rebuilds the database according to a template architecture and generates new GUID values, then the database conforms to the predetermined format and template structure, but user customizations are lost and links become broken

Engineering Contradiction:
Improvedatabase structure conformityVSAvoiduser customization data
Core Design Contradiction:
Manufacturing precisionVSLoss of information

Solution Approach 1:

The system performs preliminary actions by creating a complete backup of the original database including all user customizations and original GUID values before the rebuild process. This backup serves as a reference that is applied during the rebuild to preserve customizations while allowing the template architecture to establish the proper structure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses an intermediary mechanism by maintaining a mapping between original GUID values and newly generated GUID values. This mapping table acts as a mediator that translates the new template-based structure back to the original customization structure, allowing both the conformant template format and the preserved user customizations to coexist.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If new GUID values are generated during the rebuild process, then the database structure is standardized according to the template, but navigation structure and web links become broken

Engineering Contradiction:
Improvedatabase template compatibilityVSAvoidlink integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A GUID mapping table serves as an intermediary between the new template-based GUID system and the original customization-based GUID system. This mapping allows the database to use new GUIDs for template compatibility while translating references back to original GUIDs to maintain link integrity and navigation structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter representation by maintaining two sets of GUID values: original GUIDs for preserving links and customizations, and new GUIDs for template compliance. The mapping table enables dynamic parameter translation between these two representations, allowing the system to adapt to template requirements without breaking existing references.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If the database is rebuilt using a predetermined template format, then the restoration process is automated and efficient, but the look, feel, and content of web pages differ from the original

Engineering Contradiction:
Improverestoration speedVSAvoidweb page customization
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system performs preliminary backup of the complete original database state including all web page customizations, user modifications, and original GUID assignments. This preliminary action preserves the original look and feel information before the automated rebuild process begins, enabling subsequent application of these customizations to the new template structure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system merges two approaches: the automated template-based rebuild process that ensures structural integrity and compliance, and the original customization data that preserves the original look and feel. By combining these two elements through the GUID mapping mechanism, the system achieves both automation efficiency and customization preservation.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8364640B1System and method for restore of backup data
Publication Date: 2013.01.29 COHESITY INC
  • US8364640B1 patent drawing
  • US8364640B1 patent drawing
  • US8364640B1 patent drawing

AI summary

A system and method for restoring a web site previously defined with user customizations by an intranet portal application. A backup agent receives a restore request for a backed up web site. Restored data is used by the intranet portal application in order to rebuild the web site according to a predetermined template. Use of the template results in a rebuilt database which does not match the database originally backed up. For one or more identifiers being added, one or more new globally unique identifiers (GUIDs) are generated by the application to replace the identifiers. The backup agent queries the application to receive new GUIDs for a selected level of the hierarchy of the web site. The backup agent updates a mapping of IDs with the new GUIDs. The backup agent uses the mapping to identify differences between the rebuilt database and the database represented by the backup copy of the database. Based on identified differences, database operations are used to modify the rebuilt database so that it conforms to the originally backed up database.