by howesh » Mon Aug 26, 2013 11:51 pm people like this post
I have one VM that is in a Backup Copy job. Every time it starts, it stops and reports "Restore point is located in backup file with different block size". It is the only VM in the job and it is a newly created Backup Job, so no data has been transferred yet. So far the job has not run successfully.
by foggy » Tue Aug 27, 2013 8:21 am people like this post
Harry, there seems to be an issue with the backup copy job: if the corresponding backup job has block size different from the default one and if VMs are added to the backup copy job from the virtual infrastructure, the job could fail with the mentioned error. To work around this, you could either temporarily disable backup copy job, remove all files it has created (via Backup node in the Veeam B&R console), and re-enable it or just re-create the backup copy from scratch adding VMs from the backup job (instead of VI). Thanks.
by audiobog » Tue Sep 03, 2013 2:03 pm people like this post
Hi, Sorry for the late reply!
I've tried the workaround on the job with Datadomain repository. No success. Made another job to Windows disks instead: no problems at all. Same settings in both jobs. I'll try without any compression or inline dedup to the DD and see what happens.
by Gostev » Wed Sep 04, 2013 2:46 am people like this post
Compression or dedupe settings are irrelevant to this, so don't bother wasting time on this experiment. The only thing relevant to this issue is storage optimization setting (Local/LAN/WAN) in Veeam job.
Sorry - but i still do not get it. Where excactly do i have to change that ? I know i can change it on the Job itself - but where can i modify that for the Backup-Copy-Job? A small hint would be helpful
by v.Eremin » Thu Sep 05, 2013 8:09 am people like this post
You can disable backup copy job, delete files already created by it (delete from disk) and enable backup copy job again. This way, backup copy job will create restore points at remote location with the exact block size used by original backup job. Otherwise, recreate a backup copy job from the scratch. Thanks.
by skramjet » Wed Sep 11, 2013 11:59 am people like this post
This doesn't work. I have 2 machines, each with their optimisation set to LAN target instead of local. When the backup copy jobs are created (new backup copy jobs). They set it 'restore point is located in backup file with different block size'.
I have tried changing the optimisation settings for the jobs to Local target, but the same error still occurs.
by Gostev » Wed Sep 11, 2013 2:45 pm people like this post
What happens here (unless you are running into some kind of bug) is some other VMs included in the backup copy are backed up by the job with different block size than these two VMs. If you open a support case, they will be able to tell you which exactly after reviewing the logs. Thanks!
by paul2kl » Fri Sep 13, 2013 8:37 pm people like this post
I have the same issue as you. Did you upgrade to Veeam 7 ? If so were the backups jobs created in Veeam 6.5. Then you tried to use the backup copy job in veeam 7, and it never starts. This is the issue I have. I had to re-create the backup job in veeam 7 and then do the backup copy job ( Now it all works). But there is no way I am going to re-create all the backup jobs so I have logged a call with Support to see what can be done to get this working.