First Full restore - couple weird things I noticed before starting it
Hi ...
This morning before going to work, I started my first ever full system restore. I set it to run while I was away and will check the status/results later ...
My set up is rather simple.
1. Restoring a single system partition to the original 1TB source drive. (the drive image is stored on a second drive)
2. Booting from Acronis boot loader
3. Windows 7 64bit
But just off the top of my head, during the restore/recovery set up process, where it asks you define all the necessary stuff like target drives, etc. ... I noticed some weird language issues that didn't make a whole lot of sense to me.
I left everything default for the most part (just ensured that the main system drive was where I would be restoring to and all.
But one thing that was weird was that when choosing partitions, the main drive I want to restore is actually divided up in to three selectable options 1. some sort of small system reserved space (about 1mb or so) 2. the main 1TB system drive space 3. and the MBR ...
Now that all doesn't sound/look so strange as I know those are all elements of any normal system/primary partition ...
But what didn't really make sense to me was that during the final restore start functions, Acronis called that small "system reserved" space drive C: ... and it called the main system (1TB) data space as drive D: ....
???
It's the drive D: bit that threw me off. Why would Acronis call the main data space, the very thing I'm trying to restore as my "system" ... drive D: ... and recognize that small "system reserved" space as drive C: ??? Shouldn't my main system space be called drive C:?
Does this make sense to anyone?
Thanks for any clarification ... I guess I'll find out what happened when I get home later but thought I'd ramble a bit about some of that process I found confusing ...
.joel
- Accedi per poter commentare
Joel,
But one thing that was weird was that when choosing partitions, the main drive I want to restore is actually divided up in to three selectable options 1. some sort of small system reserved space (about 1mb or so) 2. the main 1TB system drive space 3. and the MBR ...Now that all doesn't sound/look so strange as I know those are all elements of any normal system/primary partition ...
But what didn't really make sense to me was that during the final restore start functions, Acronis called that small "system reserved" space drive C: ... and it called the main system (1TB) data space as drive D: ....
???
It's the drive D: bit that threw me off. Why would Acronis call the main data space, the very thing I'm trying to restore as my "system" ... drive D: ... and recognize that small "system reserved" space as drive C: ??? Shouldn't my main system space be called drive C:?
Yes, this could be normal but it also could be a problem and most certainly, it is confusing.
If using the TI Recovery CD, it is Linux based which assigns drive letters differently than Window so the letter mis-match is between two different drive lettering procedures. This difference is one reason why it is important to assign volumne names to your disk and completely ignore drive letters--which may not match. During a restore, you want to be sure the partiton being restored is the same as was backed up and use disk characteristics (volume names, disk size, partition size, used space, etc) as the matching factors. For example, I suggest that you assign your drive C Windows partition (which is contains Windows and your programs) with a name such as Win7-64_C
Any unique name (11 char or less) will suffice as along a you know what it means. If you have a Data partition or external disk, these should also be user name for clear recognition.
If restoring only Drive C system partiton, click on llink #3 inside my signature below and select item #3 inside that link. This will provide one illustration of how to restore Drive C only. Or, if you restored to a wrong partition, then item #2 will show you how to restore the entire disk.
- Accedi per poter commentare
Thanks for the comments ... and yeah, it simply turned out to be an issue of semantics between Linux and Windows ...
The Linux based Acronis loader (on the boot CD) was calling that little 1mb "System Reserved" area of the partition drive "C:" ... whereas Windows 7 typically doesn't even report that area of a partition as a drive letter at all (it's sort of "invisible" if you will).
But anyway, being a bit familiar already with full image back ups and restores (via DriveImage XML for quite a few years) ... I just sort of stepped through the process this morning and left for work with it set to restore (and to shut the system down when complete); the drive letter semantics were the only thing a little confusing about the process and the rest of the "step-through" dialogue made pretty good sense (using Acronis 12, BTW as I never found any reason making it necessary to upgrade even though I do own V.13 too).
And so I get home today and the system fires up perfectly. No problems. Seamless. I was a bit apprehensive as my main system 1TB drive is a RAID 0 array made up of two 600GB Velociraptor drives (which is why I had to upgrade to Acronis from DriveImage XML as DriveImage didn't support RAID restores). But it went off without a hitch. I'm stoked. Love it when stuff works the first time. Score one for Acronis; I was a huge fan of the free version of Driveimage XML as it was simply bulletproof and dependable but once I went to a RAID based system drive, I had to move on to something a bit more elegant...
As it turns out, the reason my system was crashing shortly after every new boot in to Windows was a hardware issue and not a software issue like I thought and which made me decide to go with a restore; turns out my water cooler pump that serves my two video cards had come loose at the power connector just a little bit and the video card was pushing over 100C and thereby crashing the system. LOL ... I should have checked that first (or otherwise, set up an alert system, DUH!) but was in a hurry this morning and, thinking it was software, just went with a restore. But since my images are never over a week old, it still served as a good training/trial for the software as my system has been solid for over a year now and I've always wondered if the Acronis software would actually work when it came down to crunch time; and, it does.
;-)
Thanks again for the comments..
.joel
- Accedi per poter commentare