Inquiry regarding the "Map Backup" feature in Backup Copy jobs

[hungrywolf]

I am currently migrating my backup repository.
Previously, I used a Linux Hardened Repository for primary backups, but I have now switched to an ExaGrid backup appliance.

The primary backup to the new ExaGrid device has been successfully completed.
Now, I want to reuse the backup data stored in the old Linux repository as a secondary target using the Backup Copy

Before: Primary (Linux Repository only)
After: Primary (ExaGrid) --> Backup Copy --> Secondary (Linux Repository)

However, when I try to select the existing Linux repository and use the "Map Backup" option in the Backup Copy job settings, it fails to recognize the existing backup data.

I have already deleted the original backup job from the Linux repository, and the data is currently showing as Disk (Orphaned)
The Veeam version is 12.3.2, and the backup source is a vSphere VM.

My questions are:

Is it impossible to reuse backup data created by a regular "Backup Job" for a "Backup Copy Job" via the Map Backup feature?
Is there an issue with my procedure for reusing the data?


Thank you.

[Mildur]

Hello

Welcome to the forum.

„Backup job chains“ and „Backup Copy job chains“ are not compatible to each other. The old primary backup is still there for restore, but you cannot map a backup copy job with it.

Your new backup copy job will start a new backup chain.

Best,
Fabian