1-800-691-1991 | 9am - 8pm ET
EN

Failed to register replica VM

KB ID: 1750
Product: Veeam Backup & Replication
Version: 6.x, 7
Published: 2013-04-17
Last Modified: 2020-08-13

Challenge

When using vCenter 4.0 unable to perform replication if target host doesn't have the same vNetwork as source. Replica network re-mapping doesn't work either.

Replication job fails to register replica VM with the following error:

Failed to register VM, configFile '[Datastore01] VM_replica/vm_replica.vmx', name 'VM_replica', isTemplate 'False', poolRef 'resgroup-1',
hostRef 'host-1', folderRef 'group-v1' at Veeam.Backup.ViSoap.CSoapConnection.RegisterVM(String configFile, String name, Boolean isTemplate, String poolRef, String hostRef, String folderRef)
 
vSphere also shows an error event:  Failed to register VM.

Cause

vCenter 4.0 doesn't allow registering a VM with a VMX file which contains vNetwork settings that do not exist on the target host.
 
For example, source VM has a DVS switch, which doesn't exist on the target ESXi 4.0 in vCenter 4.0:
(from source VMX file)
ethernet0.virtualDev = "vmxnet3"\n
ethernet0.dvs.switchId = "a3 cb 3a 50 fb 26 46 bf-0d 67 88 01 74 a5 98 fa"
ethernet0.dvs.portId = "231"
ethernet0.dvs.portgroupId = "dvportgroup-1"
ethernet0.dvs.connectionId = "5895333"
 
When portgroupId = "dvportgroup-1" does not exist on the target host. vCenter refuses to register such VM.
 

Solution

Algorithm of replication job is the following:

1) upload original VMX file to the target datastore;
2) register replica VM on target with original VMX file;
3) request vCenter to change vNetwork settings of the newly registered machine.

More information

Only vCenter 4.0 is affected. No such problem on standalone ESX(i) 4.0 and VC versions starting from 4.1
KB ID: 1750
Product: Veeam Backup & Replication
Version: 6.x, 7
Published: 2013-04-17
Last Modified: 2020-08-13

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.