We had the situation that some customer VMs were decommissioned (shutdown). As part of the decommissioning, we needed to keep the backups for a period of time. The normal practice would be to consolidate the backup chain into a single "last state" recovery point for archiving.
We ran a standard Backup Copy job to consolidate the full and incremental backups into a final full recovery point for archiving. The source of the backup was the Backup images and when running the job, the Backup copy job fails with ....
" Task failed Details: The object has already been deleted or has not been completely created "
A support ticket was opened - 01785607. The response from support point out that this is by design as the the job still needs to connect with the source to check the existence of the objects.
Why would there be a need to reference the source VMs when all that is needed is to read the backup images and write out the consolidated full vbk. This seems unnecessary.
Could there be an enhancement to allow the backup copy to run even though the source VMs are no longer operational.