Source backup file has different block size. Expected block size: 512, actual: ([backup name: Backup Job 1, block size: 1024])
I am getting the following error message on both my backup copy jobs. One job goes to secondary onsite storage other goes to cloud vsp.
Last week got this error thought maybe setting I changed in the jobs caused this. I reverted the settings but still, jobs would not run. I had to clear old backup files and the jobs started to run and have run correctly for the past 5 days. The one Backup job is set to do active full backups on Friday. Today Friday and both copy jobs do not copy data with this error.
Veeam B&R 9.5.4.2866 installed
Windows Server 2019
VMware 6.7
-
- Novice
- Posts: 3
- Liked: never
- Joined: Jul 21, 2017 5:04 pm
- Full Name: Nick Pozza
- Contact:
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Source backup file has different block size.
Hey Nick,
This is a bit of a nuance of Veeam Backup Copies and the process for changing the blcocksize of the backups. Backup Copies by default are Forever Forward Incremental, meaning you have a chain that has a blcocksize based on the source job.
Blocksize cannot be changed on the fly, it needs to start with an Active Full. From your error message, it sounds like someone changes the blocksize on your source job, but because the Backup Copy inherits the blocksize from the source job, the Backup Copy is confused.
You need to get both chains to be synced -- the source job won't update the backup Blocksize until an Active Full is run (I think compact full does this too). Once that matches the existing Backup Copy block size, then your job will work.
Or, just forget the Backup Copy Backups and import them independently and start "new", without deleting the points, should be fine from my experience.
This is a bit of a nuance of Veeam Backup Copies and the process for changing the blcocksize of the backups. Backup Copies by default are Forever Forward Incremental, meaning you have a chain that has a blcocksize based on the source job.
Blocksize cannot be changed on the fly, it needs to start with an Active Full. From your error message, it sounds like someone changes the blocksize on your source job, but because the Backup Copy inherits the blocksize from the source job, the Backup Copy is confused.
You need to get both chains to be synced -- the source job won't update the backup Blocksize until an Active Full is run (I think compact full does this too). Once that matches the existing Backup Copy block size, then your job will work.
Or, just forget the Backup Copy Backups and import them independently and start "new", without deleting the points, should be fine from my experience.
Who is online
Users browsing this forum: Bing [Bot], Majestic-12 [Bot], Semrush [Bot] and 60 guests