-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Source backup file has different block size
Correct, as stated above, you either need to recreate the backup copy job with the new block size or revert the block size on the original jobs and perform active full.
-
- Expert
- Posts: 194
- Liked: 18 times
- Joined: Apr 16, 2015 9:01 am
- Location: Germany / Bulgaria
- Contact:
Re: Source backup file has different block size
Thank you for the confirmation, foggy.
BTW, is there any statistical data about local vs LAN target ragarding incrementals size, deduplication ratio (I suppose deduplication will be done only in the backup copy job) and performance, especially regarding endpoint backup?
It would help to be able to make the decision if the change is worth all the work.
BTW, is there any statistical data about local vs LAN target ragarding incrementals size, deduplication ratio (I suppose deduplication will be done only in the backup copy job) and performance, especially regarding endpoint backup?
It would help to be able to make the decision if the change is worth all the work.
-
- Veeam Software
- Posts: 21075
- Liked: 2116 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Source backup file has different block size
The block size is half less for LAN target, so the size of incremental backups will also be smaller, depending on the changes pattern. In terms of performance, it will require up to double I/O, since the number of blocks will increase.
-
- Expert
- Posts: 162
- Liked: 9 times
- Joined: Jan 28, 2014 5:41 pm
- Contact:
[MERGED] Backup Copy incorrect block size
Greetings,
Here is the error I'm getting from our Backup Copy job
"Source backup file has different block size. Expected block size: 512, actual: ([backup name: <blah blah>, block size: 1024])"
I've since changed the backup job from local target (1024) to LAN (512) and let it backup a few times. However, I'm still getting the error.
What am I missing to get them back in sync?
Thanks!
Here is the error I'm getting from our Backup Copy job
"Source backup file has different block size. Expected block size: 512, actual: ([backup name: <blah blah>, block size: 1024])"
I've since changed the backup job from local target (1024) to LAN (512) and let it backup a few times. However, I'm still getting the error.
What am I missing to get them back in sync?
Thanks!
-
- Chief Product Officer
- Posts: 31607
- Liked: 6754 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Source backup file has different block size
@B.F. kindly please search for the error before creating a new topic in the future. Thanks!
-
- Enthusiast
- Posts: 82
- Liked: 11 times
- Joined: Nov 11, 2016 8:56 am
- Full Name: Oliver
- Contact:
[MERGED] Source backup file has different block size
Hey there,
i have a Backup Copy Job in my Lab-Environment where it seems that one VM-Backup can't be transferred as it is the whole time in the pending status.
The Action for this one VM in the Backup Copy Job gives me the following hint:
Source backup file has different block size. Expected block size 1024, actual: ([backup name: Backup Job name, block size: 512]).
Unfortunately i don't know what to do with these Information - is there something wrong with my Repositorys on both sides?
My Source Repository is a NTFS Dedup formatted with /L:64K and my Target-Repository is formatted with ReFS and Dedup enabled, is that a Problem? Should i rather use the same Filesystem on both sides if Dedup is used?
Many thanks
Oliver
i have a Backup Copy Job in my Lab-Environment where it seems that one VM-Backup can't be transferred as it is the whole time in the pending status.
The Action for this one VM in the Backup Copy Job gives me the following hint:
Source backup file has different block size. Expected block size 1024, actual: ([backup name: Backup Job name, block size: 512]).
Unfortunately i don't know what to do with these Information - is there something wrong with my Repositorys on both sides?
My Source Repository is a NTFS Dedup formatted with /L:64K and my Target-Repository is formatted with ReFS and Dedup enabled, is that a Problem? Should i rather use the same Filesystem on both sides if Dedup is used?
Many thanks
Oliver
-
- Product Manager
- Posts: 20285
- Liked: 2258 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Source backup file has different block size
Kindly, check the answers provided above. Thanks!
Who is online
Users browsing this forum: Google [Bot], mcz, Semrush [Bot], ysalem and 154 guests