Error: Object reference not set to an instance of an object after manually deleting a replica VM

Veeam Backup & Replication
6.x, 7.x
Last Modified:


You receive an error after manually deleting a replica VM.


The replication job is still mapped to the previous replica VM. An error is produced when Veeam attempts to access the invalid object.


Unchecking the Low Connection Bandwidth (Enable replica seeding) checkbox does not clear the values held in the seeding /mapping settings, if mapping is left enabled when the box is unchecked. The map must be cleared before unchecking this box.
If it is not already, check the box to enable replica seeding in the Name section of the job settings, then click next until you reach the Seeding options.
In the mapping options, highlight the affected VM and click the remove button.

After this you can disable Replica Mapping, and Low Connection Bandwidth (Enable replica seeding)
This will now allow Veeam to create a new replica VM.

Rate the quality of this KB article: 
3.8 out of 5 based on 35 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: