Quick Migration of VM from Instant Recovery to original host

[Dave-Departed]

Hi All,

I'm trialling Backup & Replication v6, and all has been positive thus far, except...

I have a backup of a VM, and I've tested Instant Recovery successfully, and have it published, and running fine... However, when I go to perform a Quick Migration, to move the VM's disk files from the vPower datastore to the original ESXi host datastore, it eventually fails with the following messages:

Copy snapshot files. Error: Virtual disk with key "3000" was not found
Failed to process VM '<VMname>' at <date and time> Error: Virtual disk with key "3000" was not found
Processing finished with errors at <date and time>

Anyone got any ideas, please?

My support case number is 5176055, just for completion.

Thanks

Dave

[Vitaliy S.]

Hi Dave,

It's better to continue investigating this issue with our support team, however could you please tell me if you see this issue for other VMs? If not, could you please give us more details about the VM that fails?

Thanks.

[Dave-Departed]

Hi Vitaly,

This is the first and only VM I have tested with so far.

I will try another VM, and let you know the results ASAP.

Thanks

Dave

[Dave-Departed]

Hi again Vitaly,

Yes, we get the same result with another VM. Backup and restore of the 2 test VM's work fine, as does Instant Recovery. However, within Quick Migration, when it comes to the process of suspending the VM, taking a snapshot and then copying the snapshot files, the process fails at copying the snapshot files (this time, with a different VM, we got the message "Virtual disk with the key "2000" was not found", as opposed to "3000").

Thanks

Dave

[foggy]

Dave, actually this is an already known issue, should be addressed in one of the next updates.

[Dave-Departed]

Thanks, Foggy.

Is there anywhere I can read up on this, please? Is it known what causes this behaviour? Because, obviously, before we would purchase Veeam, we'd need the Quick Migration tool to be working flawlessly!

Thanks

Dave

[foggy]

Please track the known issues sticky on this forum, Anton always puts the issues outline for each patch there.

[Gostev]

If you have a support case open, you will receive a patch or hotfix as soon as it is available, so there is no need to be checking up on topics daily or anything like that.

Because, obviously, before we would purchase Veeam, we'd need the Quick Migration tool to be working flawlessly!

Ahh, we should not have added this feature in v6 did not even have it in all the previous versions j/k

[captainflannel]

Is there an known or estimated release date of when the update/patch will be released? We also are experiencing the
..
Error. Virtual disk with key "2000" was not found
..

[Gostev]

The hotfixes are only released if there are significant amount of support cases open on the particular issue...

[dellock6]

Hi Anton,
I can add one of my customer to this error, we had to restore a server with instant recovery and I tested for the first time Quick Migration and I've seen the same error. It was not a blocking error at the end since customer had storage vmotion in place, we were only curious to see also Quick Migration in action.

[captainflannel]

Oh interesting, I did not think about vSphere licensing and vMotion requirements. For Quickmigration, is veeam essentially performing a vStorage Migration? so any vSphere Essential Plus customers w/o vStorage would be out of luck for Migration from quick restore?

[dellock6]

No, this was a specific situation where we wanted to test Quick Migration "even if" we had svmotion in place, to compare them, and we got the error.

In all other circumstances, Quick Migration is designed right to be a viable alternative of svmotion. It can work in all vSphere Editions just like any other Veeam feature.

[bishoptf]

Is there any update as to when a fix for this will be released, looked in the fixes thread and I didn't see it listed. This was my primary way to work and recover for one of my vm's and I need this for a production environment.

[jladew]

I will post my own case but just wanted to add that I am receiving this error when it attempted to do a SmartSwitch on a Win2003 Server. My VMware License is Essential, so only vStorage.

Jason

[Gostev]

This issue is addressed fixed in 6.1 that should become generally available in the coming days.