Macrium Reflect Free making multiple images?

[Lady Fitzgerald]

One advantage of having C & D partitions on one drive, when I purchased twin HDs, one was C, the other was D, it was easy to clone D-partition, or restore D-partition image, onto its new home, the 2nd HD. I guess one can also do the reverse.

You can, and that is the fastest way to transfer data to replacement drives but, same as imaging, cloning is an inefficient way to backup data drives/partitions (unlike OS and program files, which must be imaged or cloned to work). Both imaging and cloning data for backups requires too much space and takes way too long to do. A folder/file syncing program, such as FreeFileSync, is much more efficient and will result in a backup that is essentially a clone of source drive/partition. When set to mirror mode (not quite the same as RAID 1, btw, which I do not recommend for backups), a folder/file syncing program will compare a source with a destination and then copy and delete files as necessary to make the two essentially identical without altering the source. Since only folders and files that have changed are involved, it takes considerable less time to update a backup than cloning and imaging, which require all data to be dealt with every time a backup is updated.

 

[ignatzatsonic]

In your example of a 100GB partition on a HDD (assuming that is the formatted size) with only 60GB being used, to have 10% headroom on a destination partition, it would need to be at least 67GB formatted space. It never hurts to have more room for future expansion, however.[/I]

I wonder how that intelligent sector thing works in "real life", you should pardon the expression.

Ever had to rely on it working as advertised?

Like restoring a 100 GB partition, with 60 occupied, to an 80 GB disk?

I'm just curious. Offhand, I can't recall anyone on this forum who has done it--or attempted it.

Maybe it's flawless, but I rarely look at Macrium forums where that might be discussed.

 

[Lady Fitzgerald]

In your example of a 100GB partition on a HDD (assuming that is the formatted size) with only 60GB being used, to have 10% headroom on a destination partition, it would need to be at least 67GB formatted space. It never hurts to have more room for future expansion, however.[/I]

I wonder how that intelligent sector thing works in "real life", you should pardon the expression.

Ever had to rely on it working as advertised?

Like restoring a 100 GB partition, with 60 occupied, to an 80 GB disk?

I'm just curious. Offhand, I can't recall anyone on this forum who has done it--or attempted it.

Maybe it's flawless, but I rarely look at Macrium forums where that might be discussed.

The Intelligent Sector thing is a default setting so I strongly suspect everyone here who uses Macrium Reflect has used it, whether they realized it or not, including you. I've never had a problem with it in the two years or so I've been using Macrium Reflect.

 

[ignatzatsonic]

I've never had a problem with it in the two years or so I've been using Macrium Reflect.

Nor have I.

But I know of no one who has attempted (successfully or not) a restore to a drive that was noticeably smaller than the source partition.

Do you?

 

[Lady Fitzgerald]

I've never had a problem with it in the two years or so I've been using Macrium Reflect.

Nor have I.

But I know of no one who has attempted (successfully or not) a restore to a drive that was noticeably smaller than the source partition.

Do you?

