Item Subject: NT Backups
     Use shared dynamic for your serialization...

     Static         Quit immediately if the file is being changed.

     Shared Static  Retry a few times.  If the file is being changed, quit.

     Dynamic        Copy the file even if it is being changed.

     Shared Dynamic Retry a few times.  Even if the file is in use, copy
     it.




______________________________ Reply Separator _________________________________
Subject: NT Backups
Author:  ADSM-L at unix,sh/dd.RFC-822=ADSM-L\@VM\.MARIST\.EDU
Date:    8/22/96 2:27 PM


I received the following question from one of my clients. Does anyone have any i
ormation on this? Thanks for any help.
 You may have already been asked this, but just in case.  Windows NT servers
 often maintain files in an "open" state.  Such a state renders ADSM useless
 for NT server backups as these essential "open" files are skipped.

 Other vendors tackle this problem by implementing special "handlers" or
 "agents" which are knowledgeable of the application's files.  The "agents"
 are then able to safely and completely backup application "open" files.

 Does IBM have any plans to implement such "agents" for Windows NT (EXCHANGE
 is the application of most interest at this time?  Other applications will be
 involved later on.) If so what is the timeframe for availability?