Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 925 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

Upgrade from SECv3 to SECv4.5

toddh

Hello,

I am looking to upgrade from SECv3 to SECv4.5

Our current installation is running SQL Enterprise Sever 2000

I know for the upgrade to work I have to upgrade the SQL server to either 2005 or 2008

We would like to move to SQL Express Server 2008, however I have no been able to find any documentation that says I can take this upgrade path.

Has anyone taken this path before?

If I can't take this path, I wanted to try installing SQL Express Server 2008 and attach the Sophos databases to a new instance running under the SQL Express server 2008.

Does anyone know if it is possible at some point during the upgrade to point to another SQL instance?

Thank you

Cheers

:5174


This thread was automatically locked due to age.
  • 0

    Hi,

    I would be inclined to suggest the following approach:

    1. Install a new SQL 2008 instance (call it SOPHOS but anything should do) or use an existing instance.

    2. Run the SEC 3 installer on the new instance to create a SOPHOS3 database.

    3. At your SEC server stop the Sophos Management Service.

    4. Run from the DB directory:

         backupdb.bat with the necessary switches to create you a DB backup file.

    5. Move the file to the new SQL 2008 server and use restoreDB.bat to restore the database into the SOPHOS3 database, it will use overwrite.

    6. On the SEC server go into Add/Remote programs and choose modify on the Enterprise Console package and remove the database role.  The installer should then ask you where the database now resides,  it will also ask for an account that the Sophos Management service will use to connect to the remote SQL instance.  This account must be a member of the "Sophos DB Admins" group on the new SQL 2008 server.

    Once the redirection has taken place, you can confirm this by checking the key:

    DatabaseConnectionMS

    under:

    HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\

    You might also like to check that the values under:
    HKLM\SOFTWARE\Sophos\EE\Management Tools\DatabaseUser\

    reference the correct account.  The right domain name is listed, etc..  

    Please remember to adjust the above to include WOW6432node if you're running on 64-bit.

    I would then check that the Sophos Management Service can start and SEC 3 can open.  You can then detach the SOPHOS3 database from your SQL 2000 server as required.  You already have a backup file so you can always restore it should you need to.

    With SEC 3 now running again and pointing at the new location.  I would suggest leaving the system for 30 mins to catch up. With the management service down, depending on the number of clients and the time it was stopped it could still be processing backed up messages from clients.

    I would then suggest, taking the SEC 4.0 installer, and installing the new SOPHOS4 database on the SQL 2008 server.  To do so just choose the database role on the SQL server when running the installer.  Once complete you can then run the SEC 4.0 installer on the management service machine to update that.

    Now you're at SEC4.  You should then be able to repeat the procedure (database then management service) for SEC 4.5.  

    I hope this works for you.  One good thing, until you get to step 6 you can back out of this update and nothing has been affected as you can just start the management service again.

    Thanks,

    Jak

    :5178
  • 0

    Hey,

    Jak, thank you sir for providing this solution.

    As I got deeper and deeper into the upgrade process I think I was starting to move

    in this direction, however I was definitely lacking the details that you have provided.

    After struggling with this for a few days, it was actually decided that we would completely

    relocate the sophos server. So I basically just started from scratch.

    As much as I wanted to avoid this, I am kind of glad that I did because now I think I have

    a better understanding of all of the features that Sophos offers.

    Thank you for your response though.

    Cheers

    :5269