| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:ddpbackup._DEDUP_CONTAINER_EXTENT |
DEDUP_CONTAINER_EXTENT (ddpbackup.h) |
A logical container file may be stored in a single segment or multiple segments in the backup store. |
|
dedup\dedup_container_extent.htm |
dedup |
D7CEC0C4-0472-467C-87F1-1496C9F08296 |
12/05/2018 |
DEDUP_CONTAINER_EXTENT, DEDUP_CONTAINER_EXTENT structure [Data Deduplication API], PDEDUP_CONTAINER_EXTENT, PDEDUP_CONTAINER_EXTENT structure pointer [Data Deduplication API], ddpbackup/DEDUP_CONTAINER_EXTENT, ddpbackup/PDEDUP_CONTAINER_EXTENT, dedup.dedup_container_extent |
ddpbackup.h |
Windows |
None supported |
Windows Server 2012 |
DdpBackup.idl |
Windows |
DEDUP_CONTAINER_EXTENT |
19H1 |
|
|
|
|
|
|
A logical container file may be stored in a single segment or multiple segments in the backup store. DEDUP_CONTAINER_EXTENT represents a single extent of a specific container file as stored in the backup store. The extent may be the full container file or a portion of the file.
The index in the container list passed to IDedupReadFileCallback::OrderContainersRestore to which this container extent structure corresponds.
Offset, in bytes, from the beginning of the container to the beginning of the extent.
Length, in bytes, of the extent.
For example, in an incremental backup scheme, the container may reside in the store either as one complete file generated in a full backup, or as multiple incremental files that contain changes in the file since the previous backup.