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.
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.
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.
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
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?
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?