Replication broken after (target)cluster change.

[Peejay62]

After renewing a certain cluster (which is the targetcluster for a replication) a replicationjob doesn't work anymore. I keep getting the "object reference not set to an instance of an object" message within the job settings. Source and targetproxy fields are empty (I cannot choose) and the option " repository for replica metadata" also stays empty.

The initial setup was : vm1 (host1/cluster1) replicated to vm1_repl (host2/cluster2). Some hardware had to be renewed so the vmware admin chose to:
1. first rename the cluster2 to cluster2_old
2. recreated a new cluster2
3. added some new hosts to cluster2
4. migrated the VMs from cluster2_old to cluster2 (in effect clustername stayed the same, object/reference id obviously changed)
5. added some (not all) of the old hosts residing in the old cluster2 to the new cluster2
6. redistributed all the VMs (also the vm1_repl) within the new cluster

Now I don't seem to be able to get the replication up and running again as mentioned. Seems that the relationship between VM1 and VM1_repl is gone. Is this something I could expect in regard to the move that is done? Or has anybody got an idea how to fix this?

thanks, Peter

[foggy]

Peter, yes, this is expected, since, as you've correctly assumed, VM ID's have changed after that kind of maintenance. You need to map the job to the existing replica VMs.

[Peejay62]

Hi Foggy,

that's where the problem arises. Whatever I choose within Job settings, the popup for the "object reference.." is there and I cannot map the replica..
The job is kind of stuck in the job-settings dialogue.. , no matter what i select, the popup is there.
(btw, this is still V7).

Peter

[foggy]

Have you re-scanned the infrastructure after performing the changes?

[Peejay62]

yep, even twice..no success

[foggy]

Then, unless our technical support has a better suggestion, you would need to remove the job and re-add all infrastructure servers in Veeam B&R.