Puremessage Database Renaming - possible?

Hi,

We have PureMessage installed on an Exchange server using a remote SQL server. We want to install another Exchange server with PureMessage using the same remote SQL server. When trying to install PureMessage on the new Exchange server and pointing the database at the SQL Server, the install fails as there are already databases from the original Exchange install with the same names.
Is it possible to rename the databases from the original install and modify the LocalConfig.xml file in C:\Program Files\Sophos\PureMessage\Config\LastKnown\ to reflect those changes or will PureMessage not work after such a change? I couldn't find any info about this, only about moving the databases to another SQL server. I have looked at the LocalConfig.xml file and it looks straightforward enough to change the database names but maybe not...

Thanks

Justin

  • Hi  

    I will need to check this with my team, however could you please provide more details about your environment like is it clustered? Also, the version of the Puremessage you are using? Kindly take a look at this article as well as this one and see if it helps you. 

  • In reply to Shweta:

    Hi, 

    The original PureMessage install is non-clustered version 3.1.4.0 on Exchange 2010, the new one will be on an Exchange 2013 DAG, so no local SQL install possible.

    Justin

    Shweta

    Hi  

    I will need to check this with my team, however could you please provide more details about your environment like is it clustered? Also, the version of the Puremessage you are using? Kindly take a look at this article as well as this one and see if it helps you. 

     

  • In reply to JustinTL:

    Hi  

    As your original server was not installed through the clustered version, you'll not be able to do the installation of the new server on top of that.

    You can move the existing database to another server using this article and then try installing the pure message for exchange for the new server.

    We don't recommend any changes in the local config file as it may disrupt the operation of that pure message for exchange server.

  • In reply to Jasmin:

    Thanks for your reply Jasmin, we don't want to move the database from the original PureMessage install to another SQL Server but keep it on the SQL Server then install PureMessage on a different Exchange server but have the new installation's databases on the same SQL server as the original databses, hence the requirement to rename the databases. If it's not recommended to change the local config then I guess we need to do something different!

    Justin

    Jasmin

    Hi  

    As your original server was not installed through the clustered version, you'll not be able to do the installation of the new server on top of that.

    You can move the existing database to another server using this article and then try installing the pure message for exchange for the new server.

    We don't recommend any changes in the local config file as it may disrupt the operation of that pure message for exchange server.

     

  • In reply to JustinTL:

    Hi  

    The scenario which you are looking for is only possible when you have a clustered installation version where multiple exchange servers will be reporting to a single database which will have all the data with it.