Backup Copy JOb - Not cleaning up VIB after Merge...

[nikpolini]

Hi Every one.

I seem to have an issue with my backup copy Jobs.
It is set to keep 14 restore points but I have 32 files on disk.
I can see that the VBK has a date between the first and last VIB.
Its like the job is not removing the VIB after roll into the VBK.

Any ideas?

[nikpolini]

Its as if this step is missing:

https://helpcenter.veeam.com/backup/hyp ... ntion.html

[nikpolini]

OK, so I'll add a bit more info for clarity.
The copy job is set to run once per day at 6AM, after my normal backups are complete.
It is targeted at a scale-out repository with Per VM files enabled.

Now I found this: "Transform phase — copy jobs are by nature running in "forever forward incremental" mode, and performs transform operations on the target backup repository accordingly. Additionally, it is possible to schedule health checks or backup file compacting as described in the Backup Job section. The transform phase begins when all VMs are successfully copied to the target, or if the synchronization interval expires." http://bp.veeam.expert/job_configuratio ... y_job.html

Not all VMs in the Copy Job are successful, as some are only backed up Weekly or Bi-Weekly. So could this be causing the Transform stage to not happen on those VMs that are successful?

T-SQL-01 Warning 6:16:11 AM 6:04:37 AM (+1) 0.0 KB 0.0 KB 0.0 KB (1x) 0:00:00 Initial copy did not complete, and will resume on the next copy interval

[veremin]

Can you tell me whether "keep the following restore points" and "read the entire restore point" options are enabled in the target settings of backup copy job? Screenshots would be helpful.

Thanks.

[foggy]

Transformation should start once interval expires even if not all the VMs were fully synchronized. The fact that VBK file has the date between the first and last VIBs looks unexpected, so I'd recommend contacting support for logs review.

[nikpolini]

Case #01899393

Note I am getting this error message via email on the backup copy job:

Failed to merge full backup file Error: Cannot determine extent for storage ID fcf7fc1f-32b5-483a-988d-98f05f8c8d4d in scale-out backup repository REMOTE - Scale-out Backup Repository
Failed to generate points Error: Cannot determine extent for storage ID fcf7fc1f-32b5-483a-988d-98f05f8c8d4d in scale-out backup repository REMOTE - Scale-out Backup Repository

[nikpolini]

I am trying a new copy job on a test VM, but to the same Repository to see if the error is with the repository...

[foggy]

So you're backing up to the scale-out repository. Try to rescan it and make sure all the extents are available/operating as expected. Haven't you migrated backups between repositories/extents some time ago?

[nikpolini]

Hi, Yes it is to a scale-out repository.
I am not sure if I have migrated extents... Maybe.

My test job worked fine and did the merge.

I have re-created the Copy Job with 120 VMs (51TB) completely. Let see if that works.