Paul,
FirstDefense-ISR is bit different than GoBack
GoBack grabs changes to the file system real time and stores them in restore
points. One of the drawbacks of GoBack is that it detects defrag activity
as file system changes and will overwrite restore points.
FirstDefense only updates snapshots when it is told to - either by running
manually or via a schedule. Defrag activity doesnt "overwrite" any
snapshots.
GoBack uses the current active operating system as a baseline or starting
place. All changes are based on this image. There is no way to create,
maintain, or keep a T0 or alternative image.
FD keeps separate snapshots not dependant on previous activity. A snapshot
can remain untouched and pristine forever; able to take a user back in time
to any snapshot. Snapshots are removed under user requests only.
GoBack maintains a "rollback stack" of changes based on point-in-time
differences. This stack has a finite size based on a user defined setting
(only available at product install time). When the stack is full, the
chronologically earliest changes are purged. The user is unable to restore
back to any time before that date. Depending on system activity this could
be less than 2 weeks of tracked changes.
FD can maintain snapshots forever, limited only by available disk space.
GoBack requires a uninstall of the product in order to disable its activity.
All GoBack saved changes are lost. Re-installation of GoBack results in the
current OS as the new baseline.
FD can be enabled, disabled, uninstalled, installed at any time. Snapshots
remain intact. Snapshots are removed under user requests only.
- Greg/Raxco Software
Microsoft MVP - Windows File System
Disclaimer: I work for Raxco Software, the maker of FirstDefense, as a
systems engineer in the support department.
Want to email me? Delete ntloader.
