I can't import results of Extract.exe ...

[Rambarransingh.N]

Good Day,

I am using Hyper-V, Win Svr 2012 R2, and running Extract.exe on a .vbk I created with VeeamZIP, at the Powershell prompt. The extract 'appears' to work, but, when I go to the HyperV Manager and attempt to import the VM, I am constantly told there are NO VM's in the specified dir.

How do I manually register the newly extracted VM with Hyper-V ?

Thnx,
Nikita

[Vitaliy S.]

Hi Nikita,

Does this work if you try to register this VM using a Veeam backup console? Just trying to understand if there is a difference in the way you've done it with a backup console behavior.

Thanks!

[Rambarransingh.N]

Hi,

Thanks for getting back to me. If I use the actual Veeam B&R, yes, the VM will appear at the destination where I restored it. This also works for the Veeam.Backup.??? - I can't seem to find the program that I has used in the past to do this job, but it was the same thing - it would restore the VM to the Target, and it would appear in the HyperV.

However, if I use Extract.exe or Extractor.exe, both produce the same result:
- The VM is extracted, but, nothing is added to HyperV. I presumed I could use a PS cmdlt to do the job, but so far, I have not found anything that would.

Please help.

Thank you very very much,

Nikita

[Vitaliy S.]

Nikita,

Can you please post a screenshot of restored files as well as the cmdlet you're using to perform this task?

Thanks!

[Rambarransingh.N]

Host: HyperV1 - MS Win Svr 2012 R2 DataCenter
HyperV: 6.3.96....
Src VBK: V:\GOLDEN\VM-RPSR-CERTIFYD2019-01-08T144717.vbk


Dest: HyperV7 - MS Win Svr 2012 R2 DataCenter
Dest Pth: V:\

PowerShell cmd : Extract.exe -restore V:\GOLDEN\VM-RPSR-CERTIFYD2019-01-08T144717.vbk \\HyperV7\V_Drive

RESULT at Dest Pth:

DIR: VM-RPSR-CERTIFY(9fa06b2f-6acf-46fa-ac0c-fc4a33a05fd7)

Contents:
9fa06b2f-6acf-46fa-ac0c-fc4a33a05fd7.xml
backup_doc
VM-RPSR-CERTIFY_C.vhdx
VM-RPSR-CERTIFY_E.vhdx
writer_doc

- No VM is created in the Hyper V Manager after the extract.
- How do I attach this VM to the HyperV Mgr, so that I can configure it and do what I need to?

Thnx,

Nikita

[Mike Resseler]

Nikita,

To make sure we understand it: You extracted the backup file and now under a specific directory you have an XML file (which is the configuration of the VM) and two disks (VHDX). From what I understood, that is all you did. The extract utility will give you the possibility to get the files out of the VBK but will not automatically register it to a virtualization host. The easiest way to get it back into Hyper-V (at least that should work) is to "import" a VM through the Hyper-V console. Point it to the directory that you restored and follow the rest of the wizard. The potential issue that I can see with this method is that it will tell you that it expects a different location for the two VHDX files. But that is not such a big problem because then the wizard will ask you to point to the VHDX and adapt the configuration of the VM so it points to the current location.

More info on this: https://docs.microsoft.com/en-us/window ... l-machines

[Rambarransingh.N]

Good Day,

1. Your understanding of the situation is correct.
2. I presumed the extract utility would register the VM at the destination - my mistake.
3. So, I pointed HyperV at the destination and tried an IMPORT. Hyper keeps saying there are NO VM's in this directory.

IF this can be done in PowerShell, I would prefer that. I have to script this because our team is NOT good at being consistent with instructions. So, I have no choice but to make a script that does the job the same way, all the time, every time.

Thnx for the help,

Nikita

[Mike Resseler]

I'm surprised that it said there is no VM in the directory. Did you point the import to the XML file?

For PowerShell:

Import-VM -Path 'D:\Test\VirtualMachines\5AE40946-3A98-428E-8C83-081A3C6BD18C.XML'
(Path is an example)

[Rambarransingh.N]

Hi,

I tried the import-vm. PS is reporting:

The virtual machine configuration could not be read. The data might be corrupt or not valid.

Does this heave ANYTHING to do with I am using the free version ?

Thnx,

Nikita

[Mike Resseler]

Hey Nikita,

No, that should be not an issue. At least not that I am aware off.
Can you do one check. Create a new virtual machine in Hyper-V with the same settings as the protected VM. Attach the two disks that you got out of the extract utility. See if that VM can boot/ run.

[Rambarransingh.N]

Good Day,

Thnx for the info.

1. What did you mean by: "protected vm" ?
2. I can attach the drives, and start it up - everything appears fine. However, all the software in the VM, including Windows, is no longer valid or activated. For example, I have to reactivate windows in 3 days. If I do the same job by hand, via the VeeamGUI - there is no problem.

I am suspicious that this has to do with the HyperV VSS registration ?

Thnx for help.

Nikita

[Rambarransingh.N]

Good Day,

So after pouring through the powershell ref, I came across Start-VBRHvRestoreVM ... This is exactly what I am looking for, except, when you have a VeeamZIP, you don't really have a RestorePoint that you can pass to the Start-Restore. So, the hunt goes on to figure this out.

I will keep hunting.

Any help would be appreciated.

Thnx all,

Nikita

[Mike Resseler]

Nikita,

RE: Protected VM. It means the backup. Sorry, should have been more clear.
What I do not like is that you have a backup of a VM, and when you do restore (even if it is through extract.exe) that you can't import it into Hyper-V and have the state as is. I would suggest that you take a whole new backup of that (or a VM) and see if that solves the case. It looks like there is something wrong with that specific backup.

If that gives the same problems, then I think it is time to talk to support.