SQL Logging After the Fact {Scanned by HJMS}

[Steve Freegard]

Chris,

Just a thought - I've haven't used it (yet!) - but would MySQL replication
do what you want???

Alternativly - you should be able to easily achieve this manually by using
mysqldump with a couple of switches to dump the data during the timestamp
ranges the main server was unavailable then run sed over the resultant file
to change the 'INSERT INTO' lines into 'REPLACE INTO' and away you go.

Kind regards,
Steve.

-----Original Message-----
From: Chris Trudeau
To: MAILSCANNER at JISCMAIL.AC.UK
Sent: 10/7/03 5:04 PM
Subject: Re: SQL Logging  After the Fact {Scanned by HJMS}

Trever...

Looked through the archives and through my MailScanner folder and can't
seem
to find the CustomerConfig.pm you refer to....could you re-post it at
your
convenience?

Thanks!

In addition, I agree that both machines logging to a central db makes
sense,
unfortunately, I only have two sites.  So if a pipe goes down, I have
the
same problem...I think your suggestion is a good one though.  I could
log to
a single database AND add the logging function for each mailscanner
instance...that would alleviate the risk associated with logging to a
single
db.

allowing recovery/playback of logfiles...Seems to me as long as the
replay
into the database validates timestamp/messageID comparisons and doesn't
allow duplicate entries the process of recovery could be pretty easy.

CT



----- Original Message -----
From: "Furnish, Trever G" <TGFurnish at HERFF-JONES.COM>
To: <MAILSCANNER at JISCMAIL.AC.UK>
Sent: Tuesday, October 07, 2003 9:31 AM
Subject: Re: SQL Logging After the Fact {Scanned by HJMS}


> About a month ago I posted a CustomConfig.pm that would allow logging
the
> same stuff that goes into the sql logging but send it to three flat
files.
> You could use that, though ymmv.  On the other hand, you could just
log
from
> both machines to a third database system.  That would leave you with a
> single-point-of-failure in the remote database though.
>
> > -----Original Message-----
> > From: Chris Trudeau [mailto:chris at TRUDEAU.ORG]
> > Sent: Monday, October 06, 2003 2:06 PM
> > To: MAILSCANNER at JISCMAIL.AC.UK
> > Subject: SQL Logging After the Fact {Scanned by HJMS}
> >
> >
> > I have a primary/secondary configuration as it stands now.
> >
> > I have all logging happening in realtime using the MailWatch logging
> > functionality (and I love it)  Thanks Steve.
> >
> > I am treating these as totally stand alone systems...in that
> > if the primary
> > fails AT ALL, 100% of mail traffic will fail to the secondary via
DNS
> > weighted MX.
> >
> > When in a state where the secondary is handling production
> > traffic, the SQL
> > logging is logging to its own MySQL db so that it is totally
> > independent of
> > the Primary.
> >
> > I would like to assimilate all logging data back into the
> > production system
> > upon successfuly recovery, to ensure I haven't lost any
> > logging information.
> > Is there a way to log as verbosely to a log file WHILE
> > writing to the temp
> > logfiles, allowing me to-replay these logs back into the
> > production database
> > upon recovery or daily or whenever?
> >
> > Does my request make sense or am I not communicating effectively?
> >
> > CT
> >

--
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender and delete the message from your mailbox.

This footnote also confirms that this email message has been swept by
MailScanner (www.mailscanner.info) for the presence of computer viruses.