Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 0 subscribers
  • Views 6952 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

Relocate Puremessage databases

Quicksilver
Scenario: We have a Windows 2003 Server hosting the Puremessage databases on SQL 2005. Instance name: Sophos The Exchange 2010 server connects to the SQL box. We recently created a new Virtual server with SQL 2008 R2 and need to have the Puremessage databases relocated to this machine. We urgently need to relocate the Puremessage databases to the new server hosting SQL 2008. What would the easiest and safest method be to faciliate the change? Thank You
:28517


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

    Hi,

    I would recommend working with Sophos Support on this, as the following steps would need to be performed:

    1. A new instance be created on the new SQL server.
    2. Copying over the four LDB and MDB files associated with PureMessage from the old SQL server to the new one.
    3. Ensure that connectivity to the new SQL server is possible from any Exchange server.
    4. Modify the PureMessage configuration files to point to the new server.

    The tricky part will be prior to Step 4 if email is still flowing through the server, since quarantine actions and reporting would be impacted during the move. Support would be able to help to minimize disruption, aid with the configuration file syntax via some in-house tools and confirm that the new database is being written to. There's a good chance that something can break in the midst of all that, but one of our support engineers can directly assist to ensure a smooth transition to your new database environment.

    :28555
Reply
  • 0

    Hi,

    I would recommend working with Sophos Support on this, as the following steps would need to be performed:

    1. A new instance be created on the new SQL server.
    2. Copying over the four LDB and MDB files associated with PureMessage from the old SQL server to the new one.
    3. Ensure that connectivity to the new SQL server is possible from any Exchange server.
    4. Modify the PureMessage configuration files to point to the new server.

    The tricky part will be prior to Step 4 if email is still flowing through the server, since quarantine actions and reporting would be impacted during the move. Support would be able to help to minimize disruption, aid with the configuration file syntax via some in-house tools and confirm that the new database is being written to. There's a good chance that something can break in the midst of all that, but one of our support engineers can directly assist to ensure a smooth transition to your new database environment.

    :28555
Children
No Data
Unfiltered HTML