Skip to main content

ATI 2020 Slow Backups

Thread needs solution

I've seen a number of postings on slow validates due to tibx validating the entire chain. My issue is different as I only do Full Backups and my speed affects both the backup and the validate functions. I backup daily in the middle of the night when the system is idle. I'm only backing up 100GB to a USB drive using standard compression. The OS is Windows 10. My first few backups using the tibx file format were very fast but progressively became slower with each successive backup.

The numbers below are from the Activity Logs.

Date Speed Mbps Backup Mins. Validate Mins.

11/4/2019 565 12 26

11/6/2019 560 13 42

11/11/2019 394 17 59

11/12/2019 331 20 68

11/14/2019 226 29 87

11/17/2019 189 35 80

11/21/2019 113 59 109

11/27/2019 125 55 116

NEW BU 11/27/2019 535 12 9

I seem to have found a workaround: I created a new Backup Plan using the same settings, just a different name. As you can see in the chart under NEW BU I'm back to blazing speed but suspect it will gradually decline as did the previous job. I'll post updates. Anyone have thoughts? Thanks, Tom

0 Users found this helpful

Tom, take a read of forum topic: Full Backups no independent entity - which may offer you a solution here until the underlying performance issue is addressed.  There is a powershell script as a file attachment in that topic which can be used as a Post Command to copy each new Full .tibx file to a different folder and trigger a new full on the next run.

Thanks, Steve.

That explains the gradually increasing validate time but why does my backup speed decline from 565 Mbps to 125 Mbps and the backup time increase from 11 mins. to 55 mins. over the course of about 20 backups?

Tom, my understanding is that the time increases simply because of extra processing being done to identify what is changed between the original Full backup and subsequent execution of the task, so the more backups, the more time may be needed. 

There have been a fair number of users complaining about this which is directly related to the introduction of the new .tibx file format and how that is handled.

Keeping the number of incrementals or differentials low before making a new Full backup, and keeping the number of version chains stored low can help with this issue but obviously isn't ideal if a different approach has been practised with earlier versions of ATI.

Thanks again, Steve. That's been helpfull. 

Looking forward to the fix.

 

Tom

Steve,

I tried testing Restore of single files from my bootable USB Archive drive. After selecting the version, the destination folder and the file to be restored I clicked proceed, the progress screen comes up indicating it's restoring but nothing happens. I tried three different files from three different versions one at a time, all under 30 KB, and let it process for up to an hour - nothing happens.

I've been using ATI for at least ten years, until now it's served me well, but I've lost all confidence in 2020. After all the untold hour I've spent attemtping to get to backup to work it now appears I can't restore from it.

Tom

 

 

Tom, how are you doing the restore here?  Are you using the main ATI 2020 GUI and the Recovery panels, or are you doing this from Explorer by double-clicking on the archive file?

Steve,

The ATI 2020 GUI Recovery via bootable media on the same USB drive the backup versions reside.

Tom, just tested recovering a couple of different small folders from a full disk image backup via the MVP WinPE rescue media and all worked just fine as shown by the attached screen images.

Attachment Size
522230-176927.jpg 46.15 KB
522230-176930.jpg 63.52 KB
522230-176933.jpg 33.43 KB
522230-176936.jpg 43.26 KB
522230-176939.jpg 36.8 KB
522230-176942.jpg 56.42 KB
522230-176945.jpg 58.53 KB
522230-176948.jpg 37.73 KB
522230-176951.jpg 20.45 KB
522230-176954.jpg 7.9 KB