Discussion in 'backup, imaging & disk mgmt' started by guest, Aug 7, 2013.
^^ This. Every last word.
That in my opinion would be a mistake by removing Macrium which is rock solid, with Rollback new freeware. If it wasn't reliable before, how will the watered down new version be?
I have tried the new freeware rollback and got the same HAL error coming out of sleep mode that I got with version 10 a couple of years back, when customer support advised me to stop using it.
Installed Rollback Home Edition
Backed up system
Disabled system restore
Windows update set to notify
Can anyone give me Rollback Home forum thread link where they give info about released windows updates i.e released windows updates are compatible with Rollback Home or not?
I will bookmark it.
Sorry posting here.
My Rollback Home thread here is closed.
I guess admin didn't liked some users offtopic posts & closed the thread.
Yesnoo, HERE's the "Approved Updates" thread...
Going forward, lets use this thread for Rollback posts, either on Pro or home. When a new version is released, I'll leave it to Froggie to start a new thead
Many of us who used Norton GoBack tried to make the switch to Rollback Rx because
the NT kernel and GoBack were not compatible.
Years ago I purchased a very early version of Rollback and had lots of problems. I don't
know how much Rollback has changed or been improved since I tried that early version.
Tell me if these statements are still true:
1. Any RAID configuration (including RAID 0) is not compatible with Rollback. Correct?
2. The only completely reliable system backup is created with imaging software like Acronis
True Image. I have ATI on a BartPE disk and a bootable USB stick. Creating an image backup
was easy with Norton GoBack. You just clicked a button to disable the app and rebooted.
I created hundreds of image backups with GoBack disabled. What about the latest version of
Rollback? Do you still have to completely uninstall the app to create an image, or have the
authors fixed this problem?
The RAID issue, I believe, has been dealt with.
Imaging a Rollback system is still, basically, a mess for simple users. If you want a fully restorable, minimal image... Rollback must be uninstalled before imaging. This will give you the Current System State (no snapshots) in your image. If you image with Rollback installed, you will get the Current System State, an unBOOTable Master BOOT Record and no snapshots when you restore. If you do OffLine image (WinPE/Linux-based imaging operations)... unless it's an ALL SECTOR (Raw, Sector-by-Sector, etc.) image, you will get only your BASELINE Rollback image and it will unBOOTable. An OffLine ALL SECTOR (entire partition, not just "used" sectors) image should return your system (and snapshots) to their proper state.
Basically, it's still a mess as far as imaging is concerned.
Thank you TheRollbackFrog.
Without a doubt, the most depressing experience I've ever had with countless apps was Rollback!
I know people either loved or hated Norton GoBack. For me, GoBack was the most remarkable
app ever created. Knowing exactly when to enable or disable GoBack was to key to using this
app with great success. Most people who hated GoBack never really understood how it worked.
GoBack kept an amazing log of every event that occurred with your operating system. You could
literally split hairs with this app! The log was not a pretty display like Windows Explorer. It was
simply a very long list of command lines.
I wish I had expert level programming skills. I would create an open source version of GoBack
compatible with the latest Windows systems.
Has Horizon really made Rollback compatible with RAID? If true, that's a remarkable accomplishment.
I backup everything. It's almost embarassing how many partial and full backups I keep. That's the
only way I feel comfortable. I could delete the entire Registry and restore my system from a backup
in 5-to-10 minutes.
After googling about problems with uninstalling and reinstalling Rollback, I don't see how I could ever
try this app again. I use Advanced Uninstaller Pro, which does a good job of deleting everything when
you uninstall an app.
I just can't see myself constantly uninstalling and reinstalling Rollback just to create an image backup.
The finer details are that any experienced user can work around this limitation. Right now I see 4 different methods:
1. If your OS version is not higher than Win7 (32bit and 64bit) you can use RollBack 9.1. The restored HOT image will be bootable.
2. Save your MBR before installing Rollback using MBR tools like BootICE or similar. After restorig the HOT image do not try to boot into Windows right away, instead restore your saved MBR first.
3. Use Macrium Reflect for your image backups. The recovery media has an option to repair Windows boot problems. Use this option after a restore.
4. In a recent test VEEAM Endpoint backup free was able to boot into Windows after a restore of a HOT backup with Rollback 10.4 installed without the need to restore the pre-Rollback MBR.
I was also a big fan of GoBack, and it still works nicely under WinXP (but it does slow down the computer quite a bit). Despite all the negative comments about RollBack I still see it as a godsend for someone like me who needs to quickly switch between snapshots. Just don't take it as a backup solution (as the HDS advertising suggests).
Thanks for mentioning VEEAM ... Have never heard of it before this.
Will check it out, my ancient machine with RX & XP needs something light-weight.
There is an older thread about VEEAM right here on Wilders, that's why I tried it...
The concept is very similar to AX64/Flashback, only without the fast delta restore. And another major difference is that it comes from a company which mainly is active in the corporate world. The free endpoint backup software comes from a huge corporate software, you can tell it by its sheer size.
But the limitations are also similar to AX64:
The recovery media cannot be used to make backups.
No way to verify images.
Mab, doesn't that seem a bit scary to you? Why would the app be replacinging the "imaged" MBR all on its own... or is it restoring a standard MBR on its own regardless (maybe it doesn't even image the MBR to begin with).
I would be concerned (without additional knowledge)... especially if I was a BIBM user, forget about Rollback.
I have no idea if VEEAM restores its own standard MBR or if it somehow circumvents the Rollback system driver when it does a hot backup. But why should I care? I tried it on a NON-UEFI / NON-GPT Win64 system, and if it consistently works, no problem, whatever floats my boat...
And sorry, the Terabyte Unlimited stuff is not for me. I am not a noob, but this stuff is just too much hassle.
Separate names with a comma.