Trouble Making Image Backup with Acronia True Image 2016 -- apparent misread of space

Anonymous
2020-06-18T23:54:58+00:00

I have been trying for days now to make a backup image of my internal Windows 10 hard drive, fully updated to current Windows 10 level May 2020. I have been using Acronis True Image 2016, as I always do. I have been backing up to an external, USB2 connected hard drive with 160 GB of free space on it (a 320 GB hard drive), the same drive I normally backup to. This is a Gateway laptop, NE56R from 2012, which shipped with Windows 8.

I have been trying to backup all partitions, including the C, and recovery partitions (including the Push Button one, which is about 15 GB) and whatever others are there. In total, they are about 109 GB. So I ought to have plenty enough free space.

I have checked all partitions to back up with True Image. It runs the whole backup, takes a good five hours. At the end, it throws up amessage saying ther eis not enough space for the image.

I have never had this problem before. The machine is booted from the True Image disk, so that should rule out some issue wiht my Widows 10 OS. I am doing a full disk backup, and I am even using Maximum Compression, which is what I always use, so I should need something lessthatn 109 GB of free space. and Ihave 160 GB of free space on the external drive.

I have a backup of Win 10 I made in April, shortly before the new OS level cam out on the drive -- I always keep two, just because. I deleted the older of the two on there, so now have only the one. I certainly don't want to delete the one on there, and still have this problem but no backup at all. But Ihave more free space than shudbe needed.

The external drive has been used only for backups since I started using it brand new, and I make a backup once or twice a year -- and I have been using it no more than four years. So, the external drive has very little, hardly any actual use on it, it is not far from brand new.

I read something this morning about a real problem found in the new Win 10 update, something to do with Storage Space, that is some sort of function in the OS now. I don't know what that is, or what it does. But the story said if your drive is not showing as RAW, then it should be OK, not affected. I checked Disk Management, and none of my volumes nor the external drive are marked as RAW. So, that should mean that issue is not the case here.

I have done enough backups in the past four years using the Acronis True Image 2016 software. It has always worked fine, and actually with less free space (I had another item on the drive too, but have deleted it. I also have deleterd about 32 GB of stuff from my C drive in an attempt to make this backup fit, but to no avail -- that is, my last two backups were actually larger than this one, and they fit fine.)

So, why do I keep getting the message about not enough space? I should have way more than enough.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

270 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-08-02T19:08:32+00:00

    I just completed a new backup image of the full drive, all partitions. So, were are backed up, if needed, we can restore to this point from the backup. And I also did that restore point, but that might be C drive only.

    When I hear from you about getting the DIMM via using the partition number rather than assigning a letter, I will do that.

    And then we can see how to proceed.

    Backup image came in about 4 GB smaller than the one from a week ago. Maybe becuse of no bad sectors on part 5 now, although I don't know how much size those things that got deleted via BCD might have taken up, but I doubt 4 GB. Backup still had to be Sector-by-Sector becuse of the bad sectors on part 6, and that makes it somewhat larger than it woud be otherwise.

    BTW, your comment about getting space moved between sectors, I might be able to basically leap frog over partitions by using Partition Wizard. That's what I did early on. I don't know if it actually leapfrogs behind the scenes, probably uses code to move it from one partition to the next until it gets to the destination.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-02T16:03:31+00:00

    Some feedback given and sought. I just made a restore point of the computer. Except maybe it is C: only. Look at this pic, do you think it is C and maybe Push Button only, or is it everything, or maybe even C: only? And, I note, it says Push Button protection is off. Does that mean anything to us? (And then under it, look at the next comment and pic.)

    And then there is a way to create a recovery drive. Is that what we have for part 6, a recovery partition? Is so, would this be useful in dealing with part 6? Maybe this would make the file but with win 10? Of course, I don't think with the gateway stuff.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-02T13:52:47+00:00

    I’ll do the DISM this morning. Use the command:

    DISM  /Get-WimInfo  /WimFile:X:\RecoveryImage\Install.wim  /Index:1

    We were able to use partition number instead of putting on letters for that thing we did yesterday from Advanced Startup. How about we do same for this stuff too, to avoid the issue we had with the R on part 5. Just identify it as part 6, rather than putting an X on it?

    How would we do that? Maybe first go identify Part 6 as what we are working on, then:

    DISM  /Get-WimInfo  /WimFile: \RecoveryImage\Install.wim  /Index:1

    Note, no identity of what partition, we already entered it with another command. Or, we put in part 6:

    DISM  /Get-WimInfo  /WimFile:Part 6\RecoveryImage\Install.wim  /Index:1

    Maybe you can correct how we do that, then I will run that for the DISM.

    We got a bit lucky yesterday with fixing the letter issue. Let’s not run into that again, and we now have cleared those files from BCD, so those are no longer available to delete in order to force BCD to re-whatever.

    Yes, I can male a backup of the drive today. Although, don’t we need only a backup of part 6? But I already have that on the last backup I did.

    I also can make a restore point. Will do that, that should accomplish the same, is fast and easy to do too. But not sure, will that create a restore point of C only?

    Will take some hours to do the full backup. Will have to first erase the one from a few weeks ago.

    Yes, full restore, then if we do part 6 and it screws up, we can restore the backup. A pain in the neck, but that is the only certain way to cover our ****.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-02T04:31:15+00:00

    To get an actual partition 7, we'd have to move both 5 & 6 leftward into space C:partition now occupies. But we're not quite absolutely positive yet that wouldn't mess the space up. Are you willing to risk it?

    Otherwise, we'd be creating a new partition 5 (not a 7) into space grabbed from C:. In that case, partitions 5 & 6 get bumped to 6 & 7. I think the current Partition 5 self-adjusts its status as the RE location, anyway we can reestablish it. But I don't know what happens to the current Partition 6. If it loses its status as the recovery image location -- it's no longer a test. It's for real that ReagentC will have to work.

    And the whole thing is a bunch of extra work with commands I won't be able to test. I think a better idea is to do it for real the first time -- just make a system image first. That's what they are for.

    What about that DISM I asked for? Let's see that Install.wim.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-02T04:05:36+00:00

    I was thinking of creating a part 7, bring that file over to it, maybe with that command. See if it worked. Try to avoid the letter issue from part 5, maybe don't assign a letter to it, use the exiting part number to identify it.

    Was this answer helpful?

    0 comments