Aller au contenu principal

Errors in True Image 2016 from build 6559?

Thread needs solution

I turned with my Problem already technical support, feel but there unfortunately canceled not good.
The error that I have, is that True Image without reason can not be more than 2 backup archives a backup chain in the Secure Zone, all others are groundless deleted, even when switched off automatic cleanup and although enough space in ASZ is!

The error occurs reproducibly on 2 systems with different hardware and software equipment and on both Systenmen a Clean Installation was unsuccessful conducted by True Image - the bug still occurs!

0 Users found this helpful

Andreas, thank you for posting your problem in a new thread and for providing more information.

Please can you download the Log File Viewer app and look at the messages which are being written to the log file when your backups are being run.  Please post a copy of your log file to the forum so that we can help understand what the log shows.

Note: the log files are held in C:\ProgramData\Acronis\TrueImageHome\Logs - you can also zip this folder and post it to the forum if that would be easier for you, then we can check any other logs too.

What size is your Acronis Secure Zone?
What is the size of your full backup archive image file?
What backup scheme are you using, i.e. Single/Full versions only, Incremental, Differential - if the latter, how many incremental or differential images do you keep before making a new Full backup image?

At the moment my time for tests is a bit scarce, so I invite you to the screenshots and the system report the tests high here that I have created for the technical support, there should all settings to be recognizable, and the fact that backups without reason from the Secure zone are deleted

Fichier attaché Taille
368769-130738.jpg 115.9 Ko
368769-130741.jpg 192.01 Ko
368769-130744.log 797.88 Ko
368769-130747.jpg 51.66 Ko
368769-130750.jpg 54.1 Ko
368769-130753.jpg 56.79 Ko

Andreas, thank you for the extra information with screen shots and system report files.

From what I am able to see from this data, all looks to be working correctly based on the following information collected from the log & other files:

Your backup settings look to be:

Disks and Partitions backup of your drive 4 WD external drive.
Incremental scheme with 2 incrementals then new Full backup
Keep first full backup.

Your screen shots showed the following files in your ASZ but with only 2 at any one time per the images:

(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1
(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1
(5ACA824A-3C23-4676-5474-AD8B5E0FEB43)_full_b4_s1_v1

The log files show that you have been creating at least 3 different backup tasks and probably making changes to some of the configuration settings for these?

The single backup task script found in the system report date shows:

<uuid>BDCAB71C-7467-4E91-9276-356B56E5910E</uuid>
<display>Test - Backup 3 &#32;ASZ</display>

The log files for the above backup task script show that the following backup files were created in the ASZ

task=BDCAB71C-7467-4E91-9276-356B56E5910E;  task_name=Test - Backup 3 ASZ
Laufwerk 4 In Datei:  asz:\(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1. 3 
Laufwerk 4 In Datei:  asz:\(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1. 2
Laufwerk 4 In Datei:  asz:\(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1. 
Laufwerk 4 In Datei:  asz:\(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1. 3 
Laufwerk 4 In Datei:  asz:\(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1. 2
Laufwerk 4 In Datei:  asz:\(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1. 
Laufwerk 4 In Datei:  asz:\Test - Backup 3 ASZ_full_b1_s1_v1. 
Laufwerk 4 In Datei:  asz:\Test - Backup 3 ASZ 

The log files also show that you previously created two other backup tasks to the ASZ

task=784E39C4-F2EC-40A7-A5B7-E36955B993BB;  task_name=TESTBACKUP 2 ASZ
Laufwerk 4 In Datei:  asz:\(7B5E1E5F-8869-47B5-FFDD-5BBC07ADC610)_full_b2_s1_v1. 3 
Laufwerk 4 In Datei:  asz:\(7B5E1E5F-8869-47B5-FFDD-5BBC07ADC610)_full_b2_s1_v1. 2 
Laufwerk 4 In Datei:  asz:\(7B5E1E5F-8869-47B5-FFDD-5BBC07ADC610)_full_b2_s1_v1. 
Laufwerk 4 In Datei:  asz:\TESTBACKUP 2 ASZ_full_b1_s1_v1. 
Laufwerk 4 In Datei:  asz:\TESTBACKUP 2 ASZ

task=AB8CAC7F-6614-46DC-8736-7DC8B3C5EE77;  task_name=Testbackup ASZ
Laufwerk 4 In Datei:  asz:\(4F37BFD5-E343-05A0-89B2-536F19A8CC85)_full_b2_s1_v1. 3
Laufwerk 4 In Datei:  asz:\(4F37BFD5-E343-05A0-89B2-536F19A8CC85)_full_b2_s1_v1. 2 
Laufwerk 4 In Datei:  asz:\(4F37BFD5-E343-05A0-89B2-536F19A8CC85)_full_b2_s1_v1.
Laufwerk 4 In Datei:  asz:\Testbackup ASZ_full_b1_s1_v1. 
Laufwerk 4 In Datei:  asz:\Testbackup ASZ 

For each task, there are multiple backup files being created in the ASZ with no mention in the logs of any files being deleted.

I would recommend that you do not make any further changes to your Test - Backup 3 ASZ​ task as for each change you make, you reset the version chain counter.  Let the task run either on schedule, if configured, or manually, and then check the contents of the ASZ.  Please also check and note the actual image file sizes of the files that are being created in the ASZ.

 

The various log files probably stem from the fact that asked me the staff of the technical supports to test the task three times.
In his opinion, Währe of error by the Clean Installation of litter emerged Image and believed by the three-time test run of the error would not occur again.
The error, however, is reproducible at any time, as soon as I select a location for the backups in Acronis Secure Zone.
My full backups are about 20 GB big, the incremental correspondingly smaller. The Secure Zone has a size of 1 TB.
Before Build 6559 and the occurring of the fault zone backup archives of more than 3 months were included in the Secure.
The mistake is just simply that currently no longer like the past 2 archives in the Secure Zone are gedspeichert, all others will be deleted without reason.
I could reproduce on another system with different hardware and software equipment several times the error!

Andreas, sorry for the delay in responding further to your post - I have been kept busy with other non-computer matters but will try to test out your problem scenario when I have the time to do so.  I have created the ASZ on one of my computers with ATIH 2016 build 6571 so should be able to test that I am able to store more than 2 archives in the ASZ to see if I can reproduce what you are seeing.

Andreas,

My tests with the ASZ show that the backups are working correctly and that additional backups are being created without any previous ones being deleted in error.

The key difference is how backups in the ASZ are stored and displayed, which is where I believe the confusion arises.

ASZ works differently to how I remember from the last time that I used it (which was several years ago).

When you create a backup task to write to the ASZ, then the initial Full backup image is given the task name plus the normal _full_b1_s1_v1 appended characters.

When you run the same backup task, then an additional backup is created (full, incremental or differential) and this new archive is given the same name but now has the characters _full_b1_s1_v1.2 appended.

This is as your logs showed from the earlier post:

task=BDCAB71C-7467-4E91-9276-356B56E5910E;  task_name=Test - Backup 3 ASZ
Laufwerk 4 In Datei:  asz:\(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1. 3 
Laufwerk 4 In Datei:  asz:\(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1. 2
Laufwerk 4 In Datei:  asz:\(DB79663E-2779-30C5-FBC3-8B3EF2918309)_full_b3_s1_v1. 
Laufwerk 4 In Datei:  asz:\(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1. 3 
Laufwerk 4 In Datei:  asz:\(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1. 2
Laufwerk 4 In Datei:  asz:\(255BAE73-BBEC-6776-6F46-3B06D50DB95D)_full_b2_s1_v1. 
Laufwerk 4 In Datei:  asz:\Test - Backup 3 ASZ_full_b1_s1_v1. 
Laufwerk 4 In Datei:  asz:\Test - Backup 3 ASZ 

The confusion arises because only the initial container archive is shown in the ASZ, and you need to open or explore this in order to see the other archives stored within it.  Also, archives in the ASZ are not named according to the type, i.e. there are no _inc_ or _diff_ names shown.

See the screen shots attached below - the first just shows the archives for the 3 backup tasks writing to the ASZ.

The second shows the contents of my Win 10 ASZ_full_b1_s1_v1. archive and shows that it is in fact storing 3 different backups where each one is prepended with the "Backup Weekday Month Day Year and Time" plus the v1.2, v1.3 details.

Backup Tue, Jun 21 16 23:50:08 Win 10 ASZ_full_b1_s1_v1.     (my initial Full backup)
Backup Wed, Jun 22 16 08:45:20 Win 10 ASZ_full_b1_s1_v1.2  (my first incremental backup)
Backup Wed Jun 22 16 09:37:04 Win 10 ASZ_full_b1_s1_v1.3   (my second incremental backup)

Each of the above archives can then be explored to see the contents or recover data.

If you explore the archives on your own system in the ASZ you should see the same type of contents.

Fichier attaché Taille
369805-130840.png 21.38 Ko
369805-130843.png 19.41 Ko

If you were so nice to continue your tests the same tasks, to each a new backup container is created (1 Full, x incrementelle backups) per container, would the errors are likely to occur even with you.True Image stores no more than 2 Backup container and deletes older without reason. A creation of a backup chain of the same task is so impossible!I have been working for many years with the secure zone and could always save backup containers of at least 3 months there.If you try to validate the backup archive or carry out a recovery, True image then outputs the error messages that I have uploaded you today. These are, however, in my opinion normal, since the respective Oldest Backup container was deleted.

Fichier attaché Taille
369909-130876.jpg 51.18 Ko
369909-130879.jpg 53.02 Ko

Andreas, I have not forgotten this thread and am still doing further testing.

Andreas, OK, I can definitely confirm that I am seeing the exact same issue when using the ASZ.

I created a test backup task with 1 full and 1 incremental backup then start a new full version chain, but to keep up to 10 versions - only 2 version chains are ever being kept in the ASZ!  I even had the option to keep the first version selected and it ignored that too and deleted it!

I would recommend submitting Feedback to Acronis via the feedback tool in the Acronis GUI with reference to this forum post.

I am currently beta testing ATIH 2017 so my next step will be to test if the same issue is present in that new version too?  I will report this also via the MVP Forums.

p.s. It has taken me a while to get this far as I stopped using ASZ a very long time ago and had to setup a new disk partition arrangement on my test system.  Now I know why I don't like using ASZ - which is the secondary issue that is exposed by this problem.  For the first backups created in ASZ, it keeps the task name, but from the second backup version, it changes the task name to be a cryptic name, i.e. (37791F37-F6ED-4447-B026-859662FF515E)_full_b6_s1_v1.  when my chosen name was simply Test ASZ_full_b1_s1_v1.

One of the key reasons I stopped using ASZ was that I could not identify a backup of a system I had made when I needed to recover it using the Acronis Rescue Media - this was on a dual-boot system, so the contents looked very similar.  At the time I thought it was just the way ASZ worked, now I consider it to be another defect in ASZ file handling!

Thank you so much ! Now I know I was right with my assumption.
Feedback I have just sent, hope it reads someone!
Thanks again for your effort!

Andreas, this problem also happens with the ATIH 2017 Beta version.  I have reported this to the Beta testing forum as an ongoing product defect.

In version 2017, the error is then present again!
As you wonder why one has tested for hours for the support!

Andreas, if you see post: 125087: Will not back to secure zone there are more serious issues currently in ATIH 2017 with the ASZ, in that it cannot be used for backup!