Operational Defect Database
BugZero found this defect 2656 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2243
Backup job fails with “The request is not supported. Failed to duplicate extent” message.
Last update date:
2/2/2021
Affected products:
Veeam Backup & Replication
Affected releases:
10
Fixed releases:
No fixed releases provided.
Description:
Challenge
A backup job targetted at an ReFS 3.0 based repository fails with “The request is not supported. Failed to duplicate extent" Examples: Agent: Failed to process method {Transform.CompileFIB}: The request is not supported. Failed to duplicate extent. Target file: <path>vbk, Source file: <path>vib, TgtOffset: xx, SrcOffset: yy, DataSize: 4096 Error: Agent: Failed to process method {Transform.Patch}: The request is not supported. Failed to duplicate extent. Target file: <path>vbk, Source file: <path>vib, TgtOffset: xx, SrcOffset: yy, DataSize: 4096 Full backup file merge failed Error: Agent: Failed to process method {Transform.Patch}: The request is not supported. Failed to duplicate extent. Target file: <path>vbk, Source file: <path>vib, TgtOffset: xx, SrcOffset: yy, DataSize: 4096
Cause
The error occurs when the cluster size of the ReFS volume is changed, but Veeam Backup & Replication is not aware of the change from 4K to 64K. The job may be successful on incremental/active full runs, but fails on synthetic operations, (i.e. Synethtic Full, Forever-Forward-Incremental Merge, and Reverse Incremental).
Solution
To resolve this issue, make Veeam Backup & Replication aware of the change in cluster size since the repository was last edited. Identify which repository is associated with the failing job. Open the [Properties] for that repository in [Backup Infrastructure]>[Backup Repositories] Click [Finish] to force Veeam Backup & Replication to discover the new block size. Once completed run the job again.
More Information
For more information on "Fast Clone" and it's relation to ReFS functionality please review: https://helpcenter.veeam.com/docs/backup/vsphere/backup_repository_block_cloning.html
