https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODUwIiwiaGFzaCI6ImNkY2Q4YWUwLTEyMTktNGNiNi04YzllLWUyZTBiZGViNTVjNyJ9
1-800-691-1991 | 9am - 8pm ET
EN

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

Challenge

You receive an error after manually deleting a replica VM.

Cause

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

Solution

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.



KB ID:
1850
Product:
Veeam Backup & Replication
Version:
6.x, 7.x
Published:
2014-01-22
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later