Error when changing replication job destination host

[LabanM]

I recently replaced some vsphere hosts that were used as destination hosts in a few replication jobs. I migrated the replicas to the new hosts and kept the same datastores (SAN). When I try to change the destination host in the replication job I get an error and nothing changes. Do I need to recreate the jobs? I tried disabling the job first but the jobs will not disable.

Error: Object reference not set to an instance of an object.
Veeam Backup and Recovery Enterprise Version 11.0.1.1261

[jorgedlcruz]

Hello,
Have you opened a Support ticket yet? If so, please share the Support Case Number here.

For this scenario, have you used the mapping Replica functionality on the job? That usually made the trick for a lot of different scenarios similar to this.

Have you already deployed the latest patch, etc? I do not think it affects, but always better to be sure.

Totally recommending to open a support ticket, thanks!

[Egor Yakovlev]

Object reference errors are quite common when expected value in DB is not present.

- Are old hosts still visible under Backup Infrastructure > Managed Servers?
- Do new hosts share old hosts names?

/Thanks!

[LabanM]

I do not have a Veeam Support ticket open yet. I am not familiar with the Mapping Replica functionality. I will look into that.
The old servers are no longer listed in the Veeam Inventory. New hosts do not share the names as the old servers.

[LabanM]

I have a case open. Case #05416847

[Egor Yakovlev]

Thanks for the case, let's see what support discovers!

Also:

change the destination host in the replication job

+

old servers are no longer listed in the Veeam Inventory

That's the thing: product will not allow you to remove hosts while there are jobs referencing them.
So I am wondering how did you manage to keep jobs and get rid of the hosts

[LabanM]

Support recommended enabling seeding and mapping vms to replicas. Unfortunately, it did not work. I ended up writing a script to move vms to a new job and mapping vms to the replicas in the new job. Back to successful replication.