Failback error: Object reference not set to an instance of an object (4041021)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Failback error: Object reference not set to an instance of an object
Description

Failback failed with error message "Object reference not set to an instance of an object". Failover doesn't have any issue.
Cause

The Source VM changed negtwork after replication job. This can be seen from the VM settings
Resolution

The issue of Networking changes during failover/failback operation from a replicated Linux machine is expected.

Newer Linux versions now associates MAC addresses with network configuration as noted in the KB below and so ETH0 will become ETH1 which will need to be configured.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2002767

This forum has a script that might make the fix easier for VMs where only a single NIC is involved - use it at your own risk. The script basically renames eth1 to eth0 which should have the desired result.

http://www.cyberciti.biz/tips/vmware-linux-lost-eth0-after-cloning-image.html

In summary, this is non vRanger issue. You might want to clarify with vmware or linux support on how they will manage this issue in the future. RedHat has a documented workaround though. Here is the link for you:

https://access.redhat.com/discussions/916563
Defect ID

15386
Additional Information

vRanger logged enhancement request: 15386. This is if possible to correct the issue within vRanger. This will be evaluated for inclusion in the future release of vRanger.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title