Postby GerardO'Brien » Mon Aug 22, 2011 8:55 am
Some antivirus products seem friendlier than others. Some lock access to files or regions within files momentarily, denying the creator/owner access, causing distress. Some never seem to cause an issue.
What can happen isn't really known as antivirus products typically don't publish much about how/why they operate. The database can be denied access to any of its files at any time if the antivirus product is crappy enough. Some products initiate real time processing based on events, like closing a new or updated file. This can include leaping in and locking access to the file while it is checked. Some lock regions so you might see messages logged like
>> [IOCB::_write] error - The process cannot access the file because another process has locked a portion of the file. (33)
It can be wasteful of resources scanning the database files and it can have unintended side effects if the AV product turns out to be a bit of a thug.
If I was going to exclude stuff I would exclude:
.dat files in the database directory (or directories)
.bak files in the <ReorgBackupDirectory> directory (if used), or the database directory (or directories) (if not)
.reo files in the <ReorgWorkDirectory> directory (if used), or the database directory (or directories) (if not)
.log files in the <JournalArchiveDirectory> directory (if used) or the <JournalRootDirectory>\archive directory (if not)
.log files in the <JournalRootDirectory>\current directory
the .empty.jnl$ file in the <JournalRootDirectory>\current directory
the restoreinfo file in the database directory
.dat files, .da_ files, and the backupinfo file in the backup directory (or directories)
.log files and .lo_ files in their backup directory (or directories)