Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 0 subscribers
  • Views 12502 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PureMessage Exchange and SQL Downtime?

ricdgr

Hi,

What happens when the SQL Server used by Puremessage Exchange is not available?

Is all email traffic blocked? Or just the spam actions are impacted?

Thanks

:42878


This thread was automatically locked due to age.
Parents
  • 0

    I have just tested this scenario as best I can by setting up an instance of PureMessage with a remote database and then testing with / without the database instance running.

    With the database stopped, mail continues to flow, which is good.

    The usual "Sophos Update has completed an update on PureMessage spam rules" continues to be logged in the Application event log at regular intervals.

    I can also confirm that some sort of scanning must still take place, as a test e-mail with a blocked phrase created an alert e-mail and generated the following event in the Application log of the PureMessage server:

    Database was unavailable while trying to quarantine message '<b1efda52-1485-449d-a2db-e3416bc98868@EX1.domain.com>'. Message has been queued for quarantining. Please check the database availability

    I also see events as follows:

    Reporting data could not be written to the database at this time (error: -3).  Additional attempts will be made for 3 days.

    Nothing was logged to confirm PureMessage reconnected to the database, but the quarantined message appeared in the PureMessage quarantine list approximately 5 minutes after I restarted the SQL instance.

    I hope that helps others looking for answers to this question.

    Best regards,

    Simon.

    :43717
Reply
  • 0

    I have just tested this scenario as best I can by setting up an instance of PureMessage with a remote database and then testing with / without the database instance running.

    With the database stopped, mail continues to flow, which is good.

    The usual "Sophos Update has completed an update on PureMessage spam rules" continues to be logged in the Application event log at regular intervals.

    I can also confirm that some sort of scanning must still take place, as a test e-mail with a blocked phrase created an alert e-mail and generated the following event in the Application log of the PureMessage server:

    Database was unavailable while trying to quarantine message '<b1efda52-1485-449d-a2db-e3416bc98868@EX1.domain.com>'. Message has been queued for quarantining. Please check the database availability

    I also see events as follows:

    Reporting data could not be written to the database at this time (error: -3).  Additional attempts will be made for 3 days.

    Nothing was logged to confirm PureMessage reconnected to the database, but the quarantined message appeared in the PureMessage quarantine list approximately 5 minutes after I restarted the SQL instance.

    I hope that helps others looking for answers to this question.

    Best regards,

    Simon.

    :43717
Children
No Data
Unfiltered HTML