Solved Can I move a HDD image to another HDD? And a few more questions...

[Brds7t7]

Interesting, I wasn't aware of that limitation. I always thought that it would just pick up the images as long as they are in that folder and the correct drive was attached when booted into the recovery options.

Edit: Just noticed MJF's post after I was writing mine. So does that mean it will pick up the backups on a different drive? As long as they keep the same folder structure?

 

[whs]

Nah, if the address changes, it cannot find it. That figures.

 

[mjf]

Edit: Just noticed MJF's post after I was writing mine. So does that mean it will pick up the backups on a different drive? As long as they keep the same folder structure?

It should pick up WindowsImageBackup on any drive or partition of a drive provided it resides in the root of the partition. Windows imaging is clunky and you can only have one recognisable image per partition. So for multiple images you either have to temporarily rename or put them in other folders. I used to do both. I would have a folder called say "Current Images" and rename the image folder WindowsImageBackup_date. As long as you move back to the root and rename to WindowsImageBackup the system repair disk image restore should find it. It always worked for me many times in the past.

 

[Brds7t7]

Edit: Just noticed MJF's post after I was writing mine. So does that mean it will pick up the backups on a different drive? As long as they keep the same folder structure?

It should pick up WindowsImageBackup on any drive or partition of a drive provided it resides in the root of the partition. Windows imaging is clunky and you can only have one recognisable image per partition. So for multiple images you either have to temporarily rename or put them in other folders. I used to do both. I would have a folder called say "Current Images" and rename the image folder WindowsImageBackup_date. As long as you move back to the root and rename to WindowsImageBackup the system repair disk image restore should find it. It always worked for me many times in the past.

Exactly what I was thinking MJF. I was sure in the past I have moved images to another drive and it had picked them up without issue. Although that was a few years ago and my memory is toast these days

I keep older images in the folder WindowsImageBackup-Saved. If I want to restore any of the older ones I simply use command prompt to rename the folder to WindowsImageBackup before the restore.

 

[whs]

This is too much of a detour for me. I usually keep at least 5 images by the father and grandfather principle. I would not have the patience for all the required shoving. Macrium is so much easier.

 

[AddRAM]

no, I meant just make a new current image, I don`t think we`ve ever even discussed the possibilities of what you`re asking.

 

[whs]

Brian, we never discussed that possibility because nobody in his right mind would consider the native Windows imaging as a viable solution. We all prefer Macrium or other OEM solutions.

 

[AddRAM]

I don't know exactly why you are interested in doing it the way you are saying, but FTR Macrium Reflect is free and is an excellent program.

I'm 100% willing to install Macrium Reflect and use it, as you suggest, but how can I ensure that the image that I make today is an image of the state of the computer as it was yesterday, before I started installing all my programs? I'm surprised that this is so hard to understand.

It's much easier than what you are trying to do.

Well, unless Macrium Reflect is able to make a backup of the state of my computer as it was yesterday (not today), what you're suggesting is actually much harder: you're suggesting that I restore the image that I made yesterday (thus removing all the programs and settings that I spent the whole day today setting up) and then make a backup/image of that onto an external hard drive, and then re-install and re-setup all the stuff that I installed and setup today.

Why would you think the image could change ? Even if you were to create a newer image on the same drive, it won`t overwrite or mess with the 1st image, and so on.

 

[AddRAM]

Brian, we never discussed that possibility because nobody in his right mind would consider the native Windows imaging as a viable solution. We all prefer Macrium or other OEM solutions.

I never mentioned windows imaging , did I

In fact I use windows AND Macrium, just made 2 new images yesterday.

And for the record, windows imaging works perfectly

Microsoft would not put it in the system if it didn`t.

I`m still baffled that he wants to make an image of an image, I understand his reasoning, but it`s just ya know, silly

 

[whs]

I am lost - the whole discussion was regarding Windows imaging. And Microsoft put a lot of junk into the system. Imaging is certainly one of those. Make an image each day next week and then show me the 7 images at the end of the week - but don't move anything. I don't want to have you do any extra work. Just make images one after the other.

 

[AddRAM]

@mjf, what do you mean only 1 image per partition ?

Windows will make as many images as you want as long as the drive you`re storing them on has the room.

