Backup copy job does full copy after instant recovery

[jozne]

Has anyone danced with Veeam Backup copy jobs after instant recovery? Anyway straight to the issue.

1) You setup normal backup jobs & backup copy jobs , run backups few times
2) You do instant recovery and migrate to production
3) VM ID has changed, you edit SQL so the backup job "re-uses" backup files
4) You run backup, CBT does not work but you will have the machine listed only 1 time @Backups in disks under the job
5) CBT works on next run

And now comes the issue: Backup copy job does full copy. Is it possible to avoid this?


Edit: oh I forgot to mention that I removed the job from backup copy jobs for a while and readded it, could this cause problems and result to full copy?
I played with scenario where we would have original esxi hw disconnected (offline) for a while and had to use different vm name (since vcenter would complain about 2 vm with same name)

[foggy]

Hi Jari, you mention that you've done "edit SQL so the backup job "re-uses" backup files", what kind of edit was it? Have you matched the VM ID in the database?

[jozne]

Yeah I matched the VM IDs

[foggy]

To my understanding, in this case backup copy should copy only changes. The fact that you've deleted and then re-added the source job back shouldn't affect this.

[jozne]

Hi

did not seem to work even if I did not delete/readd source job to copyjob. It copies full vm.

[foggy]

You can ask support for assistance in investigating the reasons of this behavior.