This does not get me any closer to backing up these files now that
I know why they are not being backed up.  I do not feel comfortable
using Veritas or any other "non-IBM" ("non-Tivoli") system.
(e.g. Arcserve used to support the V2 client in its "Backup Client for
Open Files" product, but now they only support CA products, is an
example of why I would like to have a native Tivoli solution.)

How are others handling this?  It would seem to me to be a major
concern to most people.

Howard Heitner
McGill University
Computing Center

--------------------------- Original Message ---------------------------
Mark,
Mark,
ADSM is not able to backup files that are open and locked (exclusively
opened by a process).
Open files (e.g. from MS Office) are backed up without problems, it only can
happen that ADSM has to start over with a file when it gets changed during
backup.
Exclusively open files (databases, registry files in system32\config,...)
cannot get backed up directly by the backup client. 

For the registry ADSM has a builtin procedure that uses NT API funtions to
write the registry contents to a different location (c:\adsm.sys\...) where
the files then are not open and can get backed up easily).

For any other files you cannot backup directly you have to find another
strategy for your backup. Let us take an Exchange database as an example;
you won't get backed up priv.edb and pub.edb when the server is running. Now
there are some possibilities:
Stop the Exchange server (now those files aren't open), do the backup,
restart Exchange
Use the ADSMConnect agent for MS Exchange
Use an alternative online backup like Veritas BackupExec with the ADSM
Option

Regards,
Michael