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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODM1IiwiaGFzaCI6IjU5MjM4NjExLTc5ZWUtNDU2My05M2Y4LTYzNjgzNGMyMTI2MCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Backup Copy cancels with message: ‘Restore point is located in backup file with different block size’

Challenge

A Backup Copy job terminates with the message: ‘Restore point is located in backup file with different block size’ after adding new files or linked jobs.

Cause

Veeam Backup & Replication does not copy restore points if the block size of the restore point on the source backup repository differs from the block size of restore points on the target backup repository.
 
The data block size for restore points on the target backup repository is set at the first synchronization cycle of the backup copy job. This size is taken from the corresponding settings of the primary backup job — the backup job that creates the backup chain on the source backup repository.
 
If after the first synchronization cycle you add to the backup copy job new sources that use a different data block size, Veeam Backup & Replication will detect such restore points and display the “Restore point is located in backup file with different block sizеmessage.

Solution

Version 7.x: A Backup Copy job terminates with the message: ‘Restore point is located in backup file with different block size’ after adding new files or linked jobs.
 
Version 8.0.0.807- 8.0.0.917: The Job MAY finish with a 1-time Warning;
 
“Source backup file has different block size. Expected block size: X, actual: ([backup name: Backup: ChangeBlockSizeToBCJ, block size: Y])”
 
After the above warning or without warning, Job does not process anything and eventually fails with:
 
“No up-to-date restore points available”

If the job worked previously and is now failing please review the following:


Version 9.x: The backup copy job can be run with a new active full to start a new chain in the backup copy job with the correct block size.

Older solutions below:


Step 1:
The first troubleshooting step is to change the storage optimization setting within the source backup job back to its original setting and force the source job to create a new active full. Then attempt to “sync now” with the backup copy job. If the backup copy job still fails after performing this step, proceed to step 2.

Note: If changing the storage optimization setting back to its previous value is not an option proceed to step 2.

Step 2:
If changing the storage optimization back to its previous value is not an option or it did not correct the issue, you will need to start a new backup set for the backup copy job. http://www.veeam.com/kb1885
 
If you are attempting to seed a new backup copy job or running a backup copy job for the first time and receiving this error please review the following:
 
Step 1:
Create a new backup set  with the source backup job.  http://www.veeam.com/kb1885
 
If seeding the Backup Copy job, use the new backup set to seed. If not seeding please create a new Backup Copy job.
KB ID:
1835
Product:
Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0, Veeam Backup & Replication 7.0
Published:
2013-11-19
Last Modified:
2020-11-19
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.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.