#1 Global Leader in Data Resilience

Backup job fails with “The request is not supported. Failed to duplicate extent” message.

KB ID: 2243
Product: Veeam Backup & Replication | 9.5 | 10 | 11
Published: 2017-02-10
Last Modified: 2021-02-02
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please, try again later.

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.

  1. Identify which repository is associated with the failing job.
  2. Open the [Properties] for that repository in [Backup Infrastructure]>[Backup Repositories]
  3. 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
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.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.