Skip to main content

TM now compressing even when compression set to "none"?

Thread needs solution

My C drive (win10 OS etc.) backup file size is nearly 30% smaller than it should be (560GB instead of the 770GB that TM says the size is expected to be, and that is the actual used space windows reports). I always have NO compression, NO exclusions set, and I never saw this discrepancy with TM2013. 

Acronis support have said TM backup compresses even if it is set to "none"! But I find it unbelievable that it could reduce the backup size by over 200GB, given that most of my files on that drive are not compressible in my experience. 

Unfortunately I do not have a spare 1TB drive to recover the backup to and check...

Any comments?

0 Users found this helpful

If you have the latest ATI 2018 build #12510 then Acronis will exclude all OneDrive contents regardless of whether this is shown in the exclusions page or not.

It is also possible that other files/folders may be excluded, i.e. system files pagefile.sys, swapfile.sys, hiberfil.sys which would all be rebuilt automatically by Windows on start-up, plus the System Volume Information folders (which hold restore point data) are normally set to be excluded - all of which can add up a significant size of data.

Personally I would expect ATI to use some form of compression when saving data to the image .tib container file as it would be inefficient and wasteful to store data which can be compressed to a fraction of its size, i.e. text type files with lots of 'white space' etc.

Thanks for the info. The size of my Onedrive + restore points + pagefile would explain the huge discrepancy. I can confirm that my Onedrive folder is NOT in my "full" disk backup.

However I was really hoping my Onedrive folder would be included in the backup, as Onedrive is useful for keeping things easy to access, but useless as a backup because it is synced, so unwanted changes/deletions can't be recovered (although it has a recycle bin). Excluding it must be something Acronis implemented after 2013, and so now more features that I'm missing from before... 

I suppose the solution for Onedrive is to run a separate TM file/folder backup of it, and I will have to see how to do that for the restore points too.

It would seem to me that if my system becomes unstable/broken and I need to restore the OS that is exactly when I might need the restore points to roll back to a stable point!

In fact I find it incredible that a whole disk backup (that is not sector to sector) and set to no compression, is now compressed and excludes the place where Microsoft likes us (and I like) to keep documents  - Onedrive! In no way is this a full disk backup any longer.

Maybe I should be backing up sector-to-sector, but can I run a differential scheme for that backing up to a larger disk that has other data on it? And can a sector-to-sector backup be restored to a different than original sized drive???

I had did many successful OS restores/disk migrations with TM2013 over the years and had a lot of confidence in its features. I'm almost at the point of giving with TM2018. 

JD

 

 

JD, with the latest ATI 2018 build #12510 it is now impossible to make a backup of OneDrive folders as Acronis have disabled the ability to do so while they try to fix the issue of handling the new way OneDrive handles links for remote files (Files OnDemand) via reparse points.

There are many topics in the forum about OneDrive issues and ATI 2018 where this has been discussed in endless depth.