-----Original Message-----
From: Mark Stapleton [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 8:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Win2k Exclude List
On Mon, 16 Jul 2001 14:53:41 -0700, you wrote:
>> Does anyone have an example exclude list for Win2k that will
>>basically exclude the entire OS and all OS specific files? We're trying
>>to eliminate backing up all unnecessary files/folders that will be
>>restored as part of a separate recovery. Thanks in advance!
>Keep in mind that if you don't back up the OS files, you will have to:
>1. Install the base OS
>2. Install all the service packs
>3. Install all the hotfixes you installed
>4. Rebuild all the configurations, local profiles, and customizations
>that were in place
>And if it's a domain controller or specialized server, you'll lose all
>of the system objects.
>You're *much* better off backing up the OS files (except the ones
>normally excluded). You then do the base OS install and then overlay
>the files and system objects that are backed up.
Does this mean that after a hard drive crash you can reinstall W2K and the
TSM client and then restore everything back to normal from TSM? No need to
reinstall patches or hotfixes? I would think that there are files that
can't be restored (or backed up) by TSM that are changed when things such as
a service pack are installed. By not reinstalling the service pack, yet
restoring only portions of it from the backup you will end up with a system
that is unstable. Without a bare metal restore program, I think that you
would get into more trouble trying to restore the service pack and would be
better off reinstalling the service pack manually.
I use service packs only as an example. There could many other areas in W2K
that behave the same way. Is this really a problem? I should probably
perform a simulated disaster, and answer the question myself.
Scott Foley
NetVoyage Corp.
