New RollBack Rx version released!

When was Windows Vista expected again?
I have heard some rumors, but I can't tell for sure if the development of the next release is on track.

 

I'm sorry if I don't understand you well, Peter.

So, 01. you install a new hard drive, 02. install Windows (or reimage an OEM Windows), 03. install EF/RB and 04. import recent snapshots.
After that probably update the baseline.
That would be a FD-ISR-like recovery, right?

 

I'm sure I'm being a bit dense here but, if you restore a 4 month old image and then bring it up to date with the an external FDISR archive, isn't that the same as restoring a current image? Or are you only updating the data files (docs etc) rather than the system files as well?

Depending on what you are trying to achieve, an alternative Rollback scenario might be to restore to the, say, 4 month old baseline snapshot and then recover the current data files from the latest snapshot.

Of course, if the hard drive is trashed then we are all only as good as our latest backup

 

This procedure is needed because both FD-ISR and RF/RB don't support restores from a rescue CD.
It needs an installed and functioning Windows setup.
And in this prodecure Peter doesn't need an up-to-date disk image, just an up-do-date snapshot archive.

 

Most probably the same functionality. In FDISR I can do manually, what a frozen snapshot does automatically.
Does RB/EF clean a frozen snapshot AUTOMATICALLY during reboot or do I have to do it manually ?

This has nothing to do with frozen snapshots. FDISR has the same nature, because you can work in only ONE snapshot : the current snapshot and the rest of the snapshots are sleeping until you boot in them. I don't call that frozen.
A frozen snapshot applies to the current snapshot, the work-snapshot.

 

You can setup automagic restores, which take less than a snap. (that's why it's called snapshot )

Son, try to listen, I give you an example:

Snapshot A has document AA, Snapshot B has document BB.
Restore to snapshot A and add document AZZ to it.
Restore to snapshot B and add document BYY to it.
Restore again to snapshot A and notice that document AZZ does not exist.
Restore again to snapshot B and notice that document BYY does not exist.

If you want to retain documents AZZ or BYY, you should take a snapshot, which can be automagically done at any restore.
By the way, documents retain at reboots, until you change the worksnapshot.

 

I'm biting my tongue, ghmppfff.
Explain again why FD-ISR is more robust?

 

To make it clear I will say snapshots of EAZ-FIX are just like archives of FDISR except that u can boot into them in a snap unlike FDISR where first u have to make a snapshot from an archive to boot into it, however u can,t refresh EAZ-FIX snapshots and also they don,t retain any changes made when u boot into them, but instaed u can make another new snapshot that of course takes few seconds only.

 

Sorry Wilbert, you may have to speak more slowly for me

At the risk of become monotonous, I image my Rollback installation regularly using Drive Snapshot. Not necessarily daily, but it wouldn't be much of a hardship to do so automatically. So, if something disasterous happened to the drive then I would simply restore the most recent image. I do daily backups of My Documents etc using Handy Backup so most 'current' data is easy to restore.

Peter is still restoring an image I believe, it is just that it is 4 months old. He is then bringing it up to date with the data he archived earlier using FDISR.

If he had actually wanted to revert to a 4 month old snapshot of his system, say, because he knew that the system was more reliable then, he could obviously do this with Rollback by going back to a snapshot at that time and then restoring his current data from the latest snapshot that was available.

In the 'two messed up snapshots' scenario then I believe that Rollback would have been up for the challenge. It should be no harder than going back to a slightly earlier 'non-messed up' snapshot and recovering any more recent documents from the messed up snapshots.

As you know, snapshots can be setup to be taken automatically at up to 2 hour intervals plus they can trigger on specified executables being run (eg setup.exe) and I always take a snapshot manually before installing any new software.

.....but I could be wrong about all of this

 

I was giving you a hard time, but the source of the problem doesn't matter, does it?
Actually, maybe I want to repeat your actions and see how EF/RB handles that...

 

You are right. I just compared them so that who have not used both, they can understand. However they are not just alike for sure.

 

You are correct, Nextar.
Which only means that we know different ways to accomplish the same goal.
By the way, who was talking fast?

 

To rephrase your appreciated explanation:
FD-ISR snapshots are dynamic, EF/RB snapshots are fixed like printed photographs. Each update requires a new picture like frames in a movie.

 

Ya, right!

 

With the new release it appears you will be able to store the complete snapshot to another media not just the incremental changes.

Hope this is what you were asking for?

Thanks,

Chris

 

I am waiting for this version.

 

Maybe we will be amazed...
How about export to a complete independent archive, and import to a snapshot that only contains the differences compared to the baseline...
Just a thought.