Microsoft Exchange Mail Restoration via Virtualized Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for restoring Microsoft Exchange Server mail are inefficient and costly, as they require a full database backup, making it difficult to restore individual messages or mailboxes without restoring the entire database.

Innovation Solution

Implementing virtualization through a system filter to retrieve and restore Microsoft Exchange Server mail from a virtual copy of the database, using logs to synchronize with the real database, allowing for fast retrieval and restoration of single messages or mailboxes without mounting the database, and using de-archiving techniques to treat backed-up files as if they were on a regular hard drive.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a full database backup is performed, then all mail data is protected, but the backup process is costly and resource-intensive

Engineering Contradiction:
Improvedata protectionVSAvoidbackup cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent divides the database backup process into two levels: DB-level backup (full database backup for complete protection) and brick-level backup (individual message backup for selective restoration). This segmentation allows users to choose the appropriate backup scope, reducing unnecessary resource consumption while maintaining data protection reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables partial backup actions by allowing users to back up only specific mailboxes, folders, or individual messages (brick-level backup) rather than requiring full database backup. This partial action approach reduces backup costs and resource usage while still providing adequate protection for critical data.

Inventive Principle:
Principle #16Partial or excessive action

2Ease of operation

If a brick-level backup is performed, then individual messages can be restored, but the backup process takes several hours

Engineering Contradiction:
Improveselective restoration capabilityVSAvoidbackup duration
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent performs preliminary DB-level backup first, which is faster and covers the entire database. Then, when selective restoration is needed, it uses the pre-prepared DB-level backup combined with transaction logs to restore only specific items. This preliminary action eliminates the need for time-consuming brick-level backup while maintaining selective restoration capability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent makes the DB-level backup serve multiple functions: it provides complete data protection and also serves as the basis for selective restoration of individual messages or mailboxes. This multi-functionality eliminates the need for separate brick-level backup processes, significantly reducing backup time while maintaining both full and selective restoration capabilities.

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

3Productivity

If a DB-level backup is performed, then backup time is reduced, but restoration of individual messages is not conventionally possible

Engineering Contradiction:
Improvebackup speedVSAvoidrestoration flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent uses transaction logs as feedback mechanisms that record all changes to the database after the DB-level backup. When restoration is needed, these logs provide the necessary information to reconstruct individual messages or mailboxes from the backup, enabling selective restoration without compromising backup speed.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces transaction logs as an intermediary between the DB-level backup and the restoration process. These logs mediate by capturing database changes and enabling the reconstruction of specific messages or mailboxes from the backup, thus providing restoration flexibility without requiring slower brick-level backup processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If the entire database is restored, then all mail data is recovered, but the restoration process is costly and time-consuming

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

Solution Approach 1:

The patent segments the restoration process to allow selective restoration of individual messages, mailboxes, or folders from the DB-level backup using transaction logs. This segmentation enables users to restore only the specific data needed rather than restoring the entire database, significantly reducing restoration time while maintaining complete data recovery capability for required items.

Inventive Principle:
Principle #1Segmentation

5Adaptability or versatility

If brick-level backup is used, then selective restoration is enabled, but resource consumption increases

Engineering Contradiction:
Improveselective restorationVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent makes the DB-level backup multi-functional by using it for both complete data protection and selective restoration. Combined with transaction logs, this approach enables selective restoration of individual messages or mailboxes without requiring separate brick-level backup processes, thus reducing resource consumption while maintaining selective restoration adaptability.

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

Data Source

PatentUS10467187B1System and method for restoration of MICROSOFT exchange server mail
Publication Date: 2019.11.05 ACRONIS INT
  • US10467187B1 patent drawing
  • US10467187B1 patent drawing
  • US10467187B1 patent drawing

AI summary

A system, method and computer program product for restoration of MICROSOFT Exchange Server mail. MICROSOFT Exchange Server mail is retrieved from a virtual copy of the MICROSOFT Exchange database. Virtualization is implemented by a system filter. Logs are applied to a virtualized DB in order to synchronize it with a real DB of the MICROSOFT Exchange. The data located in the remote archive does not need to be copied into the real folder, because the data is made available by virtualization means. After the logs are applied, the virtualized DB is opened (without being mounted) from files from the virtual folder. From this point on, the DB of MICROSOFT Exchange can be viewed and the data can be queried and retrieved from the virtualized DB. Thus, a single message or a mailbox can be retrieved very fast, as if it were being retrieved from a real MICROSOFT Exchange DB.