Question

Instant VM Recovery => Migrate to production Greyed out


Userlevel 7
Badge +7

Hello guys,

One of my client can’t used the migrate to production feature. Is there some prerequisites? I miss maybe something :D

Thanks.


16 comments

Hello, I had faced the same issue yesterday. Tried to use Migrate to production option but it failed, then it turned greyed out. So I performed a Quick Migration from the inventory page. It worked! If you can use vMotion is an option too, the best path actually.

Userlevel 7
Badge +20

Hi @Stabz, what is the status of the VM? and is this restored to vSphere/vCloud/Hyper-V etc?

 

I’d be tempted to try and gleem an error message out by using the PowerShell cmdlets to attempt a migration, see why Veeam says you can’t:

https://helpcenter.veeam.com/docs/backup/powershell/instant_cmdlets.html?ver=110

Userlevel 7
Badge +7

@Stabz I’ve never seen that disabled/greyed out before. Would be curious to know the reason. Have you reached out to Support?

Cheers!

Hello sorry for the delay, unfortunately I dont get any feedbackof my client  yet. I keep you in touch :). 

Userlevel 7
Badge +20

Not sure if this helps but the VM you are trying to recover - did it come from a host that is an older version of where you are trying to recover to?  This explains the thing about host versions - Migrating VMware VMs recovered with Instant VM Recovery to Production. - Veeam Cookbook

Only thing I can think of that would prevent this.

Userlevel 7
Badge +13

Any news on this topic, @Stabz ?

Userlevel 7
Badge +7

Hi @Stabz, are you using VMware hypervisor or Hyper-V hypervisor?

Hi @Nico Losschaert , VMware hypervisor 

 

Userlevel 7
Badge +10

Alternative idea is set up a replication job then do a failover. (Source IVMR VM, Target new cluster)

Userlevel 7
Badge +16

@Stabz I’ve never seen that disabled/greyed out before. Would be curious to know the reason. Have you reached out to Support?

Cheers!

Userlevel 7
Badge +7

Sorry I was in another projet.
After a quick check, Veeam is in version 11a, I read somewhere maybe in the forum that there is a bug with this feature in this version.

The vm has been restored to the vSphere VxRail production in a new vLan. The VMs are up.

I ll continue to investigate asap

Userlevel 6
Badge +10

Did you IR to an individual host on a cluster where DRS is enabled? I believe I’ve seen this happen occasionally if vCenter migrates the VM to a different host in the cluster when an individual host was selected in the IR settings. 

On the Backup and Replication console, go to Inventory and look at the Virtual Infrastructure. Mine is VMware. Drill down the subtree until you see your Cluster and click on it. In the right pane, right click on the VM that you're having trouble with and click Quick Migration, then follow the prompts. Once it completes it will remove the VM from the Instant Recovery window. Hope this helps other people.

Userlevel 7
Badge +11

Hi @Stabz, are you using VMware hypervisor or Hyper-V hypervisor?

Userlevel 7
Badge +7

Any news on this topic, @Stabz ?

Hello, unfortunately not… my customer have move the vms directly from vSphere… so I ll not have the final answer :(

Userlevel 7
Badge +16

Hi @Stabz -

I was just following up on your post here. It appears you weren’t really able to follow up with your customer who had the issue with the IR process migrating to production? Was there a comment provided which you think may have helped if you were able to? If so, could you mark one as ‘Best Answer’ to benefit others who may experience the same issue?

Thank you.

The problem is when you pick this option (Move to production), start this process and it break. You can not start it again. VB&R ver. 11.0.1.1261. I think it is a bug , it should be an option to repeat that. Don’t you think?

Userlevel 7
Badge +7

Hello, I had faced the same issue yesterday. Tried to use Migrate to production option but it failed, then it turned greyed out. So I performed a Quick Migration from the inventory page. It worked! If you can use vMotion is an option too, the best path actually.

Alternative idea is set up a replication job then do a failover. (Source IVMR VM, Target new cluster)

Hello guys, thanks for the tips, good to know if i encounter the problem again.
 

Did you IR to an individual host on a cluster where DRS is enabled? I believe I’ve seen this happen occasionally if vCenter migrates the VM to a different host in the cluster when an individual host was selected in the IR settings. 

The VM has been IR in a cluster, but I don’t remember if DRS is enabled in this infrastructure, but this could be an explanation ! Thanks 

Comment