If you did use windows imaging it`s just like system restore and gives you the option to choose any image you want, I`ve done it.


But you`re right Wolfgang :focus:

 

[Layback Bear]

I'm getting a head ache over this backup thing.

I use to use Windows 7 backup and it didn't seem to be all the difficult to do.
Tell Window to make a image and what drive and partition you wanted it to be put. Done.

I never tried moving the backup around or changing it's name ect.
If I ever needed it I wanted Windows 7 to be able to find it.

I never tried moving a Windows 7 made image from one drive to another drive but their is one way to find out if it works. Try it. I really don't know why it wouldn't. A image is like everything else on a computer a bunch of "1" and "0". All a image does is move a bunch of "1" and "0" from one place to another. If their is a way of doing this using Windows 7 built in imaging I don't know how.

I use Macrium now because I have more choices.

 

[whs]

Jack, the discussion is about moving the image. In that case the recovery cannot find it and since there is no browse option, you cannot point it to the right location. Thus, don't move a Windows image else you have to jump thru additional hops. But that also means that you cannot make several images without unnatural additional hops.

 

[Layback Bear]

I think I understand.
That is also why I don't move images. If I start moving images I nor Windows 7 will find them with out a bunch of work and or luck.

That is why I post this.

I never tried moving the backup around or changing it's name ect.
If I ever needed it I wanted Windows 7 to be able to find it.

 

[whs]

With Macrium images that is a different story. There I can point the recovery program to the image I want to use - and I can browse to any location.

 

[mjf]

@mjf, what do you mean only 1 image per partition ?

Windows will make as many images as you want as long as the drive you`re storing them on has the room.

If you did use windows imaging it`s just like system restore and gives you the option to choose any image you want, I`ve done it.


But you`re right Wolfgang :focus:

Firstly I don't consider the discussion has strayed off topic.

Secondly I suggest you read my responses. I have made and restored more system images than I can remember using Windows built in Imaging so I know a bit about it. I've spread images across drives and had multiple discrete/standalone images in a single partition by renaming. I've used this practice on 4 generations of PCs and never had a problem.

If you choose to make multiple images to the one WindowsImageBackup then you are relying on Windows difference imaging and shadow storage. This is full of potential pitfalls and would never recommend it. That is why I use the words discrete/standalone. That is you make one image and do not add to it - get it?

To revisit the original question (again) I have copied a WindowsImageBackup folder in the past as an exercise and it did work. It is tiresome and not good practice. Also, I have said I consider Macrium a far superior imaging program that I use exclusively now. But the OP did ask about Windows inbuilt imaging.

 

[ThrashZone]

Yea sorry I didn't get the logic of making an image of an image
The shear waste of space with that in windows imaging is senseless.

Last I made a windows image it asked if I wanted to make that external drive as a backup drive
I said okay... and made it
Disconnected the external drive and windows never found that image when I needed to restore it
That made me realize windows imaging isn't reliable.

Macrium I can disconnect the drive without any issue the winpe recovery rules it reads what ever drives are connected and finds all the images on it
And can be restored to any sata connected drive the original or a updated one.

 

[whs]

Making an image of an image is an emergency measure. Read the information block of this tutorial and you will see why it may sometimes be required.

http://www.sevenforums.com/tutorials/210195-system-image-recover-broken-windows-7-system-image.html

 

[mjf]

Do you mean, I must make an image of the image?

I didn't think you meant an image of a mounted image? In this respect you can make an image of an image.
I suggested this way back (2010/11) restore a Windows inbuilt image to a smaller drive. Restoring to a smaller drive is another problem with Windows inbuilt imaging.
http://www.sevenforums.com/backup-restore/204100-recovery-smaller-hard-drive.html#post1712404

 

[whs]

If you mount the image, you can shrink it until it fits. That shrunken image you can reimage.