For a file that you are unable to back up because it is open, try using the
COPY command from the NT command line prompt. If this is what I think it is,
you won't be able to copy it for the same reason that ADSM can't copy it.

The problem is that the application has opened the file with an attribute
called "DENY_READ". This attribute says that the application will have
*exclusive* access to this file, and that no other applications (including
ADSM) will be able to open this file, even if it is just for read access.

The copygroup serialization parameters (DYNAMIC, STATIC, SHRDYNAMIC, SHRSTATIC)
still depend on whether the OS allows ADSM to open the file. A file opened by
another application with "DENY_READ" is an operating system level of
restriction which ADSM is not designed to circumvent.

Other products that allow you to manage open files (such as OpenFileManager)
are doing some fairly sophisticated things to allow this to happen, including
maintaining the open file in a consistent state for the backup product to read,
while allowing other applications and users to access and update it as normal.
ADSM isn't built to do this, so I would hesitate to call it a "bug". I would
recommend that you contact your local IBM branch and ask that they enter a
formal requirement for this.

Regards,

Andy Raibeck
ADSM Level 2 Support
---------------------- Forwarded by Andrew Raibeck/San Jose/IBM on 06-23-97
11:58 AM ---------------------------
11:58 AM ---------------------------

        ADSM-L @ VM.MARIST.EDU
        06-23-97 12:01 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet

To: ADSM-L @ VM.MARIST.EDU @ internet
cc:
Subject: AW: Backing up open files on NT 4.0

Brad,
the ADSM NT-client seems not to be able to gain access to files that are
in use by any system service. According to the ADSM manual one should
use the option shared static or shared dynamic (for SERialisation) to
get open files backed up.

On IBM's OS/2 the option works, on NT 4.0 it fails. There is 3rd party
software available to solve the problem (e.g. OpenFileManager from St.
Bernards Software), but I think IBM are responsible for the bug.
I need to backup open files, too and try to find workarounds to get all
the open files saved. I hope IBM will fix the bug, as I do not really
want to buy external software to fix IBM's bugs.

Regards,
 Michael
--
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

>----------
>Von:   Brad Lepper[SMTP:lepperb AT DIEBOLD DOT COM]
>Gesendet:      Montag, 23. Juni 1997 15:21
>An:    ADSM-L AT VM.MARIST DOT EDU
>Betreff:       NT 4.0 or FAQ
>
>Hi,
>
>I am brand new to this list.  I couldn't find a FAQ or archive anywhere.  Is
>there one?
>I have a problem that I think may be FAQ material:
>
>I have a remote tape backup server running ADSM 32-bit Windows Version 2
>Release 1, Level 6.
>My workmates and I were using this server to backup regularly under Windows
>NT
>3.51.
>However, when some of us started converting to NT 4.0, we started seeing 2
>failures after doing
>incremental backups.  The failures seem to be involved with the user registry
>hives.
>
>Access denied     C:\...\ntuser.dat.LOG
>Access denied     C:\...\NTUSER.DAT
>
>Am I doing something wrong?  How worried should I be about these failures?
>Any comments or suggestions will be greatly appreciated.
>
>Thanks
>-----------------------------------------------------------------------------
>-
>--------------------------------
>Brad Q. Lepper  work e-mail:  lepperb AT diebold DOT com
>(330)496-5964   home e-mail: brad AT 2-cool DOT com, or lepper AT cannet DOT 
>com
>-----------------------------------------------------------------------------
>-
>--------------------------------
>