Drive Cloner image with RollBack Rx

[spalmer]

Is Drive Cloner Rx wise the the way that snapshots are used. In otherwords will Drive Cloner Rx recognize the RollBack Rx snapshots and include them in the image/clone that is taken, and will it be able to save all your snapshots? The answer is unfortunately no. Drive Cloner will only do a back up of the state in which your machine is in at the snapshot that you are currently in.

So based on this answer, what then is the state of the PC with Rollback v9 after a Drive Cloner image is restored?

[Baldrick]

Originally Posted by spalmer

So based on this answer, what then is the state of the PC with Rollback v9 after a Drive Cloner image is restored?

I would have thought that was obvious...in the state it was in when the image was taken with the snapshot that was 'in use' when the image was taken...well, thatts my understanding!

[spalmer]

Originally Posted by Baldrick

I would have thought that was obvious...in the state it was in when the image was taken with the snapshot that was 'in use' when the image was taken...well, thatts my understanding!

Ok then perhaps I need to be more specific - if Rollback is installed on the restored image, will it work or will a reinstall be required?

[Nick10]

When performing a Disk Image using Drive Cloner Rx - the image will only have a single snapshot; the snapshot (or system configuration) that your PC was in when you've taken the Image... This image will NOT CONTAIN any of the other RollBack Rx snapshots or the RollBack Rx application.

Why is this?

As with all disk imaging applications; these utilities are designed to copy over Windows files and folders. So basically, whatever Windows can see will be able to be copied onto the image.

However, when RollBack Rx is installed there are two components that get installed:

1. The Subconsole, which is the mini OS that boots prior to Windows.
2. The GUI component - which is the Windows component that hooks into the Subconsole

The Subconsole is installed and written directly onto the sectors of the hard drive in its own encrpted form that is invisible to Windows. Since the subconsole can not be seen as a file or folder, it does not get copied over onto the image.

The GUI component is fully visible by Windows and will get copied over onto the image.

The net effect is that you will have an image/clone of a single snapshot. The image will not contain any other snaphots, or the RollBack Rx subconsole (therefore no RollBack Rx). The GUI component will be copied over and you will see a "greyed-out" RollBack Rx Icon on the task bar. This is because it Windows drivers can not communicate with it Subconsole (because it not longer exists in the new image).

You will get this same result with ANY disk imaging application such as Ghost, Acronis etc. even our Drive Cloner Rx.

[Baldrick]

Hence if you have to restore an image taken with any of the aforementioned imaging software, or any other for that matter, whilst you will have available the snapshopt that was current at the time the image was taken you will need to reinstall RB Rx...because the Subconsole will be missing?

But surely reinstalling RB Rx will result in the snapshot being lost...but does that matter as the image should be the same or nearly the same as the snapshot...especially if you snapshot just before you image?

Put me right as to where I am wrong!

Cheers


Baldrick

@ spalmer...I now see what your original question was aimed at! Apologies!

[bgoodman4]

If the above is the case why is there any need to uninstal Rx before imaging?

Or is there?

