Mapped backup still shown as imported

[masonit]

Hi

We run Veeam 9.5 U4 and backup Windows and Linux agents using protection groups (repository use per-vm backup files) . When we move backup job data between repositories there is an annoying thing. Even though data is mapped to the job. The new data is still shown under "Disk (Imported)" until a new backup run is done. Seems like the bond is first made after backup and not when mapping the data in the job. This is especially a problem for jobs that we run once a month. Then it is confusing having the job data as imported fpr a long time. When doing the same thing in VBR with VM backup data it is mapped directly.

\Masonit

[ejenner]

Are the repositories you're moving the files to and from addressable by a single Backup & Replication server or do you have a separate B&R server for each of the repositories you are moving files between?

[Dima P.]

Magnus,

This behavior is expected as Veeam Agent for Windows performs backup import during it's job run. May I ask why you move backup files across your repositories (was that one time operation or you do that frequently)? Thanks!

[masonit]

In our Veeam agent environment we don't move jobs often. But this time we move all our jobs to a new repository and it noticed that the behaivure is not what I am justed to.

\Masonit