To Walt, > > I came across the articles on archiving log file which posted on Wed, > 07 Aug 2002. > can i have a copy of the shell script regarding on automatically > archive log file in MySql. I m currently writing a perl script on > archiving log file generated by Snort Sensor? This script is run > back-end automatically. > > Thanx :-) evon > > the following is the article: > Message-ID: <[EMAIL PROTECTED]> > > Date: Wed, 07 Aug 2002 10:06:04 -0400 > > From: walt <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > MIME-Version: 1.0 > > To: "Rochester, Dean" <[EMAIL PROTECTED]> > > CC: "MySQL (E-mail) (E-mail)" <[EMAIL PROTECTED]> > > Subject: Re: Archive files in MySql > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > "Rochester, Dean" wrote: > > > Does MySql have archive files of transactions like Oracle does? So > if my > > > database gets hosed between backups I can roll forward the > transaction > > > archives or logs so the database is back to where it was before it > got > > > hosed. > > > > > > Thanks in advance > > > Dean-O > > > > > > > --------------------------------------------------------------------- > > > Before posting, please check: > > > http://www.mysql.com/manual.php (the manual) > > > http://lists.mysql.com/ (the list archive) > > > > > > To request this thread, e-mail <[EMAIL PROTECTED]> > > > To unsubscribe, e-mail <mysql-unsubscribe-kernel=nea- > [EMAIL PROTECTED]> > > > Trouble unsubscribing? Try: > http://lists.mysql.com/php/unsubscribe.php > > yes and no.... > > you can set mysql to use logs (see mysql manual for bin-logs), but > there is no > > way to automatically archive them. What we've done is write a shell > script which > > checks the log size every 5 min and if >= 5mb runs "flush logs" which > starts a > > new log file. It then sleeps for 5 seconds and copies the log file > that is >= 5mb > > to 2 different locations so we have redundancy in the logs, then > deletes the old > > log file from the mysql dir. One other note, if your using replication > and your > > slave server is across a WAN, you'll need to check the status of the > replication > > server before you delete the old log file. In other words, make sure > the slave > > server has caught up with the master after switching logs. I can send > you a copy > > of the scripts if you'd like. > > walt > >