Yup! Me! All seriousness aside (?), I did a test sometime back where I restored an image of data I planted on a spare 500GB HDD (I don't remember how big the data was) to a 160GB HDD. It worked just fine.

 

[DavidE]

I had a problem the first time i tried to restore to a smaller partition, and it turned out to be a User error
WHS helped me and explained how to do it here:
http://www.sevenforums.com/backup-r...m-restore-backup-image-smaller-partition.html

 

[GokAy]

I use Acronis TI 2010 Home:

The clone function can be done to a smaller drive as long as used space is smaller than destination. (500GB SSD with 100GB used space cloned to 250GB HDD). I guess it can perform the regular restore function to smaller drive as well.

 

[Lady Fitzgerald]

I use Acronis TI 2010 Home:

The clone function can be done to a smaller drive as long as used space is smaller than destination. (500GB SSD with 100GB used space cloned to 250GB HDD). I guess it can perform the regular restore function to smaller drive as well.

The same is true of Macrium Reflect for both cloning and image restoration (I have done both).

 

[RolandJS]

LadyF, you're right as rain concerning data imaging. However in the context of moving data partition from one location to another location is one good way to go. I average partition imaging once monthly, or maybe every 2-3 weeks. Resplendence has a great undelete program that I use on two computers.

 

[simrick]

Great information everyone. I really appreciate it. This has given me a lot of insight in my quest to avoid re-installation hell in the future! So I'm thinking it will be one or two complete disk images, and then just the C partition on a regular basis. For my data backup, I'm using Crashplan. And, the reason I'm using that, is because I would be able to recover "versions" of my data, should one of those encryption malware ever strike.

So, just to be clear: Let's say my HDD bites the dust. I get a new one (that's at least 10% larger than the used space on the original drive), boot from the WinPE disk, restore the full image, then restore the latest C image, then attach my Crashplan drive and restore the latest versions of my data (unless, of course, they're encrypted, then I would restore to a previous version). Does that sound right?

 

[ignatzatsonic]

So, just to be clear: Let's say my HDD bites the dust. I get a new one (that's at least 10% larger than the used space on the original drive), boot from the WinPE disk, restore the full image, then restore the latest C image, then attach my Crashplan drive and restore the latest versions of my data (unless, of course, they're encrypted, then I would restore to a previous version). Does that sound right?

You may be confused. I'm guessing you are because you say "restore the full image, then restore the latest C image".

What's contained in the so-called "full image" you mention? What partitions does it represent?

To restore Windows and get it running, you need to make and later restore an image file that represents C. You also need to make and later restore an image file of another partition IF, I say IF that other partition contains your boot files. This other partition is typically called "System Reserved", but your boot files can be anywhere, depending on who built the PC.

Let's say your boot files are on System Reserved.

You need to restore both C and System Reserved. So you need to have image files of both partitions.

You could make a single image file containing both partitions or you could make a separate image file for each. If you did the former, you'd presumably make that single image file on some repeating schedule. If you did the latter, you COULD do that repeatedly also, but more likely you'd just make one image of System Reserved and then make repeated images of C according to your schedule.

You can make images of your data partitions if you want, but I'd never fully rely on it.

 

[simrick]

So, just to be clear: Let's say my HDD bites the dust. I get a new one (that's at least 10% larger than the used space on the original drive), boot from the WinPE disk, restore the full image, then restore the latest C image, then attach my Crashplan drive and restore the latest versions of my data (unless, of course, they're encrypted, then I would restore to a previous version). Does that sound right?

You may be confused. I'm guessing you are because you say "restore the full image, then restore the latest C image".

What's contained in the so-called "full image" you mention? What partitions does it represent?

To restore Windows and get it running, you need to make and later restore an image file that represents C. You also need to make and later restore an image file of another partition IF, I say IF that other partition contains your boot files. This other partition is typically called "System Reserved", but your boot files can be anywhere, depending on who built the PC.

Let's say your boot files are on System Reserved.

You need to restore both C and System Reserved. So you need to have image files of both partitions.

You could make a single image file containing both partitions or you could make a separate image file for each. If you did the former, you'd presumably make that single image file on some repeating schedule. If you did the latter, you COULD do that repeatedly also, but more likely you'd just make one image of System Reserved and then make repeated images of C according to your schedule.

You can make images of your data partitions if you want, but I'd never fully rely on it.

The full image I was referring to would be the system reserved and C partitions of my drive - that's all there is on my computer. So I was thinking I make one full image and then subsequent images of C partition. So for this particular system of mine.. I just reinstalled Win8Pro on the new HDD then updated to 8.1...it has System Reserved and C. In Disk Management, it says that Boot is on C: partition. So in this case, could I make one complete image (both partitions) and then just update C on a regular basis?

Then if the boot was on the system reserved partition, I would need to periodically update that image as well? or am I confused....I thought the boot didn't really change...

To further confuse me, on the ASUS W8.1 machine my friend has, there are 8 partitions (ugh!):
unallocated 1MB
win re tools 800MB NTFS
system260MB FAT32
other 128MB reserved
windows C 800.35GB NTFS
D data 112.63GB NTFS
recovery (including install.wim) 17.37GB NTFS
unallocated 7.11KB

I don't have access to it at the moment, so I don't know where the boot files reside. I'm not sure how to tackle this one?

Thanks for your patience with me!

 

[DavidE]

In Disk Management, it says that Boot is on C: partition.

Post a MAXIMIZED screen print of Disk Management
http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

In Disk Management the partition that shows "Boot" is the partition that the Windows OS is installed on, and currently running.
In Disk Management the partition that shows "System/Active" is where the boot code is, used to boot up the correct Windows OS partition.
Yes, it's confusing...

 

[ignatzatsonic]

see comments in bold

The full image I was referring to would be the system reserved and C partitions of my drive - that's all there is on my computer. So I was thinking I make one full image and then subsequent images of C partition. So for this particular system of mine.. I just reinstalled Win8Pro on the new HDD then updated to 8.1...it has System Reserved and C. In Disk Management, it says that Boot is on C: partition. So in this case, could I make one complete image (both partitions) and then just update C on a regular basis?

No, I wouldn't do it that way. Here's the problem with your method. Suppose on May 1 you "make one full image", representing both System Reserved and C. Then on May 10, you make an image of C only. Then on May 20, your drive fails. You'd have to restore the May 1 image, not the newer May 10 image because you don't have an image of System Reserved ONLY. If you restore the May 10 image only, it won't boot because that image file does not include the boot files. You could restore the May 1 image and then immediately restore the May 10 image of C, overwriting the May 1 image of C, but why bother going through 2 restoration procedures? Why complicate a procedure that is shaky to begin with? You can't restore just part of an image file (C but not System Reserved). It's all or none.

Take your pic from the following, either would work:

1: ALWAYS make one image file, containing both C and System Reserved. Each and every time, at whatever schedule you want. Restore this single image file when you have issues.

2: Make an image of System Reserved ONLY. Make another image of C ONLY. Don't make more images of System Reserved unless you do something radical like install a dual boot (2 operating systems). Make periodic new images of C ONLY. When disaster strikes, you restore both images, separately.

Then if the boot was on the system reserved partition, I would need to periodically update that image as well? or am I confused....I thought the boot didn't really change...

"Boot" is never going to be on System Reserved. Boot will always be C. That's where Windows lives. C will be changing constantly. System Reserved will rarely if ever change.

To further confuse me, on the ASUS W8.1 machine my friend has, there are 8 partitions (ugh!):
unallocated 1MB

Unallocated space is NOT a partition. It's unallocated space. Your friend has 6 partitions.

win re tools 800MB NTFS
system260MB FAT32
other 128MB reserved
windows C 800.35GB NTFS
D data 112.63GB NTFS
recovery (including install.wim) 17.37GB NTFS
unallocated 7.11KB

I don't have access to it at the moment, so I don't know where the boot files reside. I'm not sure how to tackle this one?

You'd need to look at his Windows Disk Management to decipher things. He'd need to restore C and whatever partition is marked as "system" in order to recover from a drive failure. He COULD restore additional partitions, but they wouldn't be required to get back to a bootable Windows.

 

[simrick]

In Disk Management, it says that Boot is on C: partition.

Post a MAXIMIZED screen print of Disk Management
http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

In Disk Management the partition that shows "Boot" is the partition that the Windows OS is installed on, and currently running.
In Disk Management the partition that shows "System/Active" is where the boot code is, used to boot up the correct Windows OS partition.
Yes, it's confusing...

YES! Confusing! LOL

 

[simrick]

2: Make an image of System Reserved ONLY. Make another image of C ONLY. Don't make more images of System Reserved unless you do something radical like install a dual boot (2 operating systems). Make periodic new images of C ONLY. When disaster strikes, you restore both images, separately.

"Boot" is never going to be on System Reserved. Boot will always be C. That's where Windows lives. C will be changing constantly. System Reserved will rarely if ever change.

Yes, option #2 makes sense to me now. Thanks for that.

Unallocated space is NOT a partition. It's unallocated space. Your friend has 6 partitions...

You'd need to look at his Windows Disk Management to decipher things. He'd need to restore C and whatever partition is marked as "system" in order to recover from a drive failure. He COULD restore additional partitions, but they wouldn't be required to get back to a bootable Windows.

I will have access to it later next week. I'll have a look and report back. Thanks!

 

[simrick]

see comments in bold

You'd need to look at his Windows Disk Management to decipher things. He'd need to restore C and whatever partition is marked as "system" in order to recover from a drive failure. He COULD restore additional partitions, but they wouldn't be required to get back to a bootable Windows.

Okay, so here is the info on my friend's machine:

 

[simrick]

In Disk Management, it says that Boot is on C: partition.

Post a MAXIMIZED screen print of Disk Management
http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

In Disk Management the partition that shows "Boot" is the partition that the Windows OS is installed on, and currently running.
In Disk Management the partition that shows "System/Active" is where the boot code is, used to boot up the correct Windows OS partition.
Yes, it's confusing...

I've had a chance to grab screen shots of my friend's machine (above). Any chance of deciphering it, or should I head on over to eightforums?

 

[DavidE]

Create a Backup Image of the partition periodically. Create a Backup Image EFI System Partition at least once in case that ever gets corrupted. As the EFI System Partition is so small you could also include that partition in the periodic Backup Images. That way you always have it easily available whenever you need to restore the system.

 

[simrick]

Create a Backup Image of the partition periodically. Create a Backup Image EFI System Partition at least once in case that ever gets corrupted. As the EFI System Partition is so small you could also include that partition in the periodic Backup Images. That way you always have it easily available whenever you need to restore the system.[/QUOTE] Thanks David. I also noticed that Macrium have the option to "[I]Create an image of the partition(s) required to backup and restore Windows[/I]". I assume that selection would capture boot, OS and restore partitions - have I got that right? So if a computer had been upgraded to W10 from W7, or W8.1 from W8.0, that would be useless, unless you wanted to go all the way back to original configuration, correct? Thanks so much for your help!