1-800-691-1991 | 9am - 8pm ET
EN

Backup Copy "Source backup file has different block size."

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: 2021-05-21

Challenge

The issue described in this KB Article only occurs when a Backup Copy job is using the Periodic copy (pruning) mode.

During consecutive Backup Copy intervals, the same machine or group of machines fails to be processed. The message "Initial copy did not complete, and will resume on the next copy interval" appears in the job report. When the job statistics are reviewed and the individual machine(s) clicked on, the following message is seen:

Source backup file has different block size. Expected block size: 1024, actual: ([backup name: <sourcebackupjobname>, block size: 512])  
error is shown in screenshot of Veeam Backup & Replication gui
Note: The expected block size and actual can be any of the following values depending on configuration: 256, 512, 1024, 4096, or 8192
Expand for More Information about Identifying this status message
The screenshots in this section show what appears when an individual machine is clicked on in the Statistics view.
During a Backup Copy interval, if the source Backup Job creates a new restore point, the Backup Copy job will detect that new restore point. If the block size does not match the expected block size, the block size message below occurs.
error is shown in screenshot of Veeam Backup & Replication gui
However, if during the Backup Copy interval, the Backup Job does not create a new restore point, the block size mismatch message will not occur, and only the "No up-to-date restore points available" message will appear.
alternate possible out come where the source job doesn't create a new restore point
This difference in error messages occurs because the Backup Copy job detects the source restore points using a different block size and adds them to a list of restore points to be skipped from future searches. During the next interval, the Backup Copy job knows to skip those previous mismatched block size points from its search for new restore points. If no new source restore point is created during the sync interval, no warning about block size is shown.

Cause

The issue occurs when the block size that the Backup Copy job expects does not match the actual block size of the restore points created by the source Backup job(s).

As documented in the User Guide:

A backup copy job does not copy a restore point if its data block size differs from the data block size of restore points that the job has already copied to the target backup repository. To copy restore points with the changed block size, you need to create active full backups. For details, see Change Storage Optimization Settings for Backup Copy Job.

For example, if you have changed the block size for restore points in the source backup job (the Storage optimization option in the Storage Settings), Veeam Backup & Replication will not copy newly created restore points and will display the Restore point is located in backup file with different block size message.

 

Solution

Below are two of the most common scenarios for this issue, (1) when all machines in the Backup Copy job are failing to process and (2) when only a portion of the machines in a Backup Copy job are failing to process.

Two solutions for each scenario are provided. One of them details how to bring the Backup job's restore points in line with what the Backup Copy job is expecting, the other details how to force the Backup Copy job to adapt to the new block size.

1.) If all of the machines in the Backup Copy job are displaying the message "Restore point is located in backup file with different block size" it is likely that the Storage Optimization setting of the source Backup Job has been changed. To resolve this, either:

  1. Force the Backup Copy job to create a new Active Full so that it can begin a new chain with the new block size used by the source Backup Job.

    or

  2. Change the source Backup Job's Storage Optimization setting to one which aligns with what the Backup Copy is expecting. Then, force the Backup Job to create a new Active Full.

2.) If only a portion of the machines being processed by the Backup Copy job are displaying the "Restore point is located in backup file with different block size" message, the Backup Copy job likely has multiple source Backup Jobs, and one of those jobs is not using the same Storage Optimization setting as the other jobs that are in the Backup Copy job. To resolve this, make sure all the Backup Jobs used by the Backup Copy job have the same Storage Optimization Setting. Either by:

  1. Reviewing all associated Backup Jobs and changing the Backup Job's Storage Optimization settings to match what the backup is expecting. An Active Full must be run on any Backup jobs where the Storage Optimization was changed to force the job to create a new backup chain with the new block size.

    or

  2. Create a separate Backup Copy job to handle the source jobs that have a different block size.

Edge Case Example

  • Per-VM is enabled on the Backup Job repository.
  • The Storage Optimization setting has been changed in that Backup Job.
  • VM(s) are added to that job after the Storage Optimization was changed.
  • Job has not run an Active Full since the change.

The existing restore points will not have changed their block size because an Active Full has not been created. The restore points created for the new VM(s) will have the new block size. When the Backup Copy job uses that Backup job as a source runs, it will display the block size message for only the newly added VM(s).

In this situation, the solution will be to either:

  1.  Force the Backup job to create an Active Full. When that completes, force the Backup Copy job to perform an Active Full. This will force both the source and target to adopt the new block size.

    or

  2. Change the Storage Optimization setting in the Backup job to match what the Backup Copy job is expecting, and then force the Backup job to perform an Active Full so that all VM(s) in the job will start a new chain using the block size that aligns with the Backup Copy.

More information

Click here to learn more about how a Backup Copy job selects which restore points to copy from a Backup job.
When this issue occurs the HTML job report that is sent via email will have a warning every day on the same machine(s), stating "Initial copy did not complete, and will resume on the next copy interval." The email will not contain the message about block sizes, which may mask the issue. The backup admin will need to review the individual VMs to identify why the "Initial copy did not complete."
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: 2021-05-21

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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

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 try again later.