Home AOMEI Products Support

why does incremental backup takes such a long time?

edited February 2017 in AOMEI Products Support


I use Backupper Professional to make backups from my separtate data-drive.

The drive is 900GB whereoff 408 GB is used for actual data.

When I doe an incremental backup this takes a very long time > 1hr, even when no dat has changed.

I would think that this should only take a few seconds while searching with Windows Explorer for files changed after a certain date only takes 1 second!

It looks like Backupper checks the whole drive for changed databloks and does not use indexes for changed files.


  • 1. What is your desination? 

    Is it NAS? 

    2. Is it the first incremental? 

    If yes, please run the incremental backup again to check if you have the same problem.

     3, Did you set it to check the backup image after finish the backup?

    If yes, please do not choose it.It will take long time to do the the check.

  • 1. USB WD Elements HD-drive 2TB

    2. Second time incrmental indeed is an incremental, filesize is much smaller

    3. Check image is NOT set.

    Backup second incremental, with no files changed, took 1hr 15 min to complete!

    Don't understand why this takes so long. Its very dissappointing.

  • Are you running defrags on your hard drive? If so, this could increase the time required for an incremental.

  • @jecherp  Yes, it will take long time to check the whole disk to find the changed data. Please run the incremental backup again, hwn you get the third or fourth imcremental backup image, it will take less time to do the backup. Sorry for the inconvenience.

  • @admin If I have a schedule to make 1 full backup and then 6 incrementals, after which I start again with 1 full backup (space management) will the new first incremental backup take again such a very long time? 
    Why the incremental backup does not use the timestamps of altered files to establish the file to be backedup?

  • @admin Todays 4th backup ( 3 incremental) takes another 1hr and 15 min.!

  • Please send us the whole log folder and the screenshot of the "view log"(advanced---properities---view log) to us. We need to find the problem.

  • send them by Email as reply on your mail

  • Perhaps something is wrong here? 

    This comes from eventviewer

    "Kan bestandssysteemfilter 'wcifs' (versie 10.0, ‎2016‎-‎09‎-‎15T17:42:03.000000000Z) niet aan volume '\Device\HarddiskVolumeShadowCopy10' koppelen. Een ongebruikelijke uiteindelijke status 0xC000000D is geretourneerd. Dit filter en/of de bijbehorende toepassingen moeten deze toestand kunnen verwerken. Neem contact op met het leverancier als de toestand zich blijft voordoen."

  • Is that the software failed to enable the VSS? Did you do the backup sucessfully.

  • backup succeeded, allthough again it took a very long time > 1,25 hr. 

  • The backup ended succesfully. Took > 1.25 hrs. I can see in the backup popup screen that Backupper is "processing data: 177,45 GB/513,96 GB Speed 123,34 MB/s remaining: 46 min" So it looks like all blocks are processed individually, regardless of state (changed/unchanged). This take more then 1.25 hrs every time.

  • I know this is an old topic.

    I too have this same issue where an incremental back-up will take a long time.  I am backing up my NAS drive so it takes about 15 hours on a full backup.  The program is incremental backups take the same amount of time.  This makes no sense as this is not it should not take this long.  The software seems to be programmed inefficiently if it looks at each and every file to determine if it should be added ot the incremental back-up file.

    Given that I just paid for a license, this is dissapointing.  I hope someone can come up with a solution. 

  • Switches to Patapon backup. Works vast Android reliable

  • Damn  autocorrection!  Switched  to Paragon backup.  Works fast and  reliable 

  • So incremental backups seem to be talking longer than they should for me as well.  For an increment file size of about 600MB, it's consistently taking about 50 minutes to backup on Win10 with no user apps running.  The full backup created a 55GB file in 2 hours and 20 minutes, so the increment takes less time than the full, but is way way slower in terms of minutes per GB backed up.  Is this about the best I can expect for a Backuppper incremental backup?

  • @Hoot We will try to improve this feature in future versions.

  • perhaps you should revisit how you look for changed files. companies such as calsoft sell change block tracking drivers that'll allow an order of magnitude performance improvement. brute force scanning the filesystem is *painful*..

  • Did you try disabling the anti-virus? I have paraceted problem with Microsoft and Kaspersky Free. This happens to me only with file backup.

    When it starts takes forever to scan, but by disabling the protections of these anti-virus follows normally.

Sign In or Register to comment.