Try the following and Let us know !
1. try to disable open file Backup and check ( Master Server Properties->Client Attrivutes-> WIndows Open file Backup)
from Provious DOC !
1) Simply exclude the problem file, but only if it has been agreed that the
file isn't critical for audit purposes (always get management sign off
before excluding *any* file). In your case, apply an exclusion (to the
client) of "F:\folder\folder\D*_*_*x*.log" (remember - always try to get the
best wildcard pattern that matches the least number of your problem file(s),
*but* doesn't also cover (and thus exclude) too many other non-problem
files).
....or...
2) Shutdown the app (or service) that is writing the data or log file. You
use bpstart_notify and bpend_notify for this, see the manual(s). This way
the app/service is shutdown before the backup starts, and started again
after the backup completes. This is my favourite approach.
....or...
3) If you can't use option 2 *and* the exclude from option 1 covers too many
other files (e.g. a collection of logs in one folder), then I use a
bpstart_notify script to move all the "old", and thus closed, log files to
another folder so that they get secured/backed-up because they no longer
exist in the folder that has the exclusion from option 1. What I mean is, I
move all the closed file to another folder. The exclusion still ensures
that the one or two locked files are excluded, but because the
It just depends how important your files are ;). Most of the time it's a
simple option 1. *BUT* always first check with your friendly neighbourhood
technical application support team. Never, and I mean *never* ever exclude
a file just because you want to.
