Move backup to another job

[Nas]

When moving backup to another job targeted to the same SOBR (local disk as performance + Azure blob as capacity). The following warning appear.
"only backups located on the performance tier will be processed. backups from the capacity and archive tiers will be detached from the job. continue anyway?"

My expectation, after successful moving the backup on performance tier, Veeam will start offloading only the latest restore point from the new job to the capacity tier.
However, it seem that after move job completed, Veeam quickly start offloading the whole backup chain. This caused duplicate restore points to exist in capacity tier, from Old_Job (detached) and also New_Job.

Is this expected behavior of the move backup operation?

[KirillChuxlancev]

Hello,

Thank you for your question.

I can confirm that the behaviour you described is currently expected. This is because, during the Move Backup operation, a new Backup logical entity is created at the target location. As a result, the offload job treats this backup the same way it would a backup created directly by a backup job.

That said, I will discuss this scenario internally and investigate whether we could enhance this behaviour in future releases—specifically, to enable processing of only the latest part of the backup chain.