Rolling back disk image
Running Windows 7 64 bit.
Summary: What kind of problems will occur with an image rollback of the system drive?
Will have to register windows... other software?
Details:
I have a backup image of C:\ (system drive). But before trying to rollback I'd like to know what kind of problems I might run into with things like having to re-register my windows install, or perhaps problems with the Adobe tools (I'm running tools from Adobe Cloud on subscription).
I remember from yrs ago, having problems involving having to reregister windows, and possibly other software.
Will Installed products like the adobe tools think they are running on a different system after the rollback?
Hopefully someone who does rollbacks regularly can comment as to what kind of thing I might run into.
A brief outline of how to proceed with a rollback would be appreciated too.
I keep a very detailed diary of every program or Windows or setting change that I make to each of my computers, so that if I have to revert to a backup from a couple weeks ago, I know exactly how to get back to Today. Of course, this does not account for data files that have been changed or added...
Thanks for the good input.
Your technique sounds like very good plan but, man!, that must be time consuming keeping up with all the changes that might occur!
When rolling back the system is restored in its entirety to its state when the backup was created. Software installed and registered at that time will still be installed and registered, including Windows itself. However all subsequent updates, both to Windows and other software will be lost, as will any software installed and registered after the image was created.
Restoring an image is best done from the rescue media and involves you specifying which image file you wish to restore from; which drives/partitions included in the image you wish to restore; and to which drive/partitions you want to direct the restore. You also get the option to restore the MBR though if the system is still booting normally that isn't usually necessary.
When rolling back the system is restored in its entirety to its state when the backup was created.
[...]
Restoring an image is best done from the rescue media and involves you specifying which image file you wish to restore from; which drives/partitions included in the image you wish to restore; and to which drive/partitions you want to direct the restore. You also get the option to restore the MBR though if the system is still booting normally that isn't usually necessary.
Thanks.
One more thing I'd like to ask on this:
My backups are on an external drive that I power from my laptop with usb3 controller running in the expansion card.
I have a hunch that might be a problem when I boot off the cd. Do you think I should copy that backup to an internal drive.
I ask because it is 70GB of data which will take a while to copy over
Just connect the external and boot from the CD. It will be apparent whether the version running from the CD can see the backup drive or not, and if not then yes, copy the backup to a drive ATI can see. I use a similar setup and ATI sees my portable external just fine.
You could run a verification from the CD as a further reassurance everything is OK.
Just connect the external and boot from the CD. It will be apparent whether the version running from the CD can see the backup drive or not, and if not then yes, copy the backup to a drive ATI can see. I use a similar setup and ATI sees my portable external just fine.
You could run a verification from the CD as a further reassurance everything is OK.
Thanks. ATI saw the external and all seemed good to go. I ran a verification to make sure.
Again... good to go.
But, OH dear. It failed part way thru and now the OS cannot be booted at all. There were no error messages that I saw... just a notice that it had failed. But of coure not before it destroyed the working os.
Boy, this sucks.
I think I'll copy the archive over to an internal drive and try it again.
I think I'll copy the archive over to an internal drive and try it again.
Ouch, that's a gut wrencher. If it fails a second time I would download and burn the Partition Wizard bootable CD and do a surface test of the target disk. You have been very unlucky, I've done exactly what you have done so many times with never a single failure.
I keep a very detailed diary of every program or Windows or setting change that I make to each of my computers, so that if I have to revert to a backup from a couple weeks ago, I know exactly how to get back to Today. Of course, this does not account for data files that have been changed or added...Thanks for the good input.
Your technique sounds like very good plan but, man!, that must be time consuming keeping up with all the changes that might occur!
Actually it's not that hard--remember I only keep track of what program updates I install, or important setting changes I might make (like to the Registry).
I use a program called Syncback to automatically back-up all User docs, to two different locations each day (an on-board USB3 stick and a NAS). So for files at least I can always recover to "early this morning".
Harry,
The error message about no OS could be as simple the system is attempting to boot from the wrorng deviice.
Next time you atttempt a boot, do a normal boot into Windows and go into the BIOS first thing and select the correct disk to be booted--even if there is only one disk to select from.
Do you know whether your backup was a partition selection backup ( which included only some partitions) or a disk image backup which included all partitions?
I think I'll copy the archive over to an internal drive and try it again.Ouch, that's a gut wrencher. If it fails a second time I would download and burn the Partition Wizard bootable CD and do a surface test of the target disk. You have been very unlucky, I've done exactly what you have done so many times with never a single failure.
During those times you've done this same kind of action, what do you do if youy backup is both C and the small system partition of something like 200MB?
Acronis advises me to include it in the backup so I did. So my *.tib file has both the C partition and what it sees as F, the small system partition.
When it comes time to tell acronis the target you intend to aim the *.tib at. I see C and F are separate so do I click both of them or what?
I posted what I hope is the answer to your question in your other thread at http://forum.acronis.com/forum/44076. Gets a bit confusing with two threads on the same issue. Anyway here is what I posted -
"When recovering from the CD you are asked, after selecting the archive and the recovery method, to select the items to recover. The options will be Disk 1 and beneath that each partition that was included in the original backup. If your backup included the small (100MB?) partition then it will be shown separately from the C partition. If both are there, and you select both then both will be restored. If only C is there then the small partition was not included in the backup when it was created. That shouldn't matter though.
At the next step you have to choose where the selected partitions are to be located and it will normally offer you the same locations they were in originally but also allow you to set new locations. You should normally use the offered locations rather than opting for New Location, as the latter would change your disk layout and the system may or may not boot afterwards. However that would not have caused the error you have experienced.
If all that is recognisable to you then the subsequent restore failure is not connected with your choice of partitions to be restored and is indicative of some other problem, possibly with the hard disk itself. I've suggested one way of addressing that in your original thread."
So just to round this off, as your image includes both partitions you should select both to restore and restore them to their original locations if that option is still available. (it may not be as the original partitions have been removed by the restore operation)
@GroverH - this isn't a boot issue - the restore operation failed leaving the system with no OS partition at all.
Harry,
The error message about no OS could be as simple the system is attempting to boot from the wrorng deviice.
Next time you atttempt a boot, do a normal boot into Windows and go into the BIOS first thing and select the correct disk to be booted--even if there is only one disk to select from.Do you know whether your backup was a partition selection backup ( which included only some partitions) or a disk image backup which included all partitions?
Harry,
The error message about no OS could be as simple the system is attempting to boot from the wrorng deviice.
Next time you atttempt a boot, do a normal boot into Windows and go into the BIOS first thing and select the correct disk to be booted--even if there is only one disk to select from.
I didn't see any way to tell which is the 'rght' one. But there are only two so I switched to the other one. Booting from that gets the message 'No operating System found'. Whereas booting from the default I get a message 'No bootmgr found' (our very similar).
I suspect that last one about 'bootmgr' probably means its the right disc.
But it was more involved, both when making that bkup and now trying to recover it and run the os with it. ATI 'recommended' I back up both C and a small 200mb 'system' partition ATI sees as F. I followed the recommendation.
Now, when its time to rollback to that bkup ATI shows C and F both with stars one green the other bronze. I don't remember how those stars were set originally, but they probably mean something. Maybe Green is boot partition?
OK, so when I get to the point where I'm asked to select a partition to aim the recovery at, do I select both C&F or what? Remember, the *.tib has both inside. If I select one or the other, does ATI know to use only the 'right' one in the *.tib or does ATI just pour out the backup where ever I select...?
I selected just C... as the target on first attempt, ATI failed DURING that recovery attempt. Does that mean ATI is likely to have overwritten C with both C and F? And hence now unbootable?
I thought the failed recovery might have something to do with that bkup being on an external drive so I moved the *.tib to an internal drive and tried again. That time the recovery completed but again left a non-bootable situation.
Oh, and after the first failure I did do another verification of the bkup, which showed good.
Do you know whether your backup was a partition selection backup ( which included only some partitions) or a disk image backup which included all partitions?
The disc that C is on is partitioned. The disc is 500GB, C is only 159GB, then F which is also a partition of that same 500 GB disc, is only 200MB and is labeled as 'system'. That one is not listed as a partition in windows explorer... it is not shown there at all. But ATI sees it. So to answer your question I guess it was a 'Partition selection backup'.
What I backed up in this particular *.tib was only C and F, not the entire 500 GB disc.
Still not sure how to aim it for the recovery attempt... Just at C or both C & F and let ATI figure it out?
[/quote]
Harry, the boot files are in the 200mb partition, so if you only restored C, and if the small partition has also been erased, then it won't boot. You need to restore both partitions, as I said in #11
Harry, the boot files are in the 200mb partition, so if you only restored C, and if the small partition has also been erased, then it won't boot. You need to restore both partitions, as I said in #11
I've got a little more information now but hasn't been particularly useful.
After burning the PartitionWiz.iso to disc and booting with it. I have that up right now. It has lots of functions including an explorer much like windows explorer.
In that explorer I can see the small 200mb partition I mentioned and it has the boot files, including 'bootmgr' so not sure why it is missing on boot. Apparently trying to boot from the wrong partition (That would be the C partition in this case).
One item you can do on right click with partWiz is called: Set Windows Boot Partition. Apparently different from setting the 'Active' partition since that is another option,
If you attempt to set a partition as 'Windows Boot Partition' the tool apparently searches that partition for the windows directory. When I tried that on the partition I've just successfully written my backup too (C), it says it 'cannot find the windows directory' , but when I look with the explorer tool I see it full of directories and files.
I suspect this PartWiz tool may not be of the first order. So not sure I can really do much with it.
I plan to try setting the small 200mb partition that ATI sees as F. The one that has the boot files as active and then try booting.... I'll report back
Just set the 200mb partition Active and reboot.
Paraphrasing here by -hp. Hey pin head, why are you posting about this in two different threads.
Yeah, sorry about that, at first I thought it would help to have all 'recovery from failure' stuff in a different thread since this thread was initally asking how to proceed with a rollback. But it was a boneheaded idea. Hoping to just stay with this one now, and posted that fact on the other one.
"When recovering from the CD you are asked, after selecting the archive and the recovery method, to select the items to recover. The options will be Disk 1 and beneath that each partition that was included in the original backup. If your backup included the small (100MB?) partition then it will be shown separately from the C partition. If both are there, and you select both then both will be restored. If only C is there then the small partition was not included in the backup when it was created. That shouldn't matter though.
At the next step you have to choose where the selected partitions are to be located and it will normally offer you the same locations they were in originally but also allow you to set new locations. You should normally use the offered locations rather than opting for New Location, as the latter would change your disk layout and the system may or may not boot afterwards. However that would not have caused the error you have experienced.
If all that is recognisable to you then the subsequent restore failure is not connected with your choice of partitions to be restored and is indicative of some other problem, possibly with the hard disk itself. I've suggested one way of addressing that in your original thread."
First, thanks for clearing the proceedure up. It kept seeming like I was asked to do the same thing twice and that was confusing me, but your explanation makes it clear.
However I think (on my second attempt I must have stumbled thru it like its supposed to be done. It completed successfully). It just won't boot. I'm thinking it is still some kind of boot problem. Possibly having the wrong partition set as active or some other way causing the the boot up to look in the wrong place for bootmgr.
Part of why I'm thinking that is; now that I have it open with PartitionWizard, I can see the files for booting including 'bootmgr' are in the small partition (as a couple of people have already mentioned they would be). I can also see what appears to be an intact Windows directory on the partition I targetted during the restore, along with the myriad other directories and files one associates with a working OS.
So there are a lot of files in both places. However I'm running what I think you suggested right now. On partitoinWiz... under the Disk menu - Something like Surface scan or Surface chk... I can't look right now as the test is running... looks like its going to take a good long time.
This test appears to be looking for read errors. I hope that is the one you meant. I don't see any other kinds of tests under the disk menu. According to the progress shown... it is 1hr 11min and 13 seconds away from completion.
If the test pronounces my disk ok, then I'm going to try the restore again after having set the boot partition, the one with 'bootmgr' in it, as active.
[...]
If the test pronounces my disk ok, then I'm going to try the restore again after having set the boot partition, the one with 'bootmgr' in it, as active.
EEEEEHAWWWWW. It worked, It worked. I take back every mean nasty horrrible hex and curse I aimed at you Mr. Acronis . . . . You da man.
Having gone carefully thru the process for the third time. And making sure the correct little partition was set to active... It worked as advertised.
Thanks to all you posters who joined in on this ... I learned more in this one go around than I have in some 10 yrs, maybe more, of off and on use of acronis.
Harry,
Your needed technical help came from "was Earthling". He is the one that use perseverance to help you and deserving of the thanks.
It you have some spare reading time, link #2 and link #3 below can be helpful.
Phew! That was a close one. I'm as relieved as you are Harry - hate to see a system lost when the user has done all the right things. It does make me wonder though whether I'm doing the right thing always advising ppl to use Acronis, as with those not so technically minded it does seem to cause endless confusion. There are competing products, even free ones, which are rather more straightforward to use due to having a better designed user interface.
But no one can argue about its competence when used correctly. It's a lifesaver.
I often "roll back" to an earlier point in time of the OS, by restoring just my C: partition. I often do this if a system glitch appears and I'm uncertain exactly when it occurred and it's difficult to fix; I roll back by restoring an older backup from a date before the glitch. I've never had any problems doing this.
Naturally if you had installed new software or completed some new registration after that backup, then those changes would not be present in the system when you restore that backup. That's not really an issue of any particular backup tool, just simple time logic.
Having plenty of TARDIS experience may help.