Yes, the registry and SAM are included in the System Object/System State
backup.

Those files can't be backed up as "files", because Windows puts an
exclusive lock on them.
So if you try to include system32/config, you just get errors, anyway.

In fact, for Win2K and Win2K3, if you start the command line version of
the client and enter "Q INCLEXCL", you will see that MS now creates a
registry entry that says not to back those up, and TSM honors it.  SO
they get excluded from the FILE part of the backup, whether you create
an EXCLUDE for system32/config or not.

For the System Object/System State backups, TSM calls a microsoft API to
get the information from Windows ; that's why you don't need the files
themselves backed up, and that's how TSM gets around the locks.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
JR Trimark
Sent: Wednesday, April 20, 2005 1:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: JR-Windows 2000 System object


If you include the System Object for Windows 2000 and the
systemstate/systemservices for Windows 2003, will you backup the
registry
and SAM of the server?  According to the TSM Windows Client
documentation
it is recommended that the system32\config directory be excluded, why?
Isn't this where the SAM resides?

thanks in advance