Aller au contenu principal

Acronis Images are different sizes?

Thread needs solution

So here is the mystery for me:

My Dell Widows 10 Laptop has a single disk configured as such

Partition: OS9(C:) 918GB   39GB Used

Partition: EFI Healthy System Partiion  500MB Used

Partition: Healthy Recovery Partition 450MB Used

Partition: Healthy  recovery Partition  12 GB Used

When I create an image (Acronis True Image 2017 normal compression) with the installed Acronis program on my laptop, I select all the of the above partitions on the C:\ drive. I do not select "Entire PC" as my source. The image created is good, and I can see all the partitions in the recovery process. The image size is 68GB.

When I used the Boxed Acronis Installation DVD to boot the computer and create the image, I also choose all the partitions in the C:\ drive. The image appears to be good and I can also see all the partitions in the recovery process. The image size is 32GB.

Why the discrepansy in size between the two methods?? Both images appear to be bullet-proof. 

 

 

0 Users found this helpful

Steve, difficult to explain without access to more information.

The offline backup size of 32GB sounds to be more what I would expect for the partition sizes quoted, assuming that files such as the pagefile.sys, hiberfil.sys and swapfile.sys are also excluded from the backup.

Can you post a copy of the full log file for the Windows backup task that created the 68GB backup file.  You can get this via the MVP Log Viewer and post as a text file attachment.

Exactly where is this MVP viewer?

Steve, see my signature for the link.

Yes, I see those entries in your post. I wll have to do that tonight.

Thanks

OK so that was fun.

So here is the extact from the small image log file"

XXXX2_CPartiion.tib Compression: Normal Exclude: Files matching mask Match criterion:
          hiberfil.sys
          pagefile.sys
          $Recycle.Bin
          swapfile.sys
          System Volume Information
          *.tib
          *.tib.metadata
          *.~
          *.tmp
          C:\Users\defaultuser0\AppData\Local\Temp
          C:\Users\STEVE\AppData\Local\Temp
          C:\Users\defaultuser0\AppData\Local\Microsoft\Windows\INetCache
          C:\Users\STEVE\AppData\Local\Microsoft\Windows\INetCache
          C:\Users\STEVE\AppData\Local\Google\Chrome\User Data\Default\Cache
          C:\Users\STEVE\AppData\Local\Opera Software
          C:\Users\STEVE\AppData\Local\Mozilla\Firefox\Profiles
          C:\Users\STEVE\AppData\Local\Google\Chrome\User Data\Default\Cache
          C:\Users\STEVE\AppData\Local\Opera Software
          C:\Users\STEVE\AppData\Local\Mozilla\Firefox\Profiles
          C:\Windows\CSC
          C:\Users\Administrator\AppData\Local\Temp
          C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache

 

NONE of these exclusions appear in the log file of the large image.

Is that the problem.? Apparantly,

I looked at the setting for EXCLUSIONS on the installed verion. The "Files matching the following criteria" was not checked.

Any comment on that.

Steve, difficult to say why the option to exclude files matching the set criteria wasn't checked - it could be left over from how it was set on an earlier version or simply got 'knocked' when looking at settings then saved like that?

I guess the real test is to run the backup again with the exclusions enabled and see if the size is more in the region of the 32GB one rather as large as the 68GB one!

Yes, I am finishing that now. It seems that my online version always sets the "sector-by-sector" flag as a default. So I have to make sure that the excusions and sector.. flags are set properly.

So this online image came out to be 31 GB.

If it had been a snake it woudl have bit me ... and I would have deserved it.

I used up some of your vaualbe time on something that was avoidable.

I thank you again. I will be back.

Steve

Steve, glad to hear that all looks good again. Check that you haven't used 'Set as default' for some of your task settings on any of the pages, as that will then be picked up by any new tasks you create.  I found this when I encrypted one backup task but then clicked on set as default on the Notifications page after which new backups defaulted to being encrypted with the same password as the one where I did the set as default!  Took a short time to work out but quite easy to remedy by setting the desired settings, i.e. no sector-by-sector etc then clicking 'Set as default'.

Good advice. I also noticed that on any new backup the default is always to set a weekly schedule to do the next one. I disable that after the backup is done. One of the querks in my installation is that a backup will not start unless you set a schedule for the next one. I could be wrong and I will check that again.

Thank so much for all, espesially that MVP log viewer.

Steve