Since you do not have the complication of the 100MB partition, you may well use an image. Just make sure you image from a partition size equal or smaller than your SSD (with Free Macrium) and that you first align the SSD. If you do not want to bother resizing your partition, you can use free Paragon - Acronis I don't know. Have not used it in a long time.
Thanks for that WHS.
My current C partition is 60 GB on a 640 GB drive. The SSD I buy could be 60 also, in which case I guess I should shrink C a bit first if I am going to use Macrium Free.
My other idea is to maybe put a small D on the SSD for text files only. After 16 years of personal computing, I still have less than 6 GB of actual text files and would like to take advantage of the SSD's speed when manipulating them. All non-text files would have to go on a standard HDD. I just haven't decided if the small D would be a help rather than a hindrance over the long haul.
you may want to checkout Acronis too. I am not sure if you need to pay for it but it has some good features.
Bottom line, it is easier if you did a fresh installation provided you have the installation disk. However, the imaging path is the best way to go if you have a preinstalled OEM operating system and no installation disk.[/QUOTE]
Thanks WHS. I have all the neccessary installation disks, so it seems to make sense to go the fresh install route this time. Thnaks for the quick reply.
Just a quick question here, before I forget! I assume it's safe to delete the accumulating images on my backup media (as to keep things less confusing)? say just keep the last few? would this be a good idea for the Macrium Log as well?
What about just overwriting the data each time? did I miss a setting for that?
Thanks
Bret
My backup strategy is to keep some of the early "fresh" images when all your basic software has been added and keep an image when a piece of significant (paid/licensed) software is added. I then keep 2-3 staggered over the last couple of months. I use 2 imaging programs and at least 2 independent HDDs.
With Macrium I always image the tiny 100MB System reserved as part of the particular backup set. Just don't select when reimaging if you don't want to. Keeping a single one stashed away somewhere is just plain confusing in my book.
Most OSs from the big brands (Acer, HP, etc) are OEM:SLP OSs and come with a recovery partition. I have a couple of Macrium images of this partition which I have been able to restore to a new HDD.
N2Abyss:
Yes, you can delete older images. No sense keeping a stale one around too long, particularly if you update software from time to time and make an image a month or so.
I made one the day I installed Windows and I still keep it. It would just save me a little time if I had to reinstall.
I make an image about once a month, alternating between Macrium and Acronis. Every time I make one, I delete the oldest one I have (excluding the one I made the day of the install). So at any given time, I have 3 images.
I would not rename them or overwrite existing images. You might get away with it, but imaging is so touchy I would not get cute with anything if at all possible. I know Windows built in imaging isn't amused when you rename or relocate files. Macrium is not as fussy.
It's probably a good policy to re-do your rescue CD from time to time as well, particularly if you upgrade to a new version of your imaging application. Test it to make sure it works.
For all of those that wonder how many images to keep and where, I suggest you have a look at the summary I posted in the tutorial section: https://www.sevenforums.com/tutorials...trategies.html
Just order and flexibility.
You can move and rename your WindowsImageBackup Folder on the partition it was made to produce multiple images in folders and with names that suit you.
The images just need to be renamed back to WindowsImageBackup and moved to the root of the partition for windows reimaging to automatically recognize them.
Exceptions:
- The above does not apply if you have some fundamental problem with Windows imaging to begin with.
- The above does not imply copying or moving across partition boundaries. Moves across partition boundaries involve (large) physical file movement. Moves within partition boundaries are directory entry changes.
I have never had a problem with this scheme.
The move and rename can be easily carried out from the System Repair disk as described in part 1 of the tutorial.
System Image Recovery
Quote