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])
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.
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:
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:
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:
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case