I'm using HDM 15 Pro (paid) I'm trying to restore a 'legacy mode' created archive of a Windows 7-64 OS + apps to a new SSD that's only 5GB smaller than the original. It fails to restore because the target disk is smaller. The original 256 GB Samsung 850 PRO is 5 GB smaller than the 256 GB Samsung 840 EVO I'm trying to restore to. The archive is of a GPT partitioned eUFI disk with one 'C' partition w/OS + apps, which uses 80 GB of space, plus the two small GPT and eUFI partitions to the left. Is there a quick way to restore the backup to the smaller SSD? I've the FAQ's and the KB as well as in the 305 page manual and could not find any clear instructions. If I need to restore partitions individually do I simply perform the restore routine (Legacy mode) as many times as needed to restore the partitions in the order they were create? Thanks for any help. Russell
You could clean the Windows partition with CCleaner, then try to reduce its size with the partition manager included in HDM 15, and reimage.
Hi Robin, Thank you for your suggestions But --- The 4-month old backup (.pbf .pfi extentions) is the Win7 installation on my current (and larger) 256GB Samsung PRO SSD. It seems to be infected with something. I'm trying to restore that 4-month old backup on a slightly smaller 256GB Samsung EVO as I do not own a second 256GB PRO that would be the same size as the backup. I want to retrace some steps to try and reproduce the suspicious error without having any downtime on my working system other than swapping out the two SSD's (I use a mobile rack). When the 'Restore' failed due to the size difference I thought I could just restore the three partitions one at a time. So where is that option hiding? I cannot find any step-by-step instructions on restoring individual partitions in the 300 page+ manual and nothing in the online KB. The manual provides no index at the end to make finding things easy. But it is Easter Egg hunting time isn't it <g> There are two very small GPT volumes + one 238 GB NTFS 'C' volume containing 80GB data and that should easily fit into the 232 GB of unallocatted space on the target EVO SSD. How can I restore that 238 GB and make it fit? There's must be a simple way to do that -- but I've already wasted waaaay too much time guessing at how it's done, and what I've tried so far isn't working. Here's what I see: Russell
I initialized the Drive as GPT, restored the first two (small) partitions and then Apply. Created a new NTFS partition in the remaining space, named it Disk_C, gave the partition a letter (F) and pressed Apply. Closed BR15. Used Windows Disk Management to assign a letter (F) so it would appear to BR15 when restoring files. Relaunched BR15, opened the archive, selected all the files inside the Disk_C partition and files and chose Disk_C (F) as the target. Pressed Apply. Here are the errors I'm seeing: What am I doing wrong? Why can I not simply choose the Disk_C (C) partition and restore it with some 'resize to fit' magic applied? Russell
It's now 1 hour later and the progress bar suggests it will be another 2 hours to completion. I'm doing it on a second computer so I don't care that it's taking so long. But it is very surprising that restoring the same Backup in the usual manner takes only 10-15 minutes whereas doing a file restore takes hours and results in error messages. I'll find out when it's done if it worked. If worse comes to worse I'll fix any boot problems using the Win7 install disk or try out the Paragon Boot Corrector utility. Still suspecting there must be an easier way ...
Hi Robin, You were on the right track with the best solution. 1) Restored the backup to a larger drive 2) Booted it and used Win7's Disk Management utility to shrink the DiskC partition 3) Created a new backup with the smaller partitions 4) Restored that backup to the slightly smaller SSD It was a bit of work but it worked without any problems and was a LOT faster than the restore files route which took many hours and would not boot without repairing with Paragon's tool or the Win7 install disk. Everything is now working just fine. Thank you