I have a distinct recollection that the MBR can be damaged somehow if you restore an image. Due to old age (memory failing) and a bit of laziness (I don't want to search the forum threads for a detailed specific answer) I can't recall why or when the MBR issue would raise its ugly head.

I would like to be clear on this point in case I need to restore a DC image at some point.

Why I am asking now.

I had uninstalled Rx to do my PC monthly house cleaning and before I did I imaged using DC. After cleaning I then imaged using Paragon (Rx was not installed). I reinstalled Rx and after a few min of using the PC discovered that something was off. None of my external drives were recognized and a particular program would not open.

At first I thought I would restore using the Paragon image (created from within Windows) but felt it likely the problems occurred during the cleanup and that since the image was created at the end of the cleanup it was likely that this would not solve the problem.

I then actually began to restore using the DC image but was uncertain if I should do so with Rx installed or uninstalled since the image was made with Rx installed.

Thankfully I managed to solve the problems without having to restore at all.

The problem stemmed from TuneUp Utilities 2012. I had recently purchased TuneUp Utilities 2012 (after having used 2008 for 3 years with no problems) and the auto disable feature turned out to be the culprit. The problems disappeared as soon as I uninstalled this program and I have since reinstalled it but with the auto disable feature turned off (so far no issues). This is a shame because my PC was markedly faster with this feature turned on and for the week I had used the program before the clean-up disabled programs were flawlessly activated when called upon (services were started) and then the services were disabled once the program was closed. Considering TU 2012 had identified 13 services that were running when not specifically needed disabling them really did make the PC faster.

SO,,,,,,just in case,,,, I think it wise to get this clear in my mind now so that if I ever run into a similar issue I will be able to proceed promptly and with confidence.

Rx really has spoiled me. I am so used to simply rolling back out of problems that trouble shooting the problem was VERY unpleasant. In this case restoring would only have postponed the problem until (I would expect) the next time I did PC maintenance so its just as well that I resolved the problem the old fashioned way.

[pvsurfer]

Originally Posted by bgoodman4

If the above is the case why is there any need to uninstal Rx before imaging?

That's not actually necessary - it's just one of the various ways to get the disk-imaging job done.

Originally Posted by bgoodman4

I have a distinct recollection that the MBR can be damaged somehow if you restore an image. Due to old age (memory failing) and a bit of laziness (I don't want to search the forum threads for a detailed specific answer) I can't recall why or when the MBR issue would raise its ugly head.

I think that is a possibility with some image-backup programs when restoring a Hot image created with RBRx installed and running. I recall having such a problem several years ago with RBRx and Acronis True Image, but after switching to Drive Snapshot I never again experienced that problem. As mentioned (many times), when successfully restoring a hot-image (without MBR issues), you wind-up restoring only the current snapshot and having to reinstall RBRx, so a few years ago I started making Cold-Raw images in order to faithfully capture all RBRx snapshots (and the RBRx-modified MBR). At the present time, Cold-Raw imaging is the only way to ensure a complete restoration of a Windows-RBRx environment (unless you use Image For Windows and Froggie's Hot-Raw method).

pv

[bgoodman4]

Thank you for your reply but it does not answer my question since that was not the question I was asking.

The question is: If an image was made from within Windows using Drive Cloner and RollBack Rx was installed and running at the time the image was made does it matter if RollBack Rx is installed or not when you do the restore.

I do not care if only the state of the system as of the time the image was made is recovered, I am not concerned with any snapshots that may have existed on the PC at the time of the image (I know they will be lost). I just want to be sure that the restore operation will not cause further problems.

I also understand that Rx will not be functional after the restore even though it was part of the image,,,,at least the GUI was part of the image so the GUI will be there but the sub-console will not be functional. However, this is the source of my concern.

My concern and confusion stems from the idea that if the sub-console is not copied to the image then it should not be written over during a restore,,,, so why is Rx not able to function? Likewise since the restore from Drive Cloner does not copy the MBR would not restoring from a DC image made while Rx was installed leave the MBR at risk. Rx alters the MBR upon installation and since Rx was functional at the time of the image would the MBR not need to access whatever part of Rx it needs to in order to allow a successful boot after the restore?

I am sorry if this is a very stupid question but it is a concern for me and I hope someone will take pity on me and set my mind at ease about it.

[pvsurfer]

Originally Posted by bgoodman4

Thank you for your reply but it does not answer my question since that was not the question I was asking.

Sorry that I did not provide the answer you wanted, but my replies were responsive to those questions which I quoted.

The question is: If an image was made from within Windows using Drive Cloner and RollBack Rx was installed and running at the time the image was made does it matter if RollBack Rx is installed or not when you do the restore.

While I'm not all that familiar with Drive Cloner, I don't believe it should matter if RBRx is installed or not when restoring your hot-image. The outcome should be exactly the same.

My concern and confusion stems from the idea that if the sub-console is not copied to the image then it should not be written over during a restore,,,, so why is Rx not able to function?

Rather than guess, I think I'll defer to Froggie for the answer to this question.


pv

[bgoodman4]

Thanks for trying pvsurfer, much appreciated.