Client-Side Backup Deduplication via Content-Based File Naming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Oracle RMAN's lack of metadata for backup streams in Oracle databases reduces deduplication capabilities, leading to higher storage costs and increased probability calls.
Innovation Solution
A client-side deduplication system that generates unique file names for backup streams based on data blocks, creating data files in a local cache with corresponding unique names, and uses a dedupe module to perform deduplication, thereby avoiding unnecessary storage and calls to the backup server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RMAN creates backup files with unique names for every backup stream, then backup identification is improved, but deduplication capability deteriorates
Solution Approach 1:
The system segments the backup identification problem into two parts: RMAN maintains unique backup stream identifiers for reliability, while the deduplication system creates separate unique file names based on data block content for deduplication purposes. This segmentation allows both unique identification and deduplication to coexist without conflict.
Solution Approach 2:
The patent introduces an intermediary layer (the deduplication system's file naming mechanism) that sits between RMAN's backup stream identification and the actual storage. This intermediary translates RMAN's unique stream identifiers into content-based unique file names, enabling deduplication while preserving backup identification integrity.
2Reliability
If RMAN does not provide metadata about datafiles in backup streams, then backup catalog uniqueness is improved, but deduplication capability deteriorates
Solution Approach 1:
The system extracts the necessary metadata (datafile information) from within the backup stream content itself, rather than relying on RMAN to provide it externally. By parsing and extracting this information directly from the backup data blocks, the system enables deduplication while maintaining catalog uniqueness.
Solution Approach 2:
The deduplication system performs self-service by autonomously extracting and processing metadata from backup streams without requiring RMAN to provide additional information. The system independently identifies datafile contents and creates appropriate unique file names, making the deduplication process self-sufficient.
3Reliability
If each backup stream appears as a new file, then backup stream identification is improved, but storage efficiency deteriorates
Solution Approach 1:
The system changes the naming parameter from time-based/stream-based identifiers to content-based identifiers. By using data block content characteristics to generate unique file names, the system maintains backup stream identification while enabling duplicate content recognition, thereby improving storage efficiency without sacrificing identification reliability.
Data Source
AI summary
A system and a method for client-side deduplication system for a plurality of backup streams, generated by a backup and recovery client from a client database, is presented. The system includes a stream handler configured to generate a unique file name for an underlying file of each backup stream of the plurality of backup streams based on one or more data blocks in each backup stream. The system further includes a file creator configured to create a data file corresponding to each backup stream of the plurality of backup streams in a local cache of a client database server, wherein each data file has a file name corresponding to the unique file name generated by the stream handler. The client-system furthermore includes a dedupe module configured to dedupe subsequent backup streams based on the data files in the local cache.