Our VCC has just changed infrastructure and has copied our backup files to a new repository which we had to rescan.
Sure enough all the backup show up just fine, but then we try to create a new backup copy job and map this backup, it will just create new backup files. Actually duplicate Vms with a new, single 1 restore points instead of continue the other VMs restore points (same VM).
After som reading on this forum I think I have found the solution, but would like a confirmation to be sure.
Map backup will ONLY work when your last backup was a full active backup copy job (or a regular full backup before shipping it to your CC hoster).
Incremental backup files will not work.
Is this correct?
In that case we should just start from scratch with a new backup copy job, and manually deletes the older backup files when we have passed their retention?