Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 19 replies
  • Subscribers 2 subscribers
  • Views 114612 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

Upgrading Sophos Console 5.2.1 R2 to 5.4.1

Sahan Jinadasa

Good morning

I been using the Sophos Enterprise Console for few years now but very new to the upgrade process.

I have read the https://www.sophos.com/en-us/medialibrary/PDFs/documentation/sec_54_ugeng.pdf and related documentation with regard to this. However during the upgrade I encountered few problems and had to revert back to 5.2.1 R2. Having tried again I manage to install 5.4.1, I can see all managed computers listed and connected! However I got two problems:

  1. Console no longer show previous groups structure, policies and various manage roles.
  2. All of computers reporting as not up to date since yesterday 18:56, short time after the installation of 5.4.1 completed (I guess related to missing update policies).

I do have backups of old databases which were done before I started any of this work.

I would be very grateful if one of the forum members can assist me in restoring missing groups structure, policies and various manage roles (can easily be recreated) to the 5.4.1 console.

Thank you

Sahan



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

    Hello Sahan,

    no longer show
    looks like you've "lost" the database (contents) in the process. You can either restore everything (losing all data - alerts, errors, events - collected by new 5.4.1) or nothing (and you'd have to manually redo the configuration).

    not up to date
    are they reporting updating errors?     Apparently they can locate the server and as they are in Unassigned they won't receive a policy and therefore continue to use the one they've already had. Apparently SEC 5.4.1 (or rather its SUM) has successfully downloaded the software so something must have changed (e.g. previously the updated from ...\CIDs\S001\SAVSCFXP). Could you compare the value(s) in Primary server column (tab Update Details) with the information in View -> Bootstrap Locations ...?

    Christian

  • 0 in reply to QC

    Thank you Christian.

    You are correct even just comparing the size of SOPHOS521.mdf and SOPHOS540.mdf I can see massive difference in size.

    I don't mind losing information in 5.4.1 since it only been up just over 12 hours.

    Can kindly ask you to give me some guidance on this please.

    Cheers

    Sahan

  • 0 in reply to QC

    Hello Christian

    Database is on a SQL clustered instance, Sophos. Management server is viwsdb1.

    InstallDB .\SOPHOS SOPHOS540 Sophos_InstallCore540DB.log InstallDB.log
    Started
    20/01/2017
    10:26
    ==========
    HResult 0xFFFFFFFF, Level 16, State 1
    SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

    InstallDB SOPHOS\SOPHOS VIWSDB1 SOPHOS540 Sophos_InstallCore540DB.log
    Started
    20/01/2017
    10:28
    ==========
    Tables ...
    Common functions ...
    Error codes ...
    Metadata ...
    Views ...
    Functions ...
    Procs ...
    Packages ...
    Computers ...
    Groups ...
    Reporter ...
    PurgeDB ...
    Data ...
    SetAccess ...
    DefaultValues ...
    DirectoryService ...
    WebControl ...
    SophosEncryption ...
    SophosPatch ...
    ReportingInterface ...
    Upgrade ...

    Thanks

     

    Sahan

  • 0 in reply to Sahan Jinadasa

    Hello Sahan,

    on a SQL clustered instance
    I see, so yesterday's invocation with SOPHOS\SOPHOS is the correct one. Please try this once more (using SOPHOS\SOPHOS) and check/post the log.

    Christian

  • 0 in reply to QC

    C:\sec_541\ServerInstaller\DB\Core>InstallDB.bat SOPHOS\SOPHOS VIWSDB1 SOPHOS540 Sophos_InstallCore540DB.log

    Succeeded

     

    InstallDB SOPHOS\SOPHOS VIWSDB1 SOPHOS540 Sophos_InstallCore540DB.log
    Started
    20/01/2017
    11:30
    ==========
    Tables ...
    Common functions ...
    Error codes ...
    Metadata ...
    Views ...
    Functions ...
    Procs ...
    Packages ...
    Computers ...
    Groups ...
    Reporter ...
    PurgeDB ...
    Data ...
    SetAccess ...
    DefaultValues ...
    DirectoryService ...
    WebControl ...
    SophosEncryption ...
    SophosPatch ...
    ReportingInterface ...
    Upgrade ...

    Cheers

    Sahan

  • 0 in reply to Sahan Jinadasa

    Hello Sahan,

    looks ok, Could you now try the upgradeDB.exe once more?

    Christian

  • 0 in reply to QC

    Hi Christian

    C:\Program Files (x86)\Sophos\Enterprise Console>upgradedb.exe -debug -sourceVersion=521
    20.01.2017 11:55:32 Parsing command-line qualifiers ... successfully completed.
    20.01.2017 11:55:32 Validating parameter values ...
    20.01.2017 11:55:32 ... successfully completed.
    20.01.2017 11:55:32 Transferring data to the new database ...
    20.01.2017 11:55:37 Error: std::exception thrown SP Error: 55 (ErrorDataTransferFailed)
    20.01.2017 11:55:37 Exit code 5 (Failed to transfer data from the old database.)

    When I am running this from the management server, on the database I can see the SOPHOS540.mdf and SOPHOS540_log.LDF files changing...

    I bet if you are sitting at my desk you most likely have it fix in 2 mins :)

    Thanks

    Sahan

  • 0 in reply to Sahan Jinadasa

    Hello Sahan,

    you most likely have it fix in 2 mins
    whenever I had the 55 error it worked with the first try [:D]. Seriously, I did do this one or two times and the Drop-Install-Upgrade sequence did it. Haven't heard of such a persistent problem. Now Using the UpgradeDB.exe tool ... tells which SQL procedure is run and perhaps your database gurus could run it directly.

    Christian

  • 0 in reply to QC

    Thank you for your help so far...

    I will catch up dba's after their lunch and let you know how we get on.

    Cheers

    Sahan

  • 0 in reply to Sahan Jinadasa

    Hello Sahan,

    just to make sure (never forget to ask: Is the power cable plugged in): You are running the latest UpgradeDB.exe (mine is 5.4.0.574) and the DataBaseConnectionMS string points to the correct server\instance and database (SOPHOS540).

    Christian

  • 0 in reply to QC

    Yes I got the same version of UpgradeDB.exe and DatabaseConnectionMS points to Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS540;Data Source=SOPHOS\SOPHOS;

    Luckily we do have a 2nd update manager and clients seems to be updating themselves, just blind to any alerts, etc.

    Just waiting for the DBA to finish something.

    Cheers

    Sahan

  • +1 in reply to QC

    Hi Christian

    Just want to give an update and also say a massive thank you for your help and guidance.

    I had two remote sessions with Sophos... on Monday they ran DB upgrade manually within SQL but we still had the problem with the management service not starting. They got me to use SDU tool and send logs from both servers. Today one of the support chaps manage to fix the problem within 10-15mins, apparently upgrade status on on both DB wasn't set correct, and we all good again :)

    Again thank you so much for your help with this, really appreciate it.

    Cheers

    Sahan

Reply
  • +1 in reply to QC

    Hi Christian

    Just want to give an update and also say a massive thank you for your help and guidance.

    I had two remote sessions with Sophos... on Monday they ran DB upgrade manually within SQL but we still had the problem with the management service not starting. They got me to use SDU tool and send logs from both servers. Today one of the support chaps manage to fix the problem within 10-15mins, apparently upgrade status on on both DB wasn't set correct, and we all good again :)

    Again thank you so much for your help with this, really appreciate it.

    Cheers

    Sahan

Children
No Data
Unfiltered HTML