How to minimize backup size?

This shows that ATI 2020 #25700 was installed successfully on 23/07 at 22:11 and from the installer log entries, only took a few minutes to do so!

> I never said install was a problem on this device, just that it involved 3 different updates (1x2019 and 2x2010) before it finished and that the only way to activate was to type the license number.

The backup logs show logs for 3 different backup tasks of which only one task is still present in the Scripts folder and was created originally on ATI 2019 #17750, so even though is a disk backup task, will always continue using .tib backup files, not .tibx files.

> Does this mean I cannot delete an ATI 2019 task and replace it with one created for the same drive in 2010?

MyBackup was created by ATI 2020 but looks to have been deleted.  This backup looks to have been going to a network destination (\\Ml310e\k\).

> This was my test of a separate disk never backed up before  in ATI. It is my main question that it too was not .tibx and is the reason why it was deleted.

One factor that might make the initial launch of ATI to take longer on your desktop system is the number of installed disk drives along with mapped network locations, which ATI will try to scan for any existing backup .tib / .tibx files.

> This is quite normal in a PC with several disk drives (internal + USB3) and a significant number of network locations. Why should this be a problem?

One other issue is shown in the msinfo32 report data under the heading Components > Problem Devices where it lists your G: I: J: and H: drive letters associated with what looks like a multi-function card reader device.  This could also cause ATI to hang if it tries to access these drive letters!

> Multicard reader is quite common on HP desktops, why should ATI not cope with it?

Tom, please see my separate private message reply to you ref this desktop computer.

Steve, please check my PM with the other system reports / progress

The other system reports (zip files) are received & will take a look later as time allows.

Maureen laptop:
2 internal disk drives.
Win 7 Pro SP1 64-bit. Legacy BIOS boot mode.
ATI 2019 #17750 activated license. 

Tasks:
Maureen E: to network location - failed last 6 attempts due to destination unavailable.
Maureen-Laptop: to network location - successful backups as .tib files.

No Installer logs present to show any attempts to upgrade from 2019 to 2020.

Tom laptop:
2 internal disk drives plus Micro SD card using exFAT format.
Win 7 Pro SP1 64-bit. Legacy BIOS boot mode.
ATI 2020 #25700 activated license.

Tasks:B
tom-laptopPC E: to network location - successful backups as .tib files.

Installer logs shows successful install of ATI 2020 on 26/07 15:10.

The script file for the above task shows no indication of any attempt to use .tibx format.

Tom, just to clarify a point per my latest PM to you.

.tibx files are only created by new Disks & Partitions type backup tasks in ATI 2020 & beyond.

.tib files are used for all older backup tasks brought forward from earlier versions of ATI such as 2019 etc, and also still used by all Files & Folders type backup tasks in all versions.

Your system report files do not show you creating any new Disks & Partitions type backups which is why only .tib files are being created.

Tom wrote (in a pm):

The whole reason for upgrading to 2020 was to use .tibx instead of .tib and at no stage was there any limitation like this mentioned.

My understanding was that I need to use Files and Folders so I can recover individual files when needed, as well as replace / rebuild entire disks. Also that using Disks and Partitions does not allow this.

If this is so, I cannot use Acronis.

Tom, you can recover individual files or folders from both disk backups and the files & folders ones.  This has always been possible and hasn't changed in ATI 2020.

See KB 63240: Acronis True Image 2020: how to restore files from a backup (Windows) - and scroll down the document to the section showing how to open .tibx or .tib files in Explorer by double-clicking on the files.

There are pinned topics in the ATI 2020 Forum giving important information about the limitations of the new .tibx files, so this has been published and declared since 2020 was first introduced.

See the following KB documents published by Acronis with regards to .tibx files.

KB 63518: Acronis True Image 2020: do not delete first tibx file

KB 63227: Acronis True Image: Do not delete .TIB or .TIBX files outside of Acronis True Image

KB 63498: Acronis True Image 2020: new tibx backup format FAQ

KB 63425: Acronis True Image 2020: Limitations of tibx backups

KB 63516: Acronis True Image 2020: Incremental backups do not create separate files when using new backup format

KB 63445: Acronis True Image 2020: how to view and manage backup versions in new backup format

KB 63444: Acronis True Image 2020: tibx backups in local destinations

Thanks. I am sure that all you say is correct, but it does not align with the messages given above and in the user manual, if anything is said at all. Users cannot be expected to search through knowledge bases to understand how to use a product. It seems that there is no benefit is using Files and Folders.

I can say that today I created a disks & partitions task which was indeed .tibx but stopped very quickly saying resource was not available, so I immediately started the existing disks & folders .tib backup from exactly the same source to exactly the same destination. It is running without problems.

When this finished,I will try the .tibx again and if no success, can I revert to my 2019 Perpetual license which has given few problems and .tib does not have the restrictions mentioned in the 2020 releases notes.?

Tom, a full disk recovery can only be done successfully from a Disks & Partitions backup image (.tib or .tibx).  Files & Folders backups are fine when that is exactly what you want to backup & recover, but do not work for the C: OS drive and locked Windows system files & folders including the Registry files etc.

It would be interesting to see the backup_worker log for your failed .tibx backup attempt where it failed with 'resource not available' to see what the log shows?

Steve Smith wrote:

It would be interesting to see the backup_worker log for your failed .tibx backup attempt where it failed with 'resource not available' to see what the log shows?

What is a backup_worker log and how do I access and / or create it? 

It is one of the logs created when any Disk backup is run and captured in the system report zip files, otherwise is found at C:\ProgramData\Acronis\TrueImageHome\Logs\backup_worker folder.

Latest system report... https://we.tl/t-Fybc4zL6Wu

Tom, thanks for the latest system report zip file for the .tibx issue.

One request please, can you try making a Disk backup to a local destination instead of using your network location (\\?\UNC\Ml310e\k\LaptopPC Backup\) so that we can see if this issue is limited only to network destinations or will show for any .tibx backup task?

The logs show the following errors:

29/07/2020 08:43:13:405 AM +01:00 2640 E000B042B: Error 0xb042b: The network share is inaccessible.
| Path: \\Ml310e\k\LaptopPC Backup\
| error 0x2160015: A backup error.
| function: da_backup::Commit
| error 0x29b138d: Input/output error
| function: archive_stream_write_shbuf
| path: \\?\UNC\Ml310e\k\LaptopPC Backup\/TOM-LAPTOPPC E disk part.tibx
| error 0xfff0: Insufficient system resources exist to complete the requested service.
| path: \\?\UNC\Ml310e\k\LaptopPC Backup\TOM-LAPTOPPC E disk part.tibx
| code: 0x800705aa
29/07/2020 08:43:15:871 AM +01:00 2640 E013C0005: Error 0x13c0005: Operation has completed with errors.

The above is from the ti_demon log, the backup_worker log (extract below) confirms repetitive write errors to the destination location.

29/07/2020 08:43:09:590 AM type=log; level=err; archive close (commit_seq=1, reuse_seq=0, file_size=9970110464, uuid=3ada1a5f55a0c95df60b3a8c8c9ccd6a) rc=-5005 (Input/output error);
29/07/2020 08:43:09:595 AM type=log; level=err; message=image backup: failed to close archive:
29/07/2020 08:43:13:386 AM
type=commonerror;
value=A backup error.
func backup::Commit Input/output error
function archive_stream_write_shbuf
path \\?\UNC\Ml310e\k\LaptopPC Backup\/TOM-LAPTOPPC E disk part.tibx
Insufficient system resources exist to complete the requested service.

Those were indeed the error messages I got. I immediately did 2020 Files and Folders .tib backups of both my data E: drive and OS C: drive to the network location and they ran successfully yesterday with incremental backups overnight and this morning.

At the same time, I also ran a Disks and Partitions backup from my wife's laptop OS and that worked. This laptop is still showing 2019 even though I ran the 2020 install and it has appeared in My Account as an activated 2020 device. Note any previous logged backup failures you have seen have all been because her laptop was away from the house

I will try a local backup, but clearly .tib works without problems, so I need to know how I revert to my Perpetual 2019 license as I have little confidence in .tibx now.

.tibx backup to external USB worked. It is not a sustainable way for long term backup and all .tib backups to the server worked fine, so I want to revert to 2019 Perpetual. How do I do that?

To go back to ATI 2019, you will need to uninstall ATI 2020 fully and do a clean install of 2019 then recreate your backup tasks again.

Note: you shouldn't need to use the Acronis Cleanup tool to do this as you will be reinstalling ATI

Have a copy of your ATI 2019 perpetual license serial available to copy / paste after doing the new install.

Steve Smith wrote:

To go back to ATI 2019, you will need to uninstall ATI 2020 fully and do a clean install of 2019 then recreate your backup tasks again.

Note: you shouldn't need to use the Acronis Cleanup tool to do this as you will be reinstalling ATI

Have a copy of your ATI 2019 perpetual license serial available to copy / paste after doing the new install.

That did not work. The license is still shown as subscription and not Perpetual.

I also tried deactivating the Workstation, running Cleanup (as administrator), re-installing and entering the serial number (instead of signing into the account) but that still resulted in a Subscription.

Which version is showing as being installed in the Account page?

If it shows as ATI 2019, then look for the option to 'Enter serial' and click on that then enter your perpetual license serial data.

Steve Smith wrote:

Which version is showing as being installed in the Account page?

If it shows as ATI 2019, then look for the option to 'Enter serial' and click on that then enter your perpetual license serial data.

 I already entered the Perpetual serial number (see above instead of signing into My Account) with this result....

My Account shows all 3 (out of 5) licences are Subscription and none are 2019 Perpetual

GUI Account shows 2019 (with the Perpetual Serial Number) with 500GB Cloud Storage Subscription.

I also started a Support Case 04528950 giving the same info.

Tom, if your ATI GUI Account page just shows the version number and not one of the premium ATI versions, then it is showing your perpetual license.

I changed my own ATI 2020 from being on my subscription to using a perpetual license and it shows as below:

Note: the Cloud Storage shows as still being subscription because it is only available as such, but the main ATI product doesn't show a subscription version.

That is what I see in the GUI Account but My Account still shows all subscription and no 2019 perpetual activation. See attachment

Tom, you need to be looking at the Account page in the ATI GUI, not on the website.

Perpetual licenses do not show which computers have activated in the web account page and never have done so.

Thanks for clearing that up although how a new user would know escapes me, especially with having 2 Accounts.