Jerry,
your question was "how to remove the symptom". To remove the problem -
remove Windows, period.
In Windows you have two options:
1. Backup "System Object". Read carefully - it is singular not plural. All
binaries + DLLs + registry + (optional) other system components = (one)
System Object. That single object is backed up as a whole. If any
component of it is changed the whole is assumed changed and is backed up.
Same as for file backup - if few bytes are changed the whole file is
backed up. The problem is that %$#$% System Object is terribly huge.
2. Backup parts independently - exclude the %$^$% Object, backup
executables & DLLs and develop some own solution for registry, event logs,
AD, MSCS Cluster DB, etc. You are on your own. Otherwise you have to rely
on M$ and use option 1.
Sorry.
Zlatko Krastev
IT Consultant
"Lawson, Jerry W (ETSD, IT)" <jlawson AT THEHARTFORD DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
16.10.2002 14:47
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: More on Repeat Backups...
Date: October 16, 2002 Time: 7:31 AM
From: Jerry Lawson
The Hartford Insurance Group
860 547-2960 jlawson AT thehartford DOT com
----------------------------------------------------------------------------
-
First - let me thank you all for the responses to my original question.
Your answers have gotten me thinking some - I say some, because at my age,
it's hard to get everything going again, and I suffer from "senior
moments"
too often.
Most of the answers revolved around the suggestion that I could exclude
something - either the files themselves, or the System Object itself if I
get the newest client. This seems to me to be treating the symptom,
rather
than the problem - if I exclude them, obviously, I can never restore them
(DUH!). If these do get corrupted or deleted, it would appear that I
could
be in for another bout with my desktop support folks - they just had my
Laptop for 3 weeks - I'm not eager to deal with them again. Now I will be
the first to admit that I'm not MS Certified on any OS, and so the idea of
excluding the whole System Object is scary as well - doesn't that include
a
big portion of registry information if I need to do a complete restore? Or
is the idea of a Bare Metal restore with TSM one that has died?
In my (sometimes overly simplistic) mind, I remember the ADSM class I
attended where the instructor identified how a file was determined to have
changed - either the date, the time, or the size has changed. Has TSM
changed this philosophy? After all, I look at the files in question, and
nothing has changed that I can see externally. Shouldn't there be a
better
approach than to say "well, they're a part of the system object, and
therefore you need to exclude them." Shouldn't the software be smart
enough
to figure this out?
----------------------------------------------------------------------------
-
Jerry (still tilting
at
windmills)
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all
copies.
|
