Apologies if this is an improper location for this post, I received help here before.
I recently re-formatted my vista pc to WIn7. I had posted asking about an imaging program (WIn7/Macrium) and decided to go with Macrium Free, but I just noticed I don't have the option to do an "Incremental" back up, If using the free addition. Is my only choice to do a "complete disk image" every time? Unless I'm missing something.
I printed the tutorial at Macrium's site, but the walk through screen shots don't look exactly like the program I'm using, I believe they are for the full edition.
I'm I better off to purchase the full product and schedule an "Incremental" back up to run on a regular basis?
So far using Macrium Free, I have - 1. made a "Rescue CD" in the Linux recovery environment. I'm hesitant to test this CD for fear It will screw something up, I know I need to, but don't understand exactly how to do it, or what to expect!
The instructions say to power machine completely down before using (Testing?) the "Rescue CD" ?? How am I supposed to get the disc into the tray with the machine off ? Can I insert the disc, then power down, then re-power?
what do I need to look for and where do I stop the process to just check the "Rescue CD" for a working copy, before it moves the image to my fully functional pc?
2. I went ahead and created a "Disc Image" in it's own folder on an external HD.
Thanks in advance.. for any help!
Bret
I recently re-formatted my vista pc to WIn7. I had posted asking about an imaging program (WIn7/Macrium) and decided to go with Macrium Free, but I just noticed I don't have the option to do an "Incremental" back up, If using the free addition. Is my only choice to do a "complete disk image" every time? Unless I'm missing something.
I printed the tutorial at Macrium's site, but the walk through screen shots don't look exactly like the program I'm using, I believe they are for the full edition.
I'm I better off to purchase the full product and schedule an "Incremental" back up to run on a regular basis?
So far using Macrium Free, I have - 1. made a "Rescue CD" in the Linux recovery environment. I'm hesitant to test this CD for fear It will screw something up, I know I need to, but don't understand exactly how to do it, or what to expect!
The instructions say to power machine completely down before using (Testing?) the "Rescue CD" ?? How am I supposed to get the disc into the tray with the machine off ? Can I insert the disc, then power down, then re-power?
what do I need to look for and where do I stop the process to just check the "Rescue CD" for a working copy, before it moves the image to my fully functional pc?
2. I went ahead and created a "Disc Image" in it's own folder on an external HD.
Thanks in advance.. for any help!
Bret
1. There are no incrementals in free Macrium - only in the Pro version. As far as I am concerned, that is the better deal anyhow. If you make incrementals and lose any incremental in the middle of the chain, you lost the whole chain. Whilst with independent images, you are always safe- at best you lose one but still have all the others. At the low price of disks these days, i rather go with that.
2. Free Paragon makes incrementals - but as I said, I warn against incrementals.
3. For the purposes of testing, see my procedure below. That is safe and you risk nothing. You may also watch my Macrium video tutorial and read the text in the pink box: Imaging with free Macrium
Macrium test
1. Shrink 2GBs from C and define a simple volume (partition) - let's call it Y
2. Move some files (any files) into Y - I always also move the sample picture folder in (you'll see why)
3. Define a test folder on your external backup disk - call it Mtest
4. Make an image of Y to Mtest - requires that you make a new definition
5. Delete a couple of pictures from the sample picture folder on Y (I always use the 2 animals)
6. Reboot and tap (ESC, F2 or whatever it is on your system) to get into the BIOS boot sequence
7. Set your boot sequence to CD/DVD reader
8. Throw in the Macrium recovery CD and let it run, then hit Enter
9. Now you are in the recovery wizard, set it to Mtest where it says "Locate Image" and to Y where it says "Choose partition to overwrite with the image data".
Note: the partition letters may not be the same as on your system. Macrium uses its own lettering. Best is to go by the size of the partitions and open it with the little + in the front.
10. Watch out when it asks whether to replace the Master Boot Record - in this case say "do not replace" because this is only a data partition. If that were your system partition, you would replace the MBR provided you do not have a separate boot partition.
11. When you get the little window saying "Your computer will now reboot", you have to hit "Cancel" (on the bottom" to get it to reboot. That's a little strange way to end the session, but that's the way it is.
12. Check whether the 2 animals in the sample picture folder are back. That shows you that the recovery worked.
When you have done these steps, you did the whole cycle and have learned
1. That your recovery disk works
2. How to recover
3. That things work
Now you can delete the little 2GB partition and add it back to it's originating partition.
If you are not familiar with the creation and deletion of partitions, watch this tutorial: http://www.sevenforums.com/tutorials/72427-data-partition.html
2. Free Paragon makes incrementals - but as I said, I warn against incrementals.
3. For the purposes of testing, see my procedure below. That is safe and you risk nothing. You may also watch my Macrium video tutorial and read the text in the pink box: Imaging with free Macrium
Macrium test
1. Shrink 2GBs from C and define a simple volume (partition) - let's call it Y
2. Move some files (any files) into Y - I always also move the sample picture folder in (you'll see why)
3. Define a test folder on your external backup disk - call it Mtest
4. Make an image of Y to Mtest - requires that you make a new definition
5. Delete a couple of pictures from the sample picture folder on Y (I always use the 2 animals)
6. Reboot and tap (ESC, F2 or whatever it is on your system) to get into the BIOS boot sequence
7. Set your boot sequence to CD/DVD reader
8. Throw in the Macrium recovery CD and let it run, then hit Enter
9. Now you are in the recovery wizard, set it to Mtest where it says "Locate Image" and to Y where it says "Choose partition to overwrite with the image data".
Note: the partition letters may not be the same as on your system. Macrium uses its own lettering. Best is to go by the size of the partitions and open it with the little + in the front.
10. Watch out when it asks whether to replace the Master Boot Record - in this case say "do not replace" because this is only a data partition. If that were your system partition, you would replace the MBR provided you do not have a separate boot partition.
11. When you get the little window saying "Your computer will now reboot", you have to hit "Cancel" (on the bottom" to get it to reboot. That's a little strange way to end the session, but that's the way it is.
12. Check whether the 2 animals in the sample picture folder are back. That shows you that the recovery worked.
When you have done these steps, you did the whole cycle and have learned
1. That your recovery disk works
2. How to recover
3. That things work
Now you can delete the little 2GB partition and add it back to it's originating partition.
If you are not familiar with the creation and deletion of partitions, watch this tutorial: http://www.sevenforums.com/tutorials/72427-data-partition.html
Thanks WHS, I really enjoy your tutorials they are very well done!
I still have questions about testing the "Rescue Disc" as mentioned in my first post?
Thanks again
Bret
I still have questions about testing the "Rescue Disc" as mentioned in my first post?
Thanks again
Bret
�� Quote: Originally Posted by N2Abyss 
Thanks WHS, I really enjoy your tutorials they are very well done!
I still have questions about testing the "Rescue Disc" as mentioned in my first post?
Thanks again
Bret
I still have questions about testing the "Rescue Disc" as mentioned in my first post?
Thanks again
Bret
I guess maybe I wasn't clear, I recently had a pc crash due to operating system errors, and would, in that specific case need to use the "Rescue Disc" for start up. The "rescue disc" is what I need help with on testing.
I don't want to foul up anything on my re-formatted system.
Thanks
Bret
I don't want to foul up anything on my re-formatted system.
Thanks
Bret
Bret, I do understand completely. With my little Macrium test, you will test the recovery CD. Understand that this CD contains a little program running under Linux that will pull the image in - any Macrium image. An if it works properly with my little test procedure, it will work for the "real thing" too.
Another question, of course, is whether your image is whole. There is always the possibility that one has a bum image (although I have never seen that). The best way to protect yourself against that is to make and keep many images. Maybe you want to read my little tutorial on imaging strategies.
Another question, of course, is whether your image is whole. There is always the possibility that one has a bum image (although I have never seen that). The best way to protect yourself against that is to make and keep many images. Maybe you want to read my little tutorial on imaging strategies.
Ok WHS, I'll give your instructions a complete try. You have already been a big help in getting my first image shot and made using this program very easy! Thanks for all your help.
Best Regards
Bret
Best Regards
Bret
You can test that the linux boot disk works and you can get to the stage were it sees images before pulling the plug if you're worried about checking for full images. But WHS's test should be convincing enough.
I don't think you will ever be fully confident until you restore your first full system image - at least I wasn't.
Also double click on one of the *.mrimg images and Macrium will mount it to view the contents.
I don't think you will ever be fully confident until you restore your first full system image - at least I wasn't.
Also double click on one of the *.mrimg images and Macrium will mount it to view the contents.
�� Quote: Originally Posted by mjf I don't think you will ever be fully confident until you restore your first full system image - at least I wasn't.
~Maxx~
�� Quote: Originally Posted by Maxxwire �� Quote: Originally Posted by mjf I don't think you will ever be fully confident until you restore your first full system image - at least I wasn't.
~Maxx~
Once I had successfully completed that first Macrium Reflect backup it completely changed my whole attitude toward how I run my computer with the strengthened confidence that 3 complete sets of Image Backups on 3 different inert disks can inspire.
~Maxx~
~Maxx~
Yes indeed, many hours of work can be lost to the stroke of a key!!
Although not a pro by any means, I have been using a computer for many years for many things, and due to my busy schedule, Backups are often let go, (you know, Ill get to it later). The last crash with Vista was the last straw.
I lost the desktop first and couldn't get it back, so I chose to repair with data and lost everything I had! months and months of work! oh yes, most of it was backed up, but not current!
That's when I decided to give Macrium a try and as soon as I re-formatted, it's one of the first programs I loaded!
Although not a pro by any means, I have been using a computer for many years for many things, and due to my busy schedule, Backups are often let go, (you know, Ill get to it later). The last crash with Vista was the last straw.
I lost the desktop first and couldn't get it back, so I chose to repair with data and lost everything I had! months and months of work! oh yes, most of it was backed up, but not current!
That's when I decided to give Macrium a try and as soon as I re-formatted, it's one of the first programs I loaded!
�� Quote: Originally Posted by N2Abyss The last crash with Vista was the last straw.
I lost the desktop first and couldn't get it back, so I chose to repair with data and lost everything I had! months and months of work! oh yes, most of it was backed up, but not current!
I lost the desktop first and couldn't get it back, so I chose to repair with data and lost everything I had! months and months of work! oh yes, most of it was backed up, but not current!
~Maxx~
�� Quote: Originally Posted by N2Abyss That's when I decided to give Macrium a try and as soon as I re-formatted, it's one of the first programs I loaded!
Quote:
It provides the option of writing the rescue boot info to your hard drive
WHS, a quick question, I have Macrium set to run at log on, is it better to leave the computer alone while it's making an image? It makes me nervous running other tasks while it is making it's image.
Thanks
Bret
Thanks
Bret
It will be quicker if you don't attempt to do anything else while it's imaging.
BTW Paragon makes differential drive images - not incremental.
A differential image contains all the changes since the first full image.
You need either the first full image to restore to the time that was made, or the first full image any one differential to restore to the time that differential was made.
Incrementals include the changes only since the last incremental - not all the changes since the first full image.
The Macrium Bartpe plugin ( now called pebuilder) works in pe2 and pe3.
This is my pe3 media :
The macrium boot menu option adds an entry to boot a pe2 .wim including the macrium program from the hard drive .
Similar to the option to boot windows winre.wim from the HD - you will see that on the advanced boot menu, if you have the 100mb system partition.
You can add any .wim to the regular boot menu very easily.
You can also use an F key to boot any .wim from the HD, but that's a bit fiddly for beginners.
The purpose of the boot menu option is convenience - you may not have external boot media ( e.g. cd) with you.
The downside is it depends on bcd working - so is not a proper substitute for external bootable recovery media.
BTW Paragon makes differential drive images - not incremental.
A differential image contains all the changes since the first full image.
You need either the first full image to restore to the time that was made, or the first full image any one differential to restore to the time that differential was made.
Incrementals include the changes only since the last incremental - not all the changes since the first full image.
The Macrium Bartpe plugin ( now called pebuilder) works in pe2 and pe3.
This is my pe3 media :
The macrium boot menu option adds an entry to boot a pe2 .wim including the macrium program from the hard drive .
Similar to the option to boot windows winre.wim from the HD - you will see that on the advanced boot menu, if you have the 100mb system partition.
You can add any .wim to the regular boot menu very easily.
You can also use an F key to boot any .wim from the HD, but that's a bit fiddly for beginners.
The purpose of the boot menu option is convenience - you may not have external boot media ( e.g. cd) with you.
The downside is it depends on bcd working - so is not a proper substitute for external bootable recovery media.
�� Quote: Originally Posted by N2Abyss WHS, a quick question, I have Macrium set to run at log on, is it better to leave the computer alone while it's making an image? It makes me nervous running other tasks while it is making it's image.
Thanks
Bret
Thanks
Bret
My suggestion: Instead of scheduling it at boot time I suggest to schedule it on a day (or every day of the week) at a certain time. And check the box on the bottom of the little window saying:" If missed, run at next boot". Then it does not come up when you reboot during the day - e.g. because updates were installed.
�� Quote: Originally Posted by Mark Phelps �� Quote: Originally Posted by N2Abyss That's when I decided to give Macrium a try and as soon as I re-formatted, it's one of the first programs I loaded!
I used to do a lot of international travelling with work and if I was doing it now one of the very small portable HDDs would have been essential baggage - size of a pack of cards! Put images & lots of other documents etc. But it would be nice to use it as a boot recovery device for both Macrium (including linux boot) and Windows imaging as well.
Well, I tried my Macrium test file today, finally!
I'm imaging to a Iomega eGo 500GB portable HDD, so I made a little picture folder and placed on my second internal HDD, made an image, deleted some of the pictures and rebooted with the rescue disk.
All worked fine with the Linux image recovery disc, but I wasn't able to locate the Iomega drive in the drive tree! (this is a USB 3.0 drive and I recently installed a new 3.0 external card on the PC for it)
I went back through my image steps from the beginning, to make sure I was doing everything correctly, Then it dawned on me to switch USB ports this time. So I switched the Iomega drive to a 2.0 port in the front of the PC and wala! it worked! I restored the pictures I had deleted!
I don't understand why the Iomega drive isn't recognized when plugged into the 3.0 card? The drive performs and functions perfectly for imaging,transferring and reading data when attached to the 3.0 card? Oh well, at least I have a work around.
I'm imaging to a Iomega eGo 500GB portable HDD, so I made a little picture folder and placed on my second internal HDD, made an image, deleted some of the pictures and rebooted with the rescue disk.
All worked fine with the Linux image recovery disc, but I wasn't able to locate the Iomega drive in the drive tree! (this is a USB 3.0 drive and I recently installed a new 3.0 external card on the PC for it)
I went back through my image steps from the beginning, to make sure I was doing everything correctly, Then it dawned on me to switch USB ports this time. So I switched the Iomega drive to a 2.0 port in the front of the PC and wala! it worked! I restored the pictures I had deleted!
I don't understand why the Iomega drive isn't recognized when plugged into the 3.0 card? The drive performs and functions perfectly for imaging,transferring and reading data when attached to the 3.0 card? Oh well, at least I have a work around.
USB3 is so new that there is probably no support yet - especially in the Linux recovery program. This is ashame because the USB3 would lend itself particularily well for imaging. But I am sure given time, we will get it.
But if I understand you right, the image was initially written to the USB3 disk - right?
Would be interesting to know whether Win7 imaging supports it. Maybe jmf knows.
But if I understand you right, the image was initially written to the USB3 disk - right?
Would be interesting to know whether Win7 imaging supports it. Maybe jmf knows.
Yes Wolfgang, the drive has no problems saving the backup image through the 3.0 usb connection, Maybe its Linux that doesn't get along well with 3.0?
Bret
Bret
�� Quote: Originally Posted by N2Abyss Yes Wolfgang, the drive has no problems saving the backup image through the 3.0 usb connection, Maybe its Linux that doesn't get along well with 3.0?
Bret
Bret
�� Quote: Originally Posted by whs Next week I get a new laptop with USB3. I guess I will experiment - also with Windows imaging.
~Maxx~
�� Quote: Originally Posted by Maxxwire �� Quote: Originally Posted by whs Next week I get a new laptop with USB3. I guess I will experiment - also with Windows imaging.
~Maxx~
Linux o/s is not behind the times.
It is just that Paramount haven't built usb 3.0 support into the free boot disc yet.
They soon will.
It is just that Paramount haven't built usb 3.0 support into the free boot disc yet.
They soon will.
Good for me, that the new USB3 system I purchased is backward compatible!
Bret
Bret
�� Quote: Originally Posted by SIW2 Linux o/s is not behind the times.
It is just that Paramount haven't built usb 3.0 support into the free boot disc yet.
They soon will.
It is just that Paramount haven't built usb 3.0 support into the free boot disc yet.
They soon will.
�� Quote: Originally Posted by whs Well, as Bret says, the imaging part (with Macrium) seems to work.
~Maxx~
Quote:
I'm also wondering if USB3 is as fast as eSATA when Imaging with Macrium Reflect
whs- Thanks for the specs, but as we all know maximum R&W benchmark specs and the actual bandwidth that an interface operates at in use on a computer are much different. For example USB 2 has usually always operated at <1/3 of its rated bandwidth on my computer which is why I'd be interested in seeing an actual screenshot of an Image backup being made with Reflect while using USB 3.
~Maxx~
~Maxx~
I will make one in a couple of weeks when I have my new Laptop up and running. Remind me then.
Btw: those were real test figures.
Btw: those were real test figures.
With my ASUS pcie usb3 card and the Iomega eGo usb3 drive, I'm getting an average transfer rate of 397.9 mb/s. with 37.1 gb of the C: drive data being imaged in around 5.5 minutes.
Which now leads me to believe the Macrium software is not utilizing the full potential of the backup media system?
Bret
Which now leads me to believe the Macrium software is not utilizing the full potential of the backup media system?
Bret
�� Quote: Originally Posted by N2Abyss With my ASUS pcie usb3 card and the Iomega eGo usb3 drive, I'm getting an average transfer rate of 397.9 mb/s. with 37.1 gb of the C: drive data being imaged in around 5.5 minutes.
Which now leads me to believe the Macrium software is not utilizing the full potential of the backup media system?
Bret
Which now leads me to believe the Macrium software is not utilizing the full potential of the backup media system?
Bret
~Maxx~
Hi All,
Been following this topic with interest and decided to give Macrium a quick twirl. I have a few questions:
1. Im interested in imaging my C: drive - this contains my OS and Apps. When I select the drive, do I also need to select the 100MB System Reserved Partition? It appaers to be slightly greyed out, so I'm guessing (without actually trying it) that I can't actually select it, and don't need to?
2. Assuming I can successfully image my C: drive (and create a Linux boot disk), can I reintsall the image to a brand new SSD that has never been used? Is it better to install fresh to an SSD the long way, or does the image restoration do just as good a job : note, this is a brand new SSD, nothing has yet been installed on it.
As you can guess, Im moving from HDD's to SSD's, and wonder whether a fresh installation is the way to go, or whether image restoration is just as good. This is a Windows 7 Ultimate x64 system.
What say you?
Golden
Been following this topic with interest and decided to give Macrium a quick twirl. I have a few questions:
1. Im interested in imaging my C: drive - this contains my OS and Apps. When I select the drive, do I also need to select the 100MB System Reserved Partition? It appaers to be slightly greyed out, so I'm guessing (without actually trying it) that I can't actually select it, and don't need to?
2. Assuming I can successfully image my C: drive (and create a Linux boot disk), can I reintsall the image to a brand new SSD that has never been used? Is it better to install fresh to an SSD the long way, or does the image restoration do just as good a job : note, this is a brand new SSD, nothing has yet been installed on it.
As you can guess, Im moving from HDD's to SSD's, and wonder whether a fresh installation is the way to go, or whether image restoration is just as good. This is a Windows 7 Ultimate x64 system.
What say you?
Golden
�� Quote: Originally Posted by Golden Hi All,
Been following this topic with interest and decided to give Macrium a quick twirl. I have a few questions:
1. Im interested in imaging my C: drive - this contains my OS and Apps. When I select the drive, do I also need to select the 100MB System Reserved Partition? It appaers to be slightly greyed out, so I'm guessing (without actually trying it) that I can't actually select it, and don't need to?
2. Assuming I can successfully image my C: drive (and create a Linux boot disk), can I reintsall the image to a brand new SSD that has never been used? Is it better to install fresh to an SSD the long way, or does the image restoration do just as good a job : note, this is a brand new SSD, nothing has yet been installed on it.
As you can guess, Im moving from HDD's to SSD's, and wonder whether a fresh installation is the way to go, or whether image restoration is just as good. This is a Windows 7 Ultimate x64 system.
What say you?
Golden
Been following this topic with interest and decided to give Macrium a quick twirl. I have a few questions:
1. Im interested in imaging my C: drive - this contains my OS and Apps. When I select the drive, do I also need to select the 100MB System Reserved Partition? It appaers to be slightly greyed out, so I'm guessing (without actually trying it) that I can't actually select it, and don't need to?
2. Assuming I can successfully image my C: drive (and create a Linux boot disk), can I reintsall the image to a brand new SSD that has never been used? Is it better to install fresh to an SSD the long way, or does the image restoration do just as good a job : note, this is a brand new SSD, nothing has yet been installed on it.
As you can guess, Im moving from HDD's to SSD's, and wonder whether a fresh installation is the way to go, or whether image restoration is just as good. This is a Windows 7 Ultimate x64 system.
What say you?
Golden
But yes, you can image several partitions together but recover only one at a time (for good reason)
ad2) yes you can do that. But there are a few things you have to remember:
1. free Macrium can only recover to a partition of equal or larger size. So your imaged partition must have been equal or smaller in size thn the SSD - and I mean partition, not actual data or size of the image.
If you want to install an image of a big partition to a smaller SSD, you need Macrium Pro, but free Paragon can do that too
2. You first need to define a partition primary (for the active partition) on the SSD and align that. Here is how. When you do a fresh install of Win7, the installer does that for you. With the 100MB partition present, it gets a bit messy. It is a little easier with the Win7 imaging in that case because it drags the 100MB partition along. I am not sure though how Win7 imaging deals with recovery of a "large" partition to a "small" SSD.
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.
Paragon sent me an app. called Migrate to ssd - haven't tried it yet, but it looks good.
Paragon Migrate OS to SSD - Overview
Paragon Migrate OS to SSD - Overview
�� Quote: Originally Posted by SIW2 Paragon sent me an app. called Migrate to ssd - haven't tried it yet, but it looks good.
Paragon Migrate OS to SSD - Overview
Paragon Migrate OS to SSD - Overview
Not exactly, the Paragon app. will migrate to a smaller ssd or HD , and let you exclude folders, as well as aligning during the migration.
SIW and WHS:
Is there an over-riding reason NOT to image from an HDD to an SSD when migrating to SSD technology---rather than doing a clean install to the SSD?
I will be facing this issue within months. I have an install disc and have always done clean installs, but if I can get by with imaging, why not?
I have seen people imply clean is preferred, but is imaging more problematic when the destination is SSD rather than HDD? Any problems other than possibly alignment--which I understand can be corrected after the fact?
I do NOT have the 100 MB system partition.
I would likely use Macrium Free, but have access to Acronis as well.
Is there an over-riding reason NOT to image from an HDD to an SSD when migrating to SSD technology---rather than doing a clean install to the SSD?
I will be facing this issue within months. I have an install disc and have always done clean installs, but if I can get by with imaging, why not?
I have seen people imply clean is preferred, but is imaging more problematic when the destination is SSD rather than HDD? Any problems other than possibly alignment--which I understand can be corrected after the fact?
I do NOT have the 100 MB system partition.
I would likely use Macrium Free, but have access to Acronis as well.
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.
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.
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
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.
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.
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.
�� Quote: Originally Posted by ignatzatsonic I know Windows built in imaging isn't amused when you rename or relocate files.
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: http://www.sevenforums.com/tutorials...trategies.html
�� Quote: Originally Posted by mjf �� Quote: Originally Posted by ignatzatsonic I know Windows built in imaging isn't amused when you rename or relocate files.
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.
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
Không có nhận xét nào:
Đăng nhận xét