VCB backups do not restore properly and only config and log files are restored however no VMDK files are restored. This is caused because the .info file for the archive has incorrect info written to it.
Using a text editor (Notepad ++ is recommended and can be downloaded for free.) Edit the .info file in the VM Archives directory
Once we have the file open in a Text editor we want to modify the Line that begins with:
</LogText>
In that line, what we need to edit, is the vmdk file names. Scroll through the line and look for references to .vmdk files i.e.
<Type>DiskStub</Type><Name>2138 test.vmdk</Name>
<Type>DiskFlat</Type><Name> 2138 test-flat.vmdk</Name>
The problem is now identified. The vmdk file names point to the original vmdk file names in the VM, however the correct archive file names begin with scsi0-*-0(* represents SCSI id for the disk)
Referencing your Archive directory for the proper files names, edit each entry in the line to reflect the correct vmdk file name.There is a Stub entry and a Flat entry for each disk in the VM. So the entries will look similar to the following once edited:
<Type>DiskStub</Type><Name>scsi0-0-0-2138 test.vmdk</Name>
<Type>DiskFlat</Type><Name> scsi0-0-0-2138 test-flat.vmdk</Name>
<Type>DiskStub</Type><Name> scsi0-1-0-2138 test.vmdk</Name>
<Type>DiskFlat</Type><Name> scsi0-1-0-2138 test-flat.vmdk</Name>
If the VM has duplicate files names for the VMDK files, rename the entries in the order they are listed in the line. I.e. 1st vmdk Stub and Flat entries in the list would be scsi0-0-0, the set of entries 2nd would be scsi0-1-0, etc…
Thus matching the file names listed in your archive directory .Your archive directory should list the files similar to this:
02/13/200912:46 PM10,881 2138 test.info
02/13/200912:32 PM8,684 2138 test.nvram
02/13/200912:32 PM59 2138 test.vmx.sig
02/13/200912:32 PM1,427 2138 test.vmx.vzc
02/13/200912:32 PM860 catalog
02/13/200902:59 PM0 dir.txt
02/13/200912:34 PM627,945 scsi0-0-0-2138 test-flat.vmdk.sig
02/13/200912:34 PM922,016,061 scsi0-0-0-2138 test-flat.vmdk.vzc
02/13/200912:34 PM422 scsi0-0-0-2138 test.vmdk
02/13/200912:35 PM627,945 scsi0-1-0-2138 test-flat.vmdk.sig
02/13/200912:35 PM22,556,140 scsi0-1-0-2138 test-flat.vmdk.vzc
02/13/200912:35 PM422 scsi0-1-0-2138 test.vmdk
Once the .info file has been edited to reflect the correct file names in the archive, save the file, and re-run your restore attempt. The VM should now restore successfully, if not, contact Vizioncore Support.