Hi Btrivieans!

again I have a question:

System ist Windows 200 Serv or Windows 2003 Server running PSQL 8.6 and BA 1.0

If you open a btrieve-file while Backup-Agent is active, than this file will
"touched" (it gets a actual timestamp) when BA is turned off, even if there
where definitely no write-operatin on that file. More than that: eben if the
file is opened "read-only", the file is touched if you stop the BackupAgent.

Is there a patch for PSQL 8.6 to avoid this errornous "touching"?

Will PSQL9.x have the same error?

Or can one influence that behaviour in any way (options for PSQL or BA or what
ever)?

Any hint will be wellcome!


Regards
M. Malarski

I know that there is no patch available for what you are talking
about. I don't know why it would be a problem except that incremental
backups would get bigger.

The mere act of putting a file into continuous operations does update
the file. There is a bit written to the header page to indicate file
state. Backup agent puts files into continuous mode when they get
opened. Depending on backup software used an open data file is open
read-write at the OS level even if opened read-only by the application
so backups may not work without putting the file into continuous
operations anyway.

I believe it is "working as designed" as described however it could
probably be enhanced for BA to ignore read-only opens. I wold urge
you to contact Pervasive directly.

If the file is always opened read-only you could add it to the "ignore
list" for Backup Agent with BA 1.1. Keep in mind that would ignore
all file opens for the file not just read-only ones.

Leonard

On Sat, 16 Sep 2006 21:21:52 +0200, nmm
<Mircea.Malarski (AT) onlinehome (DOT) de> wrote:

A few comments on this thread:
1) You cannot use BA1.1 with PSQLV8. Upgrading to PSQLv9 would be
required if you wanted to use the "exclude list".
2) You CAN, of course, use the "Continuous Operations Mode" manually,
without using BA. Full details are in the product manuals, or a
quick-start document can be found at www.goldstarsoftware.com/press.asp
in the white paper on backups. Going this route is a bit more work,
but you control exactly which files you want touched by the backup
process.
(Keep in mind that any files that are unprotected that DO get updated
may be mangled on the backup tape...)
BB

Leonard wrote: