https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMjQ1IiwiaGFzaCI6ImZhNTAwM2MyLWQ4Y2ItNGJiOS1hZTM4LWI5NmYxMjg0MzE1MCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Job fails with an error "The request is not supported. Failed to duplicate extent"

Challenge

After reformatting the Resilient File System (ReFS) volume at 64k cluster size Veeam fails to build Synthetic Full or Grandfather-Father-Son (GFS) restore points while incremental restore points created just fine:

Synthetic full backup creation failed Error: Agent: Failed to process method {Transform.CompileFIB}: The request is not supported. Failed to duplicate extent. Target file: <Backup repository name>\<Backup job>.vbk, Source file:<Backup repository name>\<Backup job>.vib, TgtOffset: 4091998, SrcOffset: 41019571928, DataSize: 42

Cause

Veeam B&R does not detect updated cluster size automatically.

Solution

Please go to the Backup Repository tab, right-click on the repository -> Properties and  go through the wizard to the end. Once it's done the cluster size will be updated in Veeam B&R database.
KB ID:
2245
Product:
Veeam Backup & Replication
Version:
9.5
Published:
2017-02-16
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later