Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Overview of the Data Deduplication API technology.
To develop Data Deduplication API, you need these headers:
For programming guidance for this technology, see:
Enumerations
| DEDUP_BACKUP_SUPPORT_PARAM_TYPE Indicates whether Data Deduplication should perform an unoptimized or optimized restore. |
Functions
| OrderContainersRestore This method provides the application with the ability to influence the order of the pending reads that are required to retrieve the target file. |
| PreviewContainerRead Provides the application with a preview of the sequence of reads that are pending for a given container file extent. |
| ReadBackupFile Reads data from a Data Deduplication store metadata or container file located in the backup store. |
| RestoreFiles Reconstructs a set of files from a backup store that contains the fully optimized version of the files (reparse points) and the Data Deduplication store. |
Interfaces
| IDedupBackupSupport Provides a method for restoring a file from a backup store containing copies of Data Deduplication reparse points, metadata, and container files. |
| IDedupReadFileCallback A callback interface, implemented by backup applications, that enables Data Deduplication to read content from metadata and container files residing in a backup store and optionally improve restore efficiency. |
Structures
| DDP_FILE_EXTENT DDP_FILE_EXTENT represents the extent of data in a file that is to be read in a pending call to ReadBackupFile. |
| DEDUP_CONTAINER_EXTENT A logical container file may be stored in a single segment or multiple segments in the backup store. |