Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 2081 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 SEC 4.7 to SEC 50

BudgetHelp

Hi - I need to know how to upgrade SEC 4.7 to 50 but more so on the database side

We have the following set up:

Windows_ServerA running SEC4.7 and Update Mgr

Windows_ServerB running SQL 2008 Server with SOPHOS47 database

I can upgrade the SEC console no problem, but need advise on how to upgrade the SOPHOS47 DB to SOPHOS50 ?

On the SEC server to talk to the remote database, we modified this key:

Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS47;Data Source=<serverB>;

:19561


This thread was automatically locked due to age.
  • 0

    HI,

    You need to run the installer on the DB machine first.  All this will do is create 2 "empty" databases in the SQL instance:

    SOPHOS50

    SOPHOSPATCH

    This stage will leave the existing SOPHOS47 database and SEC 4.7 will continue to work.

    You then run the installer on the mamagement server, this will remove SEC 4.7 and install SEC 5.0.  As part of this install it will run a command line tool called UpdgradeDB.exe this will connect to the database machine and run a stored procedure that will copy the data from SOPHOS47 to the new SOPHOS50.

    You're then done.

    Hope this helps.

    Regards,

    Jak

    :19587
  • 0

    Hi,

    I tried this, I selected the database only install through setup but when I get to Database Details, selecting existing instance (MSSQLSERVER) I receive an error 'Cannot connect to SQL Server instance MSSQLSERVER'

    I'm a domain admin and SA for the SQL server

    :19603
  • 0

    Can you just put the name of the SQL server in the box?  If you're using the default (no-named instance) that should do it.  

    Otherwise:

    (local)

    or

    .

    should also work,

    If it all fails and you still have no joy, it is possible just to run the batch files from the DB directories (core and patch) to install the databases, but best to use the installer to minimise errors if you can.  You already have the "Sophos DB Admins" group, and the "DB account" the management service is using to connect to the database will still be a member of that.

    Jak

    :19605
  • 0

    No, none of this works, I just can't seem to install on the DB server, as you've mentioned I would prefer to avoid just running the scripts.

    The original SEC47 install was done fully on the SEC server, I then manually moved the SOPHOS47 database to the SQL DB server and changed the OLEDB registry settings on the SEC server for the remote DB connection.

    Can't believe Sophos still have not made the installs/upgrades more streamlined as mentioned with their 'Easy Upgrade' for Endpoint 10 :(

    :19609
  • 0
    Can't check the details as I'm at home. When you "manualy" moved the database - did you run the installer on the SQL server? Normally if you do so, then export and uninstall the DB on the management server, import on the database server and then start the console it will ask you for the database location. Entering the correct database will take care of the registry keys (and make subsequent upgrades simple).
    There should be a more specific error in the installer log why the connection failed. On the long run using only the installer(s) makes life easier. Some time ago I've played with moving around the database (including making the local database a remote one). As long as you have a current export nothing bad will happen. So you could just try to install the 4.7 database using the installer, re-import it and then try the 5.0 installer (which, as Jak said, would then "just" create the new databases).

    Christian
    :19615
  • 0

    I had exactly the same issue on an SQL 2005 database (Console on separate machine). 90 minutes of Sophos on remote control and they couldn't fix it. I ended up running the installer to create the database on a test SQL server (still go the error there once too!) and doing a backup/restore to move it onto the live one. Upgrading failed still but at least could install the console and start from scratch, though hardly ideal.

    :19679