New
#41
Understood. I went with defaults. Re-running
Understood. I went with defaults. Re-running
I re-run it and it took 3 hours, examining how it went now. The free disk space went down on F: drive which is good.
I'll have to admit I'm having trouble deciphering your pics. The definition you show on the left does not match the run-time display on the right. 4 partitions on the left, 5 on the right, and they do not totally match.
You covered up almost all of the disk management pic so it's impossible to see.
I can't tell what you are booted to at the time you took the pics and ran the backup.
Awful lot of data in use on your C: (booted) drive, whichever one it is. Do you have Steam or something else huge on there?
I'm sorry, but I'm really having difficulty sorting out from the pics what belongs to what and where you were when you ran the backup. Definitions don't match results, and can't see the whole Disk Management. Could you clean this up some, and explain where you were booted from and what the definition file refers to?
Thanks.
I've realized the center pic shows my disk clones that took place a few days ago and have no relationship to the disk image operation that I did today. Although the disk clones confused me as well, because the source disk and the destination disk do not make any sense. The two disks pictured are both the destination disks.
Now on the right hand side is the disk image operation that run after "Create an Image of the partition(s) required to backup and restore Windows. The size did go up from 402GB to 438GB or so versus choosing the "Image this disk" option that appears directly under each disk that apparently did not encompass the EFI partition.
this is the disk layout and the below is the log from disk imaging (not cloning)
That last definition and result now looks normal, far as I can tell. Still have my question....lot of data on C:. Is that intentional? Is it Steam or something else very big? Remember the Tree Size Free I suggested. If it doesn't need to be backed up along with the OS for recovery, and could be backed up separately, you could save a lot of time.
Getting late for me here, so I'll check in tomorrow morning.
Thanks for the fresh pics.
Well there is a simple explanation for that, C drive has all the operating system stuff and all the user data I have ever accumulated - namely everything. Photos, movies, documents, pdf files, etc and more. Over quarter century.
Some code I've written 25 years ago for operating systems like Ultrix assembly or Pascal that no longer exist in a meaningful way and cannot possibly run. I just hate throwing that away, given how many sleepless nights I've spent on it.
My SSD is the digital equivalent of household hoarders as seen on TV.
And every time I roll all this stuff over from one computer to another, I just create a sub-folder under Documents and throw it there, promising myself someday I will clean it up. Then it repeats itself. It has become recursive.
Just a suggestion but you could get yourself an external drive and move all the folders that you’re “hoarding” to it and then you wouldn’t have to devote so much time to backing it up over and over. Think of how much time you’re devoting to backing up the same stuff over and over. BTW, I totally understand the emotional attachment to keeping old projects, even if you’ll never use them again, it’s part of your history.