- Veeam Support Knowledge Base
- Backup job fails with “The request is not supported. Failed to duplicate extent” message.
Backup job fails with “The request is not supported. Failed to duplicate extent” message.
| KB ID: | 2243 |
| Product: | Veeam Backup & Replication | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2017-02-10 |
| Last Modified: | 2025-01-22 |
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
A backup job targetted at an ReFS 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: zz
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: zz
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: zz
Cause
This error can occur when there is a discrepancy between the ReFS cluster size that Veeam Backup & Replication (VBR) recorded during repository creation and the actual cluster size. For example, if the ReFS volume was initially formatted with a 4K cluster size when the repository was created within VBR, and then the ReFS volume was subsequently reformatted to a 64K cluster size, VBR would still assume the ReFS volume was formatted with a 4K cluster size. This incongruity between the last known cluster size and the actual cluster size causes Synthetic Full creation and Forever-Forward Incremental retention merges to fail.
Solution
To resolve this issue, you can force Veeam Backup & Replication to recognize the change in cluster size by following these steps:
- Identify the repository associated with the failing job.
- Edit that repository.
- Click Finish, and an infrastructure item update will occur.
- After completing these steps, rerun the job.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
