Instant Recovery dismounting fails

[david.brunner]

Dear all,

since I have trouble opening an official ticket (Enterprise license), I try my luck in posting here.

After trying the Instant VM recovery option (restore a VM, which is a backup from an vsphere Host, to an hyper-v host) the vm was shut down and removed, but it is still open in "instant recovery" with status dismounting. Some days have passed and it did not disappear even with a reboot

The only article I find about this is from 2011:
https://ict-freak.nl/2011/09/14/veeam-i ... smounting/

Should I proceed with the steps mentioned?

Thanks!

I really hope to be able to restore VM backups from vsphere to Hyper-v (in emergency situations). With V11 they said it would be supported

best regards,
David

[foggy]

Hi David, it is not recommended to interact with the Veeam B&R database directly without support assistance, specifically based on the post that old. I recommend trying to contact them again - what kind of issues did you have with opening a case?

Btw, did you shut the VM down manually using vSphere client instead of stoping the Instant Recovery session from the Veeam B&R console instead?

[david.brunner]

Hi Alexander,

it is an internal problem, it seems. The support ID, needed for opening a ticket, is not correct and I need to contact the licence admin (my boss) and this will take its time.

yes, I think I shut down the VM and deleted it manually since I did not see, that there is a publishing session open in B&R console

[foggy]

Anyway, the issue is not urgent, so I recommend taking your time to find the correct support contract ID and go through this with the help of our engineers. Thanks!

[david.brunner]

For anyone who has the same Problem - in the end I managed to create a support case.

Since stopping the session with

Code: Select all

Get-VBRInstantRecovery | Select -Last 1 | Stop-VBRInstantRecovery

did not help, this command via SQL finally removed the session:

Code: Select all

removed by moderator

[foggy]

Glad you were able to sort it out. I removed the query from your post, however, as we do not recommend database interactions without support assistance, as mentioned above. Database format changes from version to version and you can easily run into issues.

[marph]

Thank you David, for posting the PowerShell code!
Today I had the same issue. In my case I was able to stop the instant recovery session with the PowerShell code David mentioned.
Btw, at the end of the code there is a "y" missing: The cmdlet is called Stop-VBRInstantRecovery.

[Egor Yakovlev]

Hi Matthias!

None noticed that little typo for a couple of months!
Added "y" to make the PowerShell cmdlet correct

[sbk]

Another Thank you for David! I was about to open a ticket for the same issue and ran across this post before doing so. The PowerShell code also cleared the instant recovery for me that was stuck in a dismounting state after the VM was moved back to production.

[mrhron]

Hello to all!
I had the same problem, the PowerShell command did not solve it.
What I've done:
1. Get the process ID using Get-VBRInstantRecovery
2. Stopped veeam services
3. In the veeam sql database, I deleted the line with my ID.
An example script.
DELETE FROM [dbo].[VmssVms]
WHERE id = '963b9363-4a41-4556-80d5-bcfed8524edb';
If you do not want to bother, then you can clear the entire table.
DELETE FROM [dbo].[VmssVms]
After starting the services, the information about in "instant recovery" with status dismounting disappeared.

Have a good day!
Hello from Russia!