System Image is not recognized in Control Panel\...\Backup and Restore

[IfItsX]

I have a 256Gb SSD partitioned into 121GB (Volume label left at default "Local Disk") (C and 116 GB Data (D (sizes select by default in initial access to Disk Management). I also have an internal SATA 6Gb 500Gb Backup (E.

Apparently this label of my E: drive is both "meaningless" and "meaningful" for Win7:

When I wanted to make my first SystemImage, Win7 suggested that my destination choice was not a good idea. It makes perfect sense for me, but I can see that Win7 might prefer an external USB hdd.

But I went ahead and made the System Image on Backup (E and it appears to be in good order: I allowed Win7 to name it with its default folder "WindowsImageBackup" with the subfolder named from my system name, with add'l subfolders:

Backup 2012-01-03 (+ some 6 digit id #, I presume)
Catalog
SPPMetadataCache

However, this System Image is not recognized in Control Panel\...\Backup and Restore and the "Select another backup to restore files from" dialog does not recognize the E: drive nor allow me any means to select it.

However, if I select "Setup backup" Win7 immediately selects Backup (E, adding the comment [Recommended].

I can see the statement near the top of the dialog about recommending a backup on an external drive, but this is not what I consider an intelligent backup approach. I prefer to make both internal backups on my additional internal hdd and external usb hdd copies of backups.

The extensive listing of advantages and disadvantages is helpful for newer users, but those who have evolved from NT 3.51 should be allowed a certain discretion. No?

My copy of Windows 7 Annoyances informs me about how to access this System Image by the "Attach VHD" option from "Disk Management\Work with Partitions," even instructing how one can use this method to restore individual files, which normal access to System Images apparently prevents. I have not tried this approach, so I have no sense of its reliability. However, the author has stayed with the evolution of Windows and might be considered to have worthy conceptualizations.

Finally, I am concerned because of this apparently totally inhibited access to my SystemImage that it might not allow me to (make a usable?) copy it to an external usb hdd.

I'd appreciate any suggestions about two things: how to actually access this SystemImage on my internal E: drive if I need/want to, and if I attempt to make a copy of this to an external usb hdd will I be able to make a valid copy?

 

[johnebadbak]

in backup and restore there is a option to create a rescue disc. you will need this disc to access the system image should the system crash. You can backup an image to your external hdd and access it with the bootable rescue disc.

 

[JimLewandowski]

There are 2 attached files. a .bat file and a .txt file.

Use the link below to access the attachments.

http://www.sevenforums.com/backup-r...allow-multiple-images-windowsimagebackup.html


Download the one of your choice and if .txt, rename it to a .bat extension.

Prior to running, make sure ALL drives are connected that may have System Images upon them.

Your current working directory is the directory to which you saved the sysimage.bat (or .txt that has been renamed .bat).

Run using the following:

sysimage.bat /I Y > sysimout.txt

This will run it and direct the output to sysimout.txt. Inside this will be all the information about every system image, which drives were backed up, which had a matching shadow (system) entry, which physical WindowsImageBackup files were found, etc.

Post that results .txt file back here as an attachment (i.e. MANAGE ATTACHMENTS option at the lower left of REPLY screen).

A wrinkle I have not checked into is when in Windows Recovery Environment, the drive letters could be different. So, how would System Image deal with having a shadow copy saying "I'm on drive F" but F is now E in win RE?

The 6-digit # on \Backup is HHMMSS.

It didn't like you targeting D for your system image as that's on the same physical disk as the OS (C).

 

[whs]

1. Windows imaging is a bad choice. It is too restricted and too touchy. The day you really need it you never know what will happen. Free Macrium or Free Paragon are much better choices.

2. Yes you should be able to attach the VHD. I am sure O'Reilly has explained how - if not ask here. He is an excellent author.

 

[IfItsX]

There are 2 attached files. a .bat file and a .txt file.

Download the one of your choice and if .txt, rename it to a .bat extension.

<snip>

The 6-digit # on \Backup is HHMMSS.

It didn't like you targeting D for your system image as that's on the same physical disk as the OS (C).

***

Jim,

Thanks for interest and potential innovative methods of inquiry or solution. I've been up to me ears in development environment details - all working, but lots of learning curve - that followed a building of a new (for me, anyway) high-powered system and move directly from 11 years of Win2k-skipXP-to-Win7 x64 and !! 16GB of memory! Have we finally arrived yet?

Thanks for the clue about the 6-digit #.

I quite agree with you that targeting a D partition on my OS drive would be foolish. In all of the detail you furnished me, I think you missed that I mentioned early on that "I also have an internal SATA 6Gb 500Gb Backup (E." It was this non-ssd "internal" Western Digital HDD that I made the SystemImage backup to.

When I have recovered a bit during the next couple of days I will explore what you offer. It appears to be right out of the annals of the under-the-hood potential that has made the Windows Annoyance series so helpful and successful. I do notice though that a few of the descriptions he offers are no longer available, perhaps changed somehow in sp1.

Thanks again. Back to you in a bit.

 

[JimLewandowski]

Good. I aim to please. I may upload a later version with a few cleaned up bugs but that one should be fine for you. I just uploaded a new version to the link below.....

I myself wish to have information that I can see rather than guessing at how this stuff works.

To keep only one copy of the .bat floating around, use this link and download from the first post attachments. I have removed the attachments in THIS thread.

http://www.sevenforums.com/backup-r...allow-multiple-images-windowsimagebackup.html

 

[IfItsX]

1. Windows imaging is a bad choice. It is too restricted and too touchy. The day you really need it you never know what will happen. Free Macrium or Free Paragon are much better choices.

2. Yes you should be able to attach the VHD. I am sure O'Reilly has explained how - if not ask here. He is an excellent author.

***

Exactly my concern. A few years back when Maxtor was still a helpful alternative - at least I had good luck with them, they bought the best hdd technology that existed from Quantum, my preferred drives - they offered "MaxBlast" which was a limited feature subversion of Acronis True Image. I made some images with it and never never worked. Then a year or so later I flirted with the idea of diving in and making the big cross-hardware version of their product. However, I spent a great deal of time lurking in their forums and I was quite put off with how many serious complaints people were having. Not the kind of stuff that helps me to sleep at night. So, those experiences have been lurking in the back of my mind and I have not been approaching this transition with the idea of actually "depending" on it to work. Wonderful, isn't it.

Fortunately, I make many detailed data backups using two different software approaches from AJC Software, using their Backup and their Sync. Sync and I are having some issues in the transition to Win7, but I think I may be able to make the cultural adaptation Andrew has used with his Sync 3.5. We'll see. Thanks for verifying the VHD approach and I appreciate your support of David Karp's authority. It's an ironic shame that his web site has been so virtually unusable for so long, i.e., with search totally in bugsville.

Thanks for the recommendations for Free Macrium or Free Paragon. I'll give them a look.