TSM B/A client 5.2.0.3
Client:  Windows 2000 Server

We have some IIS servers where Microsoft is recommending to change the
location of metabase.bin from c:\winnt\system32\inetsrv to a new
subdirectory located at c:\winnt\system32\inetsrv\metabase (see basics
of changes below)

I just want to get some feedback on what the group thinks if there will
be any problems with doing disaster recoveries with these servers.  The
assumption is since IIS (and Windows) knows about the changed location,
when the file is restored back to that location, there should be no
problems with IIS on the recovery.

Looking at dsmsched.log pre and post move, the file gets backed up, but
since it is a Windows system file too, I am just wondering how TSM will
handle it.

Thoughts?

Thanks in advance,

Matt


Changes wanted:


Change Description: Move the IIS metabase.bin file from
c:\winnt\system32\inetsrv to a new subdirectory located at
c:\winnt\system32\inetsrv\metabase and have this new subdirectory
excluded from the NAV realtime scan. 


------------------------------------------------------------
Reason For Change: Microsoft has identified this as a culprit to the
intermittent "resource is currently in use" error.
During business hours, the IIS metabase.bin file changes approximately
every 3 minutes. Since it is a .bin file and is in the c:\winnt\system32
directory structure, the NAV scans (and locks it) each time it changes. 




This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message.  Any 
disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited.