Veeam Backup 7.0.0.771 – Restore Point is located in backup with differen block size

Als bekennender Veeam Backup Fan habe ich mich sehr über das Feature in 7.0 „remote site copy“ gefreut.

Die ein oder andere Hürde während der Implementierung und dessen Lösung sammle ich nun hier.

Im sehr guten Veeam Forum fand ich diese hilfreichen zwei Beiträge dazu:

Backup Copy never starts

Postby howesh » Mon Aug 26, 2013 11:51 pm
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.

howesh

Top
Re: Backup Copy never starts

Postby foggy » Tue Aug 27, 2013 8:21 am
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.

foggy
Veeam Software

Der Fehler in meinem Fall lag daran, dass ich eine andere evtl. auch falsche Art der Optimierung bei der Target wahl genommen hatte. Ich wählte für ein per Netzwerk angeschlossenes NAS „Wan optimization“ welches die Blocksize entsprechend anpasst wie in diesem Post von Entwickler Gostev erklärt wird:

Re: Backup Copy never starts

Postby audiobog » Tue Sep 03, 2013 2:03 pm

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.

— Bent
audiobog

Re: Backup Copy never starts

Postby Gostev » Wed Sep 04, 2013 2:46 am

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.

Gostev

Veeam Software

Wie empfohlen habe ich also gleich beide Tipps genutzt und die alten CopyJobs gelöscht sowie die Optimierung auf LAN Target geändert.

Tipp:
Um den CopyJob löschen zu können, muss man den BackupJob davor deaktivieren, ansonsten bleibt löschen ausgegraut.
Anbei noch der offizielle KB Eintrag dazu sowie tiefergehende Informationen über die Art, wie Veeam den Restore Point wählt.
http://www.veeam.com/kb1835
Restore Point Selection – User Guide
http://helpcenter.veeam.com/backup/70/vsphere/backup_copy_select_point.html

Re: Backup Copy never starts

Postby foggy » Mon Sep 16, 2013 10:36 am

skramjet wrote:I have tried changing the optimisation settings for the jobs to Local target, but the same error still occurs.
Gostev:

Changing optimization settings for the job takes effect after performing a new full only.