Fehler: Das ist nicht das letzte Volume eines Backup Archive / this is not the las Volume from a backu archive
Ich bekomme immer wenn ich unter VMWare (12) eine Archive von meinem alten BS zurückspielen möchte (Restore) den Fehler "Das ist nicht das letzte Volume eines Backup Archive"!
Ich versuche das Archive mittels "Acronis Rescue Media" mit Acronis True Image 2016 (64 Bit) in die vorbereitete VM zu integrieren (Restore).
Egal was ich versuche, ich bekomme immer die selbe Fehlermeldung.
Das Archive ist ein Vollbackup einer SSD! Also keine Versionskette oder Incrementelles Backup ...
Ich möchte einfach mein altes System (vom alten Rechener mit alter Hardware) in eine VM bekommen, um dort zugriff zu haben.
Wenn ich das tib File in Acronis am Rechern öffne, wird es auch gemountet ohne jedgliche Meldung!
Jemand eine Idee was hier falsch ist?
-Rescue Media als 1 CD in der VM angelegt
-tib als ISO im 2 CD in der VM angelegt
Booten der VM über 1'tes CD und dann Versuch von Restore ...
Oder wie bekomme ich ein *.tib in eine VMWare?
----------------------------------
I always get the error "This is not the last volume of a Backup Archive " when I want to restore a Image inside VMWare 12! I try the archives means " Acronis Rescue Media " with Acronis True Image 2016 ( 64 bit ) into the prepared VM ( Restore ) .
No matter what I try , I always get the same error message . The Archive is a full backup of a SSD ! So no version chain or incrementel backup ... I just want my old system to get ( from the old computer with old hardware ) in a VM to have access there .
When I open the tib file in the Acronis Rechern , it is also mounted without any error message!
Some one have a hint for me?
Or how i can restore a old *.tib to a VMWare?


- Accedi per poter commentare

I am attempting to push a TIB backup of an EFI only to a new VM now. I am using VM Workstation 12 Pro (12.1.0 build-3272444) and ATIH 2016 (6027) offline bootable UNIX recovery media for the image deployment.
I took all of the defaults in VMWare (SCSI drive instead of SATA, 60G drive, 2 GB memory, but did change neworking from NAT to Bridged so that it would be able to see my network shares more easily), I had the acronis ISO mounted at boot and when I started the VM, it launched straight into ATIH 2016 x64 without issue. Within ATIH 2016 offline Linux recovery, I then selected my previously backed up .TIB image on my network share and provided authentication credentials and it picked it up fine. However, initially, Acronis could not detect a suitable disk to restore to, so I backed out of the recovedry and used the tools menu to mount a new disk and initialize the newly created 60GB VM hard disk. After that I could then select the 60GB VM hard drive as a disk to recover the image to.
I then selected all partitions except for MBR Track 0 and started the push to the VM. The image is deploying without any issues (will it boot, not sure yet, but I'll find out soon). This leads me to believe that you either have a corrupted .TIB, it has been renamed (wrongly) or you are not selecting the first numerical TIB in the chain when it prompts you to pick one (don't pick the last one, it needs to be the 1st one).
As far as I can tell, the deployment to VMWare is working fine and I will soon find out if it boots, and if it does not, I will first try Universal Restore since i specifically picked a different system image for this test than that of the physical hardeware that I am running VMWare on. I'll post back when the image deployment is done with an update.
- Accedi per poter commentare

The image pushed fine - it did not boot. I think this may be a limitation of VMWare though as the image I pushed back was GPT/UEFI only, yet Acronis bootable recovery medial booted into the legacy mode and not UEFI mode and the virtual bios is very basic so it probably only works with legacy bios (MBR) images. I am going to test again with a legacy system, Win 10x64 OS deployment now just to see if it will boot that way.
Regardless, I had no issues with the actual Acronis deployment process in VMWare - no issues with my backup .TIB... so I'm still inclined to think your backup is bad, was renamed incorrectly, or you are not selecting the 1st numerical sequence of the backup and that's why it's telling you "This is not the last volume of a Backup Archive ". Any chance there is an off named file in your backup, perhaps one that has a -1, -2 or some other "-" at the end like this:
yourbackupname_full_b1_s1_v1-1.tib
If so, you may want to try and validate your backup to see if it checks out as a good backup.
- Accedi per poter commentare

The second legacy image pushed from Acronis .TIB backup to VMWare and booted without the need for Universal Restore. I am still not sure if there is a VMWare Worstation limitation of UEFI and/or GPT though. I will have to go back and look at another VM to test to see how a clean install of Windows 10 x64 sets the disk type in VMWare Workstation 12. Regardless, this does seem to work as long as you have a good source .TIB backup to start with.
- Accedi per poter commentare