Eric,

You can use the client QUERY SYSTEMINFO command to see which files are
protected by Windows system file protection, and are thus part of the
system state.

   dsmc query systeminfo sfp

will list all system-protected files.

   dsmc query systeminfo sfp=fully-qualified-file-name -console

will tell you whether fully-qualified-file-name is system-protected.

For example:

   dsmc query systeminfo sfp=c:\windows\system32\xcopy.exe -console

should indicate that, indeed, this is a protected file.

Per Microsoft specification, system-protected files are part of the system
state, and system state backup and restore is an "all or nothing"
proposition. Therefore TSM does not permit backup or restore of individual
system state components.

Now, the question to you is, why do you need to restore xcopy.exe?

There should be no need for you to restore xcopy.exe or any other
system-protected file. As a test, go into your c:\windows\system32
directory. Do a "dir" for xcopy.exe. Then delete the file. Wait a few
seconds, then do the "dir" again. You should see the file restored. (Note:
you might want to copy xcopy.exe just as a precaution, but system file
protection is a standard feature of Windows 2000, XP, and 2003, and
something would have to be seriously wrong with your OS for xcopy.exe to
not be restored.)

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/09/2006
02:24:19 AM:

> Hi *SM-ers!
> Sorry for the repost. On the list server itself I saw that my mail from
> yesterday did make it to the list. I don't know why I don't see it
> myself, nor do I see the replies on my post... Although I receive posts
> from adsm-l it looks like I do not receive all of them...
> If xcopy.exe is part of the System Objects, what if I would like to
> restore only this file? It doesn't seem to be possible, because TSM
> stores all System Object\System Files as one single object...
> Kindest regards,
> Eric van Loon
>
>       Isn't this part of the system object?
>
>       Regards,
>
>       Karel
>
>
>       -----Original Message-----
>       From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> On Behalf Of
>       Loon, E.J. van - SPLXM
>       Sent: woensdag 8 februari 2006 10:40
>       To: ADSM-L AT VM.MARIST DOT EDU
>       Subject: 5.3.2 client misses files after backup?!?!?!?
>       Importance: High
>
>       Hi *SM-ers!
>       We discovered something very alarming here. We have two
> Windows XP 5.3.2
>       clients and on both of them file backups are missing.
>       When I start the GUI, click on the backup button and
> navigate to the
>       c:\windows\system32 directory it doesn't list all files!
> For instance,
>       the file xcopy.exe is not listed and thus not backed up
> during an
>       incremental.
>       The files are NOT excluded (in that case, they would be
> visible through
>       the interface with the exclude icon in front of the
> filename) so I
>       cannot think of any reason why it's not seen by TSM!
>       Could anyone check to see if they see similar behavior
> on their Windows
>       XP client, using the 5.3.2 client?
>       Kindest regards,
>       Eric van Loon
>       KLM Royal Dutch Airlines
>
>
> **********************************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee
> only. If you are not the addressee, you are notified that no part of
> the e-mail or any attachment may be disclosed, copied or
> distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message. Koninklijke Luchtvaart
> Maatschappij NV (KLM), its subsidiaries and/or its employees shall
> not be liable for the incorrect or incomplete transmission of this
> e-mail or any attachments, nor responsible for any delay in receipt.
> **********************************************************************