what is the difference between legacy backup copy job and new backup copy job

[apolloxm]

Can someone tell us what is the difference between legacy backup copy job and new backup copy job? what is the benefit if we choose to use new backup copy job? In the legacy backup copy job, there is have 5 times retry, is this still valid in the V12? in the V11a. for some reason, we need to create a active full backup copy by weekly, if there is a network issue, the VBK file will show incomplete in the VEEAM UI, but we still can click sync now to create a VIB file that link to this VBK? dose the V12 still have the same behavior?

[Mildur]

Hello Apollo

I moved this topic to the correct forum. It affects vSphere and HyperV. So we can post it in the main VBR forum.

You can only create new backup copy jobs in V12.
Our new backup copy job allows switching between periodic and immediate backup copy jobs. Per-machine backup is now mandatory for new backup copy jobs.

Legacy backup copy jobs are backup copy jobs (periodic copy jobs) which you had in V11. To be able to use new features of V12 for the backup copy jobs, you must migrate them to the new format:
post476468.html#p476468

for some reason, we need to create a active full backup copy by weekly, if there is a network issue, the VBK file will show incomplete in the VEEAM UI, but we still can click sync now to create a VIB file that link to this VBK? dose the V12 still have the same behavior?

If the copy job doesn't finish within a copy session, they will normally continue in the next session and store the backup data in a VIB file. Did some backups finished to copy? And some were copied in the second session?

Best,
Fabian

[apolloxm]

If the copy job doesn't finish within a copy session, they will normally continue in the next session and store the backup data in a VIB file. Did some backups finished to copy? And some were copied in the second session?

For example, I have a back copy job. it will copy a 2TB VM from backup jobs with active full on every Tuesday. due to there is the network issue(switch was broken and we replaced the new one), the backup copy job finished with an error. per our company policy, we need to resync the data to make sure the VBK file can be restoring. We just click sync now to recreate a VIB file, but the file still mapping to the old VBK file. in this case, we didn't need to run a full from beginning which can save the time. I am not sure is that the same behavior in V12? also, Veeam backup copy job will retry 5 by itself if there is small isssue. is that still working in V12?

[Mildur]

We just click sync now to recreate a VIB file, but the file still mapping to the old VBK file. in this case, we didn't need to run a full from beginning which can save the time. I am not sure is that the same behavior in V12?

Checking the current behavior in V12. I will update the topic later.

also, Veeam backup copy job will retry 5 by itself if there is small isssue. is that still working in V12?

Yes, same behavior. See our user guide: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian