Incremental Backups are very big.
I do an incremental backup of two discs. The first full bachup is about 258 GB . The folowing are about 115 GB . This seems very big to me because for the moment I use the Computer only sometimes. My Secu zone is about 950 GB large and so ist is filled very quickly. What is going wrong. In earlier versions of th Program I never had that problem.
I can see from the icon next to the backup name that it's a disk/partitions backup. Is it the system disk? What are the excluded items. Have you excluded pagefile.sys, swapfile.sys, $Recycle.Bin?
I did exclude these files.
Today it is totaly crazy. See Screenshot. I have added the log of 19-410-14.(one of 5)
There are no files I know.
Do I make backup of the secu zone.
Thomas, the log file does not show why there is a problem here, and because the ASZ is a FAT32 type partition, this is why there are so many AAB??.TIB files shown in the log, because of the 4GB file size limit of FAT32.
I would recommend trying to isolate this issue to see which of your two source drives in causing the backup size to be so large?
If you have an external backup drive you can use, then make a separate backup of each disk drive separately.
One possible reason for this issue is if 'Sector-by-Sector' method is being used for the backup - this can be because you selected this for the Advanced Options page 'Image creation mode' or else can be used by ATI if bad sectors are detected on one of the disk drives.
Hello.
Sorry I am a little bit late.
I will do separate Backup for Disc C (System) and D (Data)
Sector by sector is not activatet.
I dont know if there are bad sectors. How can I find them, good old chkdsk?
Thomas, CHKDSK /R is one method for checking for any bad sectors but will only work with partitions that have been allocated a drive letter, so won't check any hidden / system partitions for errors (but these are normally very small size anyway, so shouldn't be a factor here).
Hello.
I send the result of the test with separate backups of the two disks. Ther were no changes between th full and the incremental backup.
Disc C seems to be normal
Disc D is abnormal big in my eys, no idea why.
Chkdsk didn´t find any problem on disk d.
I send the directory of the secu zone of the incremental backup od disc d, on whitch i installed the secu zone.
Is it possible that ATI backups the secu zone during the incremental backup.
It backups itself?
Why can this happen and what can I do against it?
Thomas, if you are seeing the ASZ within your backup image, then this begs a further question:
What Exclusions do you have for this backup task? Normally all .tib & .tibx files are excluded by default, so should exclude such files held in the ASZ.
When I select my own disk drive which has an ASZ partition, this does not show in the Source list for a Disks & Partitions backup, so I would expect that Acronis would ignore it, but if not, then the default exclusions should prevent any backup files being included.
I controlled the exclusions.
*.tib and *.tibx are excluded.
Thomas, in your backup image, if you click on the ACRONIS SZ item to see the contents, what do you see within it?
Next, for this backup task, what exactly have you selected as the Source - are you selecting the whole D: drive or are you just selecting your Data partition from that drive?
I includet wat I see in the folder ASZ
I can not look into those files
I selectet Drive D
As I did since ATI 9
Thomas, ok, I just made a test full disk backup of my external Seagate drive which also has an ASZ with .tib files within, along with multiple .tib / .tibx files in folders on the NTFS partition on the drive.
When choosing the Source drive, there was no mention or evidence of the ASZ even when selecting to show hidden partitions!
The backup was successful and rather than being over 400GB (if including all the ATI tib contents of the drive) it was only 48GB in size.
However, when I open the Recovery page for this backup task, it does show the Acronis SZ and within this, a 1.2GB .tib backup archive file! So the Exclusions are applied for files in the main NTFS partition but ignored for those in the ASZ on that drive!
Please open a Support Case direct with Acronis Support for this Thomas and I will do the same with a reference to this forum topic too.
Support Case # 04196401 now open and files submitted to Acronis (Balachander) including a System Report zip file and lots of screen images etc.
Received the following update from Acronis development for my support ticket # 04196401
This is Kristina Kalugina from Acronis Customer Central.I have checked the status of the internal ticket regarding backup in Acronis Secure Zone and I have discussed it with the development team.
Unfortunately the issue has not been fixed in the recent update because according to our statistics the issue is minor and not many users have Acronis Secure Zone. The priority of the task has been decreased. The issue is supposed to be fixed in one of the next versions of Acronis True Image and we will get back to you once the fix is available.
I have replied with the comments shown below:
Sorry but I fail to understand how this issue can be deemed to be minor when it increases the size of any disk backups for any drive that has an Acronis Secure Zone because all .tib files from the ASZ are not excluded, despite the backup task Exclusions being set (as default) to do so?
Other users are coming to the forums with issues related to ASZ and often have the ASZ on their OS drive, so any backup being created of that OS drive could literally result in a recursive backup of both the drive and the ASZ .tib files including the new .tib file being created if the destination is the ASZ.
This needs to be fixed for ATI 2020 in a further new build, not in ATI 2021 or later.
To be honest, with all the issues being reported for ATI 2020 in the forums, this is likely to be yet another reason why users will abandon using Acronis True Image and look for a competitor product.
15479: Acronis Backup to Cloud: Disk Defragmentation Is Not Recommended
That is correct as the backup is done on a sector-by-sector basis. Same applies to local disk and partition backups. Only relevant to mechanical drives; SSD are do not need to be defragmented; they need to have trim run regularly - that does not change the sector location of data, unlike defragmentation.
Ian