Why Migrate to Production no finished Instant Reovery ?

[skydok]

Hello,
After VM recovery finished to Power ON VM on the Veeam NFS i do the "Migrate to Production".
after the vStorage finishes on the VMware Side the Running jov is finished but the in the Left Pan "Instant Recovery" doesn't finishes and it stays Mounted .
if i stop the Publishing then it stops and everything is ok. the Recovered VM in the vCenter stays as it should .

i don't know if by Design it doesn't finished the "instant Recovery Mounted" or not.
please open my eyes on that case.


thank you

[Vitaliy S.]

Hello,

Yes, this is by design. VM will stay mounted in the UI even if you've moved/copied/migrated it back to production. No need to worry.

Thanks!

[RPatel]

Hi, I have same issue,
I moved the machine to production.
Veeam shows running, starus is Working.
On VM side instant machine is restore but Machine_Migrated intant is still there.
I suppose to manually deleted machine Migrated (delete off the disk) from VCentere server?
Thanks

[Gostev]

Yes, but first "stop publishing" the VM in Veeam.

[RPatel]

Hi Anton,
Yes once click "stop publishing" in Veeam, Instant in Machine_Migrated removes by it self.
I thought it might have automated process, So basically this it how it works?
Thanks

[foggy]

Yes, this is how it works, as mentioned above:

Yes, this is by design. VM will stay mounted in the UI even if you've moved/copied/migrated it back to production. No need to worry.

[deduplicat3d]

I had to recover my first VM today and noticed the above behavior. I would like to put in a feature request to stop the job after migrate to production, I don't see why the user would want to see this after they migrate to production. You can still view the results under history.

[foggy]

But wouldn't you want to verify that the migrated VM operates as required prior to removing instantly recovered VM?

[tsightler]

But wouldn't you want to verify that the migrated VM operates as required prior to removing instantly recovered VM?

To play devils advocate here, what can you possibly do about it even if the migrated VM doesn't operate as required? In what possible way does having the instant recovery session still running actually help? Sure if the migration itself actually fails, but for a migration that was reported as successful. If the migration uses Storage vMotion or if the "delete source VM files" options are selected there's not even any files left in the instant recovery session so what possible use is the instant recovery session at this point?

[foggy]

If the migration uses Storage vMotion or if the "delete source VM files" options are selected there's not even any files left in the instant recovery session so what possible use is the instant recovery session at this point?

Right, I was not thinking of this case. In situation where there's no source VM already, stopping IR session automatically does makes sense.