Veeam Backup & Replication • Migrate to new server while continuing volume-based backup of disk attached to old server?

I have migrated my VBR installation to a new server following the official instructions. Copying and re-mapping the existing backup files went without problems. However I did not yet succeed to continue my existing backup job which was doing an agent-based volume-level backup of a disk attached to the old VBR server (which should keep being attached to it).

The new server has migrated the "localhost" PC in the protection group with the old server's IP address but somehow it also sees the machine as its own so it has added a second "localhost" entry with its own IP address in the protection group. Now there are two "localhost" entries there, one with the old server's address, one with the new one's.

Rescanning the protection group yields the error that it cannot delete the PC which I think he should not do anyway because I have a backup job using it:

09.05.2026 18:45:50 Warning : localhost cannot be deleted, because it is used as the source for one or more backup jobs. Agent Backup Job 1 (Windows Agent Backup)

Trying to run the job produces the following error:

09.05.2026 17:34:47 Failed : Task failed. Error: Failed to connect to agent at localhost. Rescan the machine and try again.

What ist the recommended way to continue backing up the disk on my old server with the existing job (so that after migration no new chain has to be started or a new active full has to be produced). Is there any way of getting rid of the "localhost" host addressing? Anything that can be done prior or after the migration to change this association and let VBR simply refer to the managed agent by its IP address / host name?

Statistics: Posted by pfeifix — May 09, 2026 5:40 pm

---