You are correct. The AV scan should not happen unless the database is shutdown or some kind of file locking contention could occur.
It should be possible in your OS to deny your AV access to the folders that contain your database files. This may mean changing the user account your AV runs under and/or modifying the permissions on the folders. But first, I would attempt to add your data folders into the "exceptions" list so that NAV will avoid scanning those folders. You may also want to put your server executable (mysqld or whichever variant you use) into the "do not interfere" programs list (The names may be different in the version you use but all good AV software has facilities to make exceptions to what gets scanned and which ports and processes are monitored) It's my firm belief that no process and nobody should be able to touch (lock, read, anything) my datafiles except the server executable itself and possibly a backup process (one that I approve of and coordinate the server with). I think that most DBA's will agree with that philosophy. Shawn Green Database Administrator Unimin Corporation - Spruce Pine matt_lists <[EMAIL PROTECTED]> wrote on 12/29/2004 03:01:45 PM: > How does everyone handle antivirus's and file locking issues? > > I've been fighting with our sysadmin for weeks, I insist that norton > should not touch our database files, innodb, myd, myi > > now it does, and I see corrupt data, and norton will skip files because > it cant get a lock, I dont want to think about the files it locked when > mysql was writing data to them > > it's hard to tie the corrupt data to the norton locks on myd files, but > it's the only thing I've been able to tie together so far > > data corruption involves data in the table skewed, I've had table > crashes, but not on the files norton cant get a lock on > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] >
