Aller au contenu principal

Why is Acronis 2021 (Build 39216) so slow? Can I Image a Linux Mint 20.2 Partitions?

Thread needs solution

Hi All,
I have been using Acronis for donkey years now.
I have been stuck with Acronis True Image 2019 (Build 14110)
The reason for that is, if it’s not broke why fix it?
It does exactly what I want it to do!
The other day I came to try out:
Acronis True Image 2021 (Build 39216)
I could not believe how slow it had become,
so I did a benchmark test on both of them.

1.
Acronis True Image 2019 (Build 14110)
Takes 3 Minutes to do a backup to the SSD
Acronis True Image 2019 (Build 14110)
takes 2 Minutes 32 Seconds to Validate the same Image.

Size of Backup is 107 GB
Source Drive: Samsung 960 EVO 1TB M.2-2280 SSD
Destination Drive: SanDisk SDSSDXPS960G   SSD 1TB

2.
Acronis True Image 2021 (Build 39216)
Takes 8 Minutes 30 Seconds to do a back up to the SSD.
Acronis True Image 2021 (Build 39216)
takes 6 minutes to Validate the same Image.

Size of Backup is 107 GB
Source Drive: Samsung 960 EVO 1TB M.2-2280 SSD
Destination Drive: SanDisk SDSSDXPS960G   SSD 1TB

Could somebody who is knowledgeable, and in the know
explain to me what is going on here?
The benchmark results look very bad, shocking!!

3.
I would like to ask a second question while I am here:
Can I use Acronis 2021 (Build 39216) to image a boot partition (all of the drive).
It is a Linux Mint version 20.2 installation on the drive?

I know Acronis True Image 2019 (Build 14110)
turns it's nose up at it, that is why I was going to try
Acronis 2021 (Build 39216)

Thanks all, for your help and advise.............

 

0 Users found this helpful

George George,

The application has changed significantly between 2019 and 2021.  These changes have caused backup and validation times to increase as you note.  The 2020 and 2021 applications perform new functions during backup that 2019 does not.  Disk and filesystem health check is now a part of the backup process.  Metadata is also generated and stored during the backup.  These processes are designed to enhance the reliability of the produced image file itself and to reduce errors overall.  If you watch the backup screen during the running of a backup task you will note that Processing and Calculating time consume the lions share of the backup process.  The actual file creation is unchanged from the 2019 version in relative terms.

In regards to your Linux Mint question, the bigger question is what filesystem are you using here, ext 4 or XFS?

True Image supports the Ext 4 filesystem but not XFS.  Having said that you can image a disk with a non supported filesystem by using Sector by Sector mode in the product.

Look below for more:

Ext 4 support

Filesystem support

Hi Enchantech,

Thank you for your detailed explanation. Very informative.

To answer your question the Linux Mint 20.2 filing system is

formated in ext 4.

Also I was not running Acronis from a windows 10 installation .

I was running it from a USB self Booting device...

But I don't think that would have changed your advice you gave in your answer would it?

Cheers

 

No it does not change my answer as long as the True Image product used to create the boot device is one of the products listed at the top of kb 6045.  If boot device media was created from another version of the product then you should use the Sector by Sector method.

Thank you for the Link to  kb 6045.
I found it very informative, especially to Link to
1543: Creating a Sector-By-Sector Backup with Acronis Products.
I have both:
Acronis True Image 2019 (Build 14110)
Acronis True Image 2021 (Build 39216)
I do not have enough storage space to do a sector-by-sector backup.
If I go ahead and make a standard Image/backup, am I likely to end up with a failure to complete the task or end up with a bad image that will not restore?
It is my first-time using Linux system, that is why I am unsure in what the outcome will/would be! I just fancied exploring my horizons in trying Linux out. I have a lot to learn!
My primary O/S is Windows 10.
Cheers...

If you create the Linux based rescue media for ATI 2021 and use this to create your backup of your EXT4 Linux partitions / drive, then there should be no issues which would require using sector-by-sector backup mode.  Earlier versions of ATI had issues in recognising EXT4 partitions correctly (which was fixed in later builds of ATI 2020) but is present in ATI 2019.

The key test you need to perform is to check that you are able to see both the Source & Target SSD's when booted from the Linux media, as if not, it would suggest that it does not have the required device drivers for these, and that would need you to create WinPE media using the Windows 10 ADK (on a Windows PC).

I have used ATI to image Ubuntu 21.04 and 20.04 builds with no issues.

If you are running a dual-boot system with Windows 10 as your primary OS, then you can backup (and restore) any Linux partitions using the ATI 2021 Windows GUI application just as you would any other Windows partition.  I have done this successfully over the years when I was using dual-boot with Ubuntu, though these days I use VMware Workstation 16 Player and run Ubuntu in a Virtual Machine from within Windows 10.  Using VM's allows me to use a synchronisation program to simply copy the folders holding my VM's to an external backup drive (when the VM's are shutdown) without needing to use ATI at all for backups.  I just use ATI to backup my stand-alone Linux PC's (mainly older laptops that don't run or like Windows 10..!).

Thank you, Steve for the information,
It was well appreciated. A nice read.
Cheers.

Thank you Steve, for the You Tube Demo Video.....