K
kony
That's a term from danabase management. In this context it means
restoring the last backup.
Yes I know, I was just questioning it as a real strategy to
do anything more than uninstall a bad driver- something that
doesn't necesssarily require a rollback at all.
I do not understand you.
There isn't anything all that positive about a rollback, why
do it? Just turn off system restore and make the regular
backups, since an entire backup certainly covers and gain
you might see from the rollback, plus a lot more coverage.
Please explain the use of the term comprehensive in this context.
Covers more scenarios. Could be a failing drive, a virus, a
bad driver, system instability, etc, etc. The off-drive
backup covers all these instead of several different
strategies that only target a few things (potential
problems) each.
Displace?
Yes, there is no need for a rollback if one has a good
backup strategy. Particularly important might be to keep
backups of OS partition and documents separate, so that your
old docs aren't overwritten. This works nicely into make
backup strategies since the documents are going to change
more often anyway, at least once a system is finalized and
fully configured, in it's everyday-running state.
I am talking about keeping a complete hardware backup of the HD each
morning at 4:00 am. That way if something goes wrong during the day,
depending on the extent of the problem, you can recover the new data
onto a 3rd disk (eg. use xcopy /D and then replace the corrupted HD
with the backup version you made earlier that morning.
That's plenty comprehensive and displaces nothing I am aware of.
Oh, then we have a different definition of rollback. More
often I hear the term used for a driver rollback or misused
to mean a system restore point.