Salta al contenuto principale

"This is not the last volume of the back-up archive" due to full backup

Thread needs solution

Hi,

I am using TIH2016 to back up my SSD two times a week. I selected to create a full backup every time (no differential!) and also selected to keep the last three versions so I have the possibility to choose.

Yesterday was the day ... my SSD crashed and I wanted to restore my latest backup. So I booted from the Acronis medium, selected recovery, selected the latest backup volume and boom ...

This is not the last volume of the back-up archive

What the ... ?! :( What can I do now and why does this error pop up? I only found that one in conjunction with differential backups....

 

Here is the log from the last full backup:

1    Information    07.04.2016 03:00:03    Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false; 
2    Information    07.04.2016 03:00:03    Aktion Samsung SSD 840 EVO 120GB wurde per Planung gestartet.
3    Information    07.04.2016 03:00:03    Aktionsbeschreibung: Stufenbeschreibung.
4        07.04.2016 03:00:03    AcronisLRPCConnect::BEGIN id=2.128
5        07.04.2016 03:00:03    AcronisLRPCConnect::BEGIN id=1.608
6        07.04.2016 03:00:03    Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
7        07.04.2016 03:00:03    Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0
8        07.04.2016 03:00:03    Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0
9        07.04.2016 03:00:03    Refreshing Drivers...
10        07.04.2016 03:00:03    Enter to process disks in Mbr Driver (id = 9)
11        07.04.2016 03:00:03    Exit from process disks in Mbr Driver (id = 9)
12        07.04.2016 03:00:03    Enter to process disks in Gpt Driver (id = 10)
13        07.04.2016 03:00:03    Exit from process disks in Gpt Driver (id = 10)
14        07.04.2016 03:00:03    LDM: New ProcessDisks(rawLayer, headLayer)
15        07.04.2016 03:00:03    ProcessDisks: One more disk to check
16        07.04.2016 03:00:03    ProcessDisks: One more disk to check
17        07.04.2016 03:00:03    Mark All groups as Root Like Dgs
18        07.04.2016 03:00:03    ------ Volumes Objects ------
19        07.04.2016 03:00:03    LDM initialization complete
20        07.04.2016 03:00:03    Analysiere Volume '0-0'...
21        07.04.2016 03:00:04    Analysiere Volume '2-1'...
22        07.04.2016 03:00:04    Analysiere Volume 'C:'...
23    Information    07.04.2016 03:00:04    Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false; 
24        07.04.2016 03:00:04    Fehler beim Öffnen der Konfigurationsdatei ''.
25        07.04.2016 03:00:04    Fehler beim Erstellen der Datei.
26    Information    07.04.2016 03:00:04    Aktion: Backup
27    Information    07.04.2016 03:00:04    Priorität geändert in 'Niedrig'
28    Information    07.04.2016 03:00:04    Backup-Archiv erstellen Kennwortgeschützt Von: 	Laufwerk 2 In Datei: 	"D:\Temp\backups\Samsung SSD 840 EVO 120GB.tib" Komprimierung: 	Normal Exclude: 	Durch Ausschlussmaske erfasste Dateien Passendes Kriterium: 	$Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Martin\AppData\Local\Temp, C:\Users\sshd\AppData\Local\Temp, C:\Users\Martin\AppData\Local\Microsoft\Windows\INetCache, C:\Users\sshd\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Martin\AppData\Local\Google\Chrome\User Data, C:\Users\Martin\AppData\Local\Opera Software, C:\Users\Martin\AppData\Roaming\Opera\Opera, C:\Users\Martin\AppData\Local\Mozilla\Firefox\Profiles, C:\Users\sshd\AppData\Local\Google\Chrome\User Data, C:\Users\sshd\AppData\Local\Opera Software, C:\Users\sshd\AppData\Roaming\Opera\Opera, C:\Users\sshd\AppData\Local\Mozilla\Firefox\Profiles  
29    Information    07.04.2016 03:00:04    Ausstehende Aktion 160 hat begonnen: 'Volume-Image erstellen'.
30        07.04.2016 03:00:21    Partition 2-1 sperren...
31    Information    07.04.2016 03:00:21    Schreibe vollständige Version zu Datei: Samsung SSD 840 EVO 120GB_full_b32_s1_v1.tib
32    Information    07.04.2016 03:00:29    Ausstehende Aktion 160 hat begonnen: 'Volume-Image erstellen'.
33        07.04.2016 03:00:45    Partition C: sperren...
34    Information    07.04.2016 03:22:00    Ausstehende Aktion 160 hat begonnen: 'Volume-Image erstellen'.
35    Information    07.04.2016 03:22:00    Die folgenden Backups wurden erfolgreich erstellt: "D:\Temp\backups\Samsung SSD 840 EVO 120GB_full_b32_s1_v1.tib"
36    Information    07.04.2016 03:22:00    Backup-Archiv konsolidieren Speicherort: 	"D:\Temp\backups\Samsung SSD 840 EVO 120GB_full_b32_s1_v1.tib" Ziel: 	"D:\Temp\backups\Samsung SSD 840 EVO 120GB_full_b32_s1_v1_C9AD1EC1-81AA-4613-8A19-B26C6F2EF91A.tib"  
37    Information    07.04.2016 03:22:00    Backup-Archiv konsolidieren Speicherort: 	"D:\Temp\backups\Samsung SSD 840 EVO 120GB_full_b32_s1_v1.tib" Ziel: 	"D:\Temp\backups\Samsung SSD 840 EVO 120GB_full_b32_s1_v1_C9AD1EC1-81AA-4613-8A19-B26C6F2EF91A.tib"  
38    Information    07.04.2016 03:22:00    Backup-Datei mit dem Pfad D:\Temp\backups\Samsung SSD 840 EVO 120GB_full_b29_s1_v1.tib wird gelöscht.
39        07.04.2016 03:22:00    ServerLRPC::_CloseConnection id=2.128
40        07.04.2016 03:22:00    ServerLRPC::_CloseConnection id=1.608
41        07.04.2016 03:22:00    ServerLRPC::_CloseConnection id=1.608
42        07.04.2016 03:22:00    ServerLRPC::_CloseConnection id=2.128
43    Information    07.04.2016 03:22:01    Aktion erfolgreich.
0 Users found this helpful

Peter, I would recommend trying to validate your backup archives to ensure that each one has good integrity.

Have you tried to restore from any of the other archives you have available?

I tried booting rescue media not from UEFI and now I can start recovery, but then I get the error that the backup volume is corrupt, nice :D

The third and oldest backup file worked ... :/ System is now restored and I set the option validate image after backup, hopefully this happens not again :(

 

 

/EDIT: just for fun I just validated the backups that wont recover, and TIH says they are valid ... that is not good.

HI Peter, the backup that is saying it validated but also corrupt... perhaps try running checkdisk /f /r on that drive and see if any errors are detected and/or attempted to be repaired.  Dirty sectors on a disk can corrupt the files on them and/or prevent them from being read correctly.  

If the SSD was going bad - it is quite possible that the contenets of the backup have the same corruption as was present on the SSD before it died, so even though it validates - as far as having everything needed, it might actually have bad sectors/blocks in the backup itself, making it unusable.  

If possible, try restoring that "corrupted" backup to another test drive and click the buttons to ignore "errors/warnings" during recovery and see if the iamge can be recovered afer that.  I know the option to ignore back sectors/warnings can be done during the backup, but can't remember if they are in the recovery option as well and currently don't have time to boot into a recovery disk to double check that though. 

Also, was the recovery started in Windows (I'm guessing not since the SSD failed).  If it was though, try using the offline bootable recovery media and make sure that when you boot up, you boot to the proper installer type that matches the OS disk (legacy/MBR or UEFI).  The acronis bootable media can do both, and for backups, it doesn't matter which one, but for recovery, it should be the same type as the OS was originally installed with.