The files are opened for read access (i.e. we intend to read the file
only, not write), with read and write share attributes (i.e. allow other
applications to open the file for read and write access).
I don't know why your application is crashing; you should check with the
author/vendor of that application. If they try to open the file for
exclusive use, perhaps that is why.... but I can not say for sure, since I
do not have access to that application's source code.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
mrkirra2001 <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
03/01/2002 19:24
Please respond to mrkirra2001
To: [EMAIL PROTECTED]
cc:
Subject: Fw: How does client open files for backup?
I asked this question last week, but no responses... I thougt I'd try
again... :-)
/gjs
----- Original Message -----
From: "mrkirra2001" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 8:52 AM
Subject: How does client open files for backup?
> How does the Windows NT client (v4.2) open files for backing up?
>
> Last night we had a situation that TSM was backing up a file and another
> application wanted to open that file for read/writing and the second app
> crashed. I thought TSM open the file so that it allows all other
processes
> to also open the file for either reading or writing. Why else detect
that
a
> file has changed if this wasn't the case?
>
> Thanks
>
> /gjs
>
>
