VM Machine error after recovery from Time Machine

[CyberNewbie]

Hi guys

Could I get some help, pls  
I have made a backup of my IMac on a external hdd and then cleaned the hole machine. Now I am trying to get back some of my VM´s from the Time Machine Backup.
Steps I am taking:

Copy the vmdk file from the HDD to my IMac
Then click on the Fusion file and tried to open it with Fusion, but I am getting error 

Trying other alternatives like creating a custom machine gives me the same error. 
I have never did this before so I will appreciate a noob explanation, pls.

Another error..

[a_p_]

Please open a Terminal window, go to the VM's folder (vmwarevm package), run ls -l to list all of the VM's files, and post the result.
Usually one, or more of the required .vmdk files (...-s001.vmdk - ...-s0xx.vmdk) are missing.
Users often report such issues with Time Machine backups.

André

[CyberNewbie]

 

[CyberNewbie]

Hei Andre

I just attached a picture of the VM from the terminal, but I can´t see any of the file you are taking about to be missing?

[a_p_ · Accepted solution]

You missed the "-l" for the ls command, which shows the files with their properties (sizes, time stamps, ...).
Anyway, what you may try is to delete the .lck files, to find out whether this already solves the issue.

If that doesn't help, then post the ls -l output (please copy&paste as text), and attach the 4 small .vmdk descriptor files (compressed in a .zip archive) to your rely. The header files are those without -s00x in their names.

André

[CyberNewbie · Accepted solution]

Sorry for the "-l", anyway deleting the .lck files did the trick. 

Thank you for your support Andre  

[ColoradoMarmot]

As you've discovered, time machine isn't reliable backup for virtual machines.  It's best to actually exclude it from the backups, then use an alternate approach for backup/restore.  Either manual copies or @wila has an application that will do it as well.

[CyberNewbie]

Yes i have seen that. Unfortunately at that moment this was the only choice. But thanks for the advice, will definitely try something else in the future.