VEEAM Instant recovery migrate to production issue

I don’t recall IR ever doing that before either. I also never do so to a different location. There is an option to create a server name for different location. Did you verify if that name suffix “-migrate” was somewhere in the name?

Also, what VBR version are you on? Are you migrating to HV or vSphere?

I have not used IR in a while but if I am not mistaken there is something in the wizard to specify the suffix I believe.  I could be wrong or maybe that is something new in 12.x if you are on that release.  Checking on the documentation.

Also, as Shane asked - what VBR version and hypervisor are you using?

@jackg3 - I checked the User Guide on VM naming for IR.

For vSphere, there is nothing in the restore wizard in which you can add a suffix...you’d have to type a suffix in the VM name field:

For Hyper-V, you can click on the Name button & add a suffix: 

But, both are manual operations...meaning, you have to type them in. There’s nothing I found to where a suffix gets added to an IR-restore VM automatically.

hi @jackg3 also check your vmware license; maybe the host in the new location can not use vmware storage vmotion because of a mising license.

best regards
daniel

Great catch Matthias! Yep..that’s probably what it is because @jackg3 said it appeared when he “migrated to production” and the only options are Storage VMotion and Quick Migration. Jack, notice from the link Mattias shared on what the VM name becomes when using QM as noted below:
 

Is the name shown above what you’re seeing with the underscore (VM-NAME_migrated) and not with a dash (VM-NAME-migrated)?