Deduplicating Exchange Database Attachment Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing deduplication techniques fail to effectively deduplicate attachment files associated with Exchange Database (EDB) files due to proprietary formatting and metadata interference, leading to duplicate copies being stored across backup and archive systems.

Innovation Solution

A method and system that inspect database files with embedded attachment files, generate maps to separate and reorder data blocks, and create transformed database files for deduplication across various backup formats, allowing attachment files to be deduplicated with other files on the same storage device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary formatting and metadata are maintained in Exchange Database files, then database file integrity and functionality are preserved, but attachment files cannot be effectively deduplicated across backup processes

Engineering Contradiction:
Improvedatabase file integrityVSAvoiddeduplication effectiveness
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the Exchange Database file into distinct components: attachment file data blocks and database metadata blocks. By generating a map that identifies and separates attachment data blocks from the proprietary database format, the system enables attachment files to be extracted and deduplicated independently while preserving the integrity of the remaining database structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts attachment file data blocks from within the Exchange Database file structure by inspecting the proprietary format and identifying attachment-specific data blocks. These extracted attachment blocks are then written to a separate attachment data file, allowing them to be deduplicated across multiple backup processes without affecting the database file's proprietary formatting and metadata.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If multiple backup processes store copies of attachment files, then data redundancy is created, but storage space is wasted

Engineering Contradiction:
Improvedata backup reliabilityVSAvoidstorage space utilization
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent creates an attachment data file that serves multiple backup processes universally. By extracting attachment files from different Exchange Database backups into a common attachment data file, the system enables a single copy of each attachment to serve multiple backup requirements, eliminating redundant storage while maintaining backup reliability across different processes and formats.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If attachment files are embedded within database files, then database structure is maintained, but storage redundancy increases

Engineering Contradiction:
Improvedatabase structureVSAvoidstorage redundancy
Core Design Contradiction:
Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

The patent segments the composite database file structure into separate attachment data blocks and database metadata blocks. By identifying and extracting attachment file data blocks while maintaining the map of their original positions, the system separates duplicate attachment content from the stable database structure, reducing storage redundancy without compromising database integrity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9244936B1Systems and methods for enabling deduplication of attachment files within a database
Publication Date: 2016.01.26 COHESITY INC
  • US9244936B1 patent drawing
  • US9244936B1 patent drawing
  • US9244936B1 patent drawing

AI summary

A computer-implemented method for enabling deduplication of attachment files within a database is described. A database file comprising data blocks of an attachment file positioned intermittently among data blocks of the database file is inspected. A first map may be generated from the inspection of the database file and the attachment file. The data blocks of the database file and the data blocks of the attachment file are identified according to the first map. The data blocks of the database file are written to a database data file. The data blocks of the attachment file are written to an attachment data file. The attachment data file is deduplicated with at least one other data file